Microsoft Azure Azure Application Insights Data Plane
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth27 EndpointsREST
For Agents
Run Kusto/Analytics queries against an Application Insights resource and read its events and pre-aggregated metrics.
Use for: Run an Analytics query for failed requests in the last 24 hours, Retrieve all exception events for application 'contoso-web' in the last hour, Fetch the event with id evt-1234 from application 'contoso-web', Read the requests/duration metric averaged over the last day
Not supported: Does not provision App Insights resources, configure sampling, or write telemetry — use only to read existing events, metrics, and run Analytics queries.
Jentic publishes the only available OpenAPI specification for Azure Application Insights Data Plane, keeping it validated and agent-ready. This API exposes the read-only telemetry surface for Application Insights: run Analytics (Kusto) queries against an application's logs, retrieve events filtered by event type, fetch event metadata via OData, and read pre-aggregated metric data with metadata. It is the surface used by dashboards, agents, and analytics pipelines that consume App Insights without hitting the management plane.
Install Jentic One Beta
Connect the Azure Application Insights Data Plane to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Application Insights Data Plane, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Azure Application Insights Data Plane API.
Run an Analytics (Kusto) query over an application's telemetry
Retrieve events of a specific type for a given application
Fetch a single event by id within an application
Read pre-aggregated metric data with optional time grain and aggregation
List the available metrics and their metadata for an application
Discover OData metadata for the events endpoint
Use Cases
Patterns agents use Azure Application Insights Data Plane API for, with concrete tasks.
★ Ad-Hoc Telemetry Investigation
On-call engineers triaging an alert run Analytics (Kusto) queries against Application Insights to find the affected requests, their durations, and correlated exceptions. GET /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/query takes a Kusto query string and returns columnar results suitable for piping into a notebook or chat reply.
Run a Kusto query 'requests | where success == false | summarize count() by resultCode' against application 'contoso-web' for the last 24 hours
Event-Type Drilldowns
Analysts often filter by event type (requests, exceptions, dependencies, customEvents) for a focused view. GET /components/{applicationName}/events/{eventType} returns paginated events for the chosen type with OData query support, so dashboards can drill from a high-level metric down to individual events.
List the last 100 exception events for application 'contoso-web' filtered to severityLevel >= 3
Pre-Aggregated Metric Reads
Status-page widgets and runbooks often need a single metric value over a fixed window without running a full Analytics query. GET /components/{applicationName}/metrics/{metricId} returns pre-aggregated metric data with timespan and aggregation parameters, which is faster and cheaper than the query endpoint for steady-state reads.
Read the requests/duration metric for application 'contoso-web' for the last hour with aggregation=avg
Agent-Driven Incident Summaries
An AI agent investigating an alert can run a Kusto query, fetch the matching exception events, and summarise the failure mode for a human. Through Jentic, the agent searches for 'query Application Insights telemetry', loads the query endpoint, and submits the Kusto string. The Azure OAuth token is held in the credential vault, and the agent sees only structured results.
Search Jentic for 'query Application Insights telemetry', load the query endpoint, and execute a Kusto query that returns the top exception messages from the last hour
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for azure application insights data plane, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/query
Run an Analytics query
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/events/{eventType}
Execute OData query for events of a type
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/events/{eventType}/{eventId}
Get a single event
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/events/$metadata
Get OData metadata
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/metrics/{metricId}
Read a metric
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/metrics/metadata
List metric metadata
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/query
Run an Analytics query
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/events/{eventType}
Execute OData query for events of a type
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/events/{eventType}/{eventId}
Get a single event
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/events/$metadata
Get OData metadata
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/metrics/{metricId}
Read a metric
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/metrics/metadata
List metric metadata
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure Active Directory OAuth 2.0 tokens are minted and rotated inside the Jentic vault (MAXsystem). Service principal client secrets stay encrypted; agents call Microsoft.Insights/components with a short-lived scoped token only.
Intent-based discovery
Agents search by intent (e.g., 'query Application Insights telemetry') and Jentic returns the matching query, events, or metrics operation with its input schema, so the agent does not need to know the long Microsoft.Insights data-plane path layout.
Time to first call
Direct integration: 1-2 days for AAD app registration, token acquisition, Kusto query construction, and pagination. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure Application Insights Data Plane API through Jentic.
Why is there no official OpenAPI spec for Azure Application Insights Data Plane?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure Application Insights Data Plane via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Application Insights Data Plane use?
The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme). Jentic stores the AAD app secret in the MAXsystem vault and exchanges it for a short-lived bearer token at execution time, so agents never see the raw secret.
Can I run Kusto (Analytics) queries against an application?
Yes. GET /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Insights/components/{applicationName}/query accepts a Kusto query string and returns columnar results. Use it for ad-hoc telemetry investigation or scheduled report generation.
How do I retrieve only exception events from an application?
Call GET /components/{applicationName}/events/{eventType} with eventType=exceptions. Add OData $filter and $top parameters to narrow severity, time range, or count, and follow nextLink for pagination.
What are the rate limits for the Application Insights Data Plane?
Limits depend on the App Insights resource pricing tier and the workload's daily ingestion. Heavy Kusto queries are subject to tighter throttling than metric reads. Honour HTTP 429 Retry-After values and prefer the metrics endpoint over the query endpoint for steady-state polling.
How do I run an Application Insights query through Jentic?
Run pip install jentic, then search Jentic with 'query Application Insights telemetry'. Jentic returns the query endpoint with its input schema. Load and execute with your subscription, resource group, application name, and Kusto string; the OAuth token is resolved from the vault automatically.
GET STARTED