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 / Azure Metrics
Azure Metrics logo

Microsoft Azure Azure Metrics

Browse all Azure APIs
39
AI ReadinessNon-Ready (F)39/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring Observabilitynone1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Publish custom metric data points for an Azure resource into the Azure Monitor metrics store. Useful when an agent needs to emit numeric telemetry tied to a subscription, resource group, and resource name.

Use for: I need to publish a custom metric for an Azure VM, Send a numeric data point to Azure Monitor for a specific resource, Record a request count metric against an Azure resource, Emit a latency value into the Azure metrics store

Not supported: Does not handle log ingestion, trace ingestion, or metric querying - use for publishing custom numeric metrics to Azure Monitor only.

Jentic publishes the only available OpenAPI specification for Azure Metrics, keeping it validated and agent-ready. The Azure Metrics API lets clients submit custom metric data points to the Azure Monitor metrics store via a single regional ingestion endpoint at monitoring.azure.com. It is the publishing side of the Azure Monitor metrics pipeline, used by applications and infrastructure to record numeric time-series data tied to a specific Azure resource. Once ingested, these metrics can be queried, charted, and alerted on through Azure Monitor.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Azure Metrics to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Metrics, 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-metrics" | 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-metrics" | 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 Azure Metrics API.

Publish a batch of custom metric values for an Azure resource at a specific timestamp

Tag emitted metrics with namespace, name, and dimension values for later filtering in Azure Monitor

Scope metric submissions to a subscription, resource group, resource provider, and resource type

Send numeric time-series data into the Azure Monitor metrics pipeline for charts and alerts

Record application-level counters that complement the platform metrics Azure already collects

Use Cases

Patterns agents use Azure Metrics API for, with concrete tasks.

★ Custom Application Metrics

Publish application-level numeric metrics (request rate, queue depth, error count) against the Azure resource that hosts the workload. The Azure Metrics ingestion endpoint accepts a batch of values with namespace, name, and dimensions, and stores them in Azure Monitor for charting and alerting alongside platform metrics. A single POST per emit cycle is enough to instrument a service.

POST a custom metric named 'request_count' with value 42 and dimension 'endpoint=/checkout' against a specific App Service resource using the Metrics_Create operation.

Telemetry From Background Jobs

Background workers and scheduled jobs running outside Application Insights can still emit health and throughput numbers by sending them to the Azure Metrics endpoint. Each call records a metric value tied to the Azure resource that owns the job, so dashboards and alert rules in Azure Monitor see the same shape of data as platform metrics.

Emit a 'job_duration_seconds' metric with value 12.5 for the resource hosting the worker after each job run using a POST to the metrics path.

Threshold Alerting On Custom Signals

Azure Monitor alert rules trigger on metric values regardless of whether the metric was emitted by the platform or a custom source. By publishing custom values through the Azure Metrics API, teams gain the ability to alert on signals Azure does not collect natively, such as business KPIs or third-party integration health, without standing up a separate monitoring stack.

POST a custom 'failed_payments_per_minute' metric so an existing Azure Monitor alert rule can fire when the value exceeds a configured threshold.

AI Agent Telemetry Ingestion

An agent acting on Azure resources can publish operational telemetry about its own actions (operations attempted, latency, retry count) to Azure Monitor via the Metrics ingestion endpoint. Through Jentic, the agent searches for the Azure Metrics operation by intent, loads the input schema, and POSTs values without manually constructing the long subscription/resource-provider/resource path.

Use Jentic to call the Azure Metrics POST operation and emit an 'agent_action_count' metric tagged with agent_id and outcome dimensions after each tool invocation.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for azure metrics, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{resourceProvider}/{resourceTypeName}/{resourceName}/metrics

Publish a batch of custom metric values for an Azure resource

POST

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{resourceProvider}/{resourceTypeName}/{resourceName}/metrics

Publish a batch of custom metric values for an Azure resource

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.

A

Azure Metrics

- Non-Ready (F)
39/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
14
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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.

14

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
58%

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.

0%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

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 Azure Metrics ingestion endpoint by hand means acquiring an Azure AD bearer token for the https://monitoring.azure.com/.default scope even though the spec declares no scheme, shaping the time-series payload, and treating 429 responses as a signal to back off and batch. Through Jentic you install once, import Azure Metrics from the API Directory, store the Azure AD credentials once, and your agent calls it.

Permission scoping

This endpoint puts the subscription, resource group, resource provider, resource type, and resource name in the URL path (/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{resourceProvider}/{resourceTypeName}/{resourceName}/metrics), so a rule can pin your agent to publishing metrics for one resource. It exposes a single publish operation, so the agent can emit metric values and nothing else unless you add more operations.

Credential isolation

Your Azure AD bearer credentials for monitoring.azure.com are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'publish a custom metric to Azure Monitor', and Jentic returns the Metrics_Create operation with its input schema so the agent submits values without hand-constructing the long subscription and resource-provider path.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Monitor Management Client

→

Reads metric definitions, alert rules, and diagnostic settings while azure-metrics writes metric values.

Choose monitormanagementclient when the agent needs to query or configure Azure Monitor; use azure-metrics only to publish numeric data points.

Alternative

Application Insights Management Client

→

Application Insights ingests richer telemetry (traces, exceptions, dependencies); azure-metrics only handles numeric metrics.

Pick Application Insights when the workload needs distributed tracing or exception telemetry, not just numeric values.

Complementary

Azure Action Groups

→

Defines the notification targets that fire when alerts on these custom metrics trigger.

Use azure-action-groups after publishing metrics, to wire alerts on those metrics to email, webhook, or runbook actions.

FAQs

Specific to using Azure Metrics API through Jentic.

Why is there no official OpenAPI spec for Azure Metrics?

Microsoft Azure does not publish an OpenAPI specification for the Azure Metrics ingestion endpoint. Jentic generates and maintains this spec so that AI agents and developers can call Azure Metrics 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 Azure Metrics API use?

The published spec does not declare a security scheme, but in practice the monitoring.azure.com ingestion endpoint requires an Azure AD bearer token with the `https://monitoring.azure.com/.default` scope. Through Jentic, those tokens are stored in your Jentic One instance and never enter the agent's context.

Can I publish multiple metric values in one call to Azure Metrics?

Yes. The Metrics_Create POST operation accepts a payload with a time, base data, and dimensions, so one call can carry several metric series for the same resource at the same timestamp.

What are the rate limits for the Azure Metrics API?

Azure Monitor enforces ingestion limits per region and per resource (documented as throttling on the monitoring.azure.com endpoint). The OpenAPI spec does not encode the exact numbers, so production agents should treat 429 responses as a signal to back off and batch more values per request.

How do I send a custom metric with the Azure Metrics API through Jentic?

Run pip install jentic, then call client.search('publish a custom metric to Azure Monitor'). Jentic returns the Metrics_Create operation, you load its schema, and execute with subscriptionId, resourceGroupName, the resource path, and the metric payload.

Does Azure Metrics replace Application Insights?

No. The Azure Metrics ingestion endpoint only handles numeric metric data points. Logs, traces, exceptions, and request telemetry still belong in Application Insights or Log Analytics.

Can I limit what my agent is allowed to do with the Azure Metrics API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. The Azure Metrics API exposes a single publish operation (Metrics_Create), so your rules can let the agent emit metric values and nothing else. Since the subscription, resource group, resource provider, resource type, and resource name all live in the request path, you can also pin the agent to publishing metrics for one specific Azure resource.

GET STARTED

Start building with Azure Metrics API

Explore with Jentic One
View OpenAPI Document