Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Azure / Diagnostics API Client
Diagnostics API Client logo

Microsoft Azure Diagnostics API Client

Browse all Azure APIs
52
AI ReadinessFoundational (C-)52/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring Observabilityoauth222 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Run Azure App Service diagnostic detectors and analyses programmatically - list detector categories, fetch detector responses, and execute on-demand site analysis for a web app or deployment slot.

Use for: I need to run a diagnostic detector against my Azure web app, List all diagnostic categories available for an App Service site, Retrieve the detector response that explains why my site is throwing 500 errors, Execute a site analysis to investigate slow response times on a deployment slot

Not supported: Does not modify App Service configuration, deploy code, or change scaling - use for App Service diagnostic detectors and on-demand site analyses only.

Jentic publishes the only available OpenAPI specification for Diagnostics API Client, keeping it validated and agent-ready. The Azure Diagnostics API Client provides programmatic access to diagnostic detectors, analyses, and category data for Azure App Service sites and App Service Environments. It exposes 22 endpoints that let you list site diagnostic categories, retrieve detector responses for sites and deployment slots, and execute analyses against a running web app. The API is part of the Microsoft.Web resource provider on management.azure.com and is used to surface the same troubleshooting data as the Azure portal Diagnose and solve problems blade.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Diagnostics API Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Diagnostics API Client, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-diagnostics-api-client" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-diagnostics-api-client" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Diagnostics API Client API.

List diagnostic categories available for an Azure App Service site

Retrieve detector responses for a hosting environment to investigate platform issues

Fetch site analysis results for a specific diagnostic category and time range

Execute a named site analysis on demand against a running App Service app

Run detectors against a deployment slot to compare staging and production behaviour

Pull aggregated detector responses across all sites in a resource group

Use Cases

Patterns agents use Diagnostics API Client API for, with concrete tasks.

★ Automated App Service Incident Triage

When an Azure App Service site is misbehaving, on-call engineers can use the Diagnostics API to pull the same detector output that the portal Diagnose and solve problems blade shows. By listing detector responses for the site, then executing the relevant detector against the suspected time window, the API surfaces the root-cause category - CPU pressure, memory exhaustion, dependency failures, or platform restarts - without an engineer ever opening the portal. Results return in seconds and can be piped straight into a Slack or PagerDuty incident channel.

List all detector responses for the site mywebapp in resource group prod-rg, then execute the ApplicationCrashes detector and return the top three findings.

Slot-Level Regression Detection

Before swapping a staging deployment slot into production, teams need to confirm that the new build is not introducing regressions. The Diagnostics API exposes detector and analysis endpoints scoped to a specific deployment slot, so an agent can run the same checks against staging that already pass against production and surface any new diagnostic findings. This lets continuous delivery pipelines gate slot swaps on real diagnostic signal rather than just synthetic tests.

Execute the HttpServerErrors detector against the staging slot of mywebapp and compare the result count against the production slot output for the last 30 minutes.

Hosting Environment Health Monitoring

App Service Environment operators run dozens of sites on shared infrastructure and need a single view of platform health. The hosting environment detector endpoints return diagnostic data scoped to the entire ASE rather than a single site, so an agent can pull a daily health summary covering networking, scaling, and front-end availability. This is the same data the Azure platform team uses to investigate ASE-wide incidents.

Retrieve all hosting environment detector responses for the ASE named prod-ase and flag any with severity Error in the past 24 hours.

AI Agent Diagnostic Assistant via Jentic

An AI assistant integrated through Jentic can resolve App Service support tickets without a human pulling logs. Given a customer report like the checkout site is slow, the agent searches Jentic for diagnose azure app service, loads the Diagnostics API operation schema, executes the relevant analysis against the named site, and replies with a plain-English summary of the detector output. Credentials never leave your Jentic One instance, and the agent only sees a scoped access token.

Through Jentic, search for diagnose azure app service, load the Diagnostics_ExecuteSiteAnalysis schema, and run it against mywebapp with the analysis name AvailabilityAndPerformance.

Key Endpoints

22 endpoints — jentic publishes the only available openapi specification for diagnostics api client, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/diagnostics

List diagnostic categories for an App Service site

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/detectors

List detector responses for a site

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/diagnostics/{diagnosticCategory}/analyses/{analysisName}/execute

Execute a named site analysis

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/diagnostics/{diagnosticCategory}/detectors/{detectorName}/execute

Execute a named site detector

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/slots/{slot}/detectors

List detector responses for a deployment slot

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/detectors

List detector responses for an App Service Environment

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/diagnostics

List diagnostic categories for an App Service site

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/detectors

List detector responses for a site

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/diagnostics/{diagnosticCategory}/analyses/{analysisName}/execute

Execute a named site analysis

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/diagnostics/{diagnosticCategory}/detectors/{detectorName}/execute

Execute a named site detector

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/slots/{slot}/detectors

List detector responses for a deployment slot

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/detectors

List detector responses for an App Service Environment

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

D

Diagnostics API Client

- Foundational (C-)
52/100
73
Foundational Compliance
63
Developer Experience & Jentic Compatibility
32
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

32

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
79%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Microsoft.Web diagnostics API by hand means acquiring Azure AD OAuth 2.0 bearer tokens, constructing the ARM URLs under management.azure.com, and handling pagination and the x-ms-ratelimit headers yourself. Through Jentic you install once, import the Diagnostics API Client from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The site, slot, and hosting-environment ids travel in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/...), so a rule can pin your agent to one subscription, resource group, and site. The surface is read-and-execute only, so you can limit the agent to listing detectors and running the analyses it needs and leave the rest out.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected as a short-lived bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'diagnose an azure app service site' or 'list detector responses for a web app', and Jentic returns the matching Diagnostics operation with its subscription, resource-group, and site-name input schema so the agent calls the right endpoint without crawling Azure REST docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

DNS Management Client

→

Manage Azure DNS zones and record sets that often back the App Service sites being diagnosed

Choose this when the agent needs to inspect or change DNS records pointing at an App Service site, not when investigating in-app failures

Complementary

EventGrid Management Client

→

Wire Azure resource events (including App Service health events) into downstream consumers

Use when the agent needs to subscribe to App Service events rather than poll detectors directly

Alternative

Disk Resource Provider Client

→

Manages Azure managed disks rather than App Service diagnostics

Choose this when the workload runs on virtual machines rather than App Service and the agent needs to inspect disk state

FAQs

Specific to using Diagnostics API Client API through Jentic.

Why is there no official OpenAPI spec for Diagnostics API Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Diagnostics API Client via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Diagnostics API Client use?

The API uses Azure Active Directory OAuth 2.0 (azure_auth). Calls go to https://management.azure.com/ with a bearer access token obtained from Azure AD. Through Jentic, the Azure credential is held in your Jentic One instance and the agent receives a scoped access token only - the underlying client secret or certificate never enters the agent context.

Can I execute a site analysis against an Azure App Service deployment slot?

Yes. The endpoint POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/slots/{slot}/diagnostics/{diagnosticCategory}/analyses/{analysisName}/execute runs a named analysis against a specific deployment slot, which is useful for validating staging slots before swap.

What are the rate limits for the Diagnostics API Client?

Azure Resource Manager applies subscription-scoped throttling, generally documented as 12,000 reads per hour and 1,200 writes per hour per subscription. The Diagnostics API endpoints are read-heavy (GET) plus a few execute (POST) operations and share that envelope. Inspect x-ms-ratelimit-* response headers for remaining quota.

How do I list detector responses for a site through Jentic?

Run pip install jentic, then search for list azure app service detector responses, load the Diagnostics_ListSiteDetectorResponses schema, and execute it with subscriptionId, resourceGroupName, and siteName. The response is the JSON detector collection straight from the Microsoft.Web provider.

Does this API let me change App Service configuration?

No. The Diagnostics API Client is read-and-execute only - it lists detectors, fetches detector responses, and runs named analyses. To modify App Service settings, scaling, or deployment slots, use the separate Web Apps management API on the Microsoft.Web provider.

Can I limit what my agent is allowed to do with the Diagnostics API Client?

Yes. Because you run Jentic One yourself, your own rules decide which Diagnostics operations and credentials the agent may use. Since the subscription, resource group, site, and slot ids all travel in the URL path, you can pin the agent to a single subscription, resource group, and site. The surface is read-and-execute only, so you can allow just the operations you need, such as listing detector categories, fetching detector responses, and executing named site analyses, and leave the rest off.

GET STARTED

Start building with Diagnostics API Client API

Explore with Jentic One
View OpenAPI Document