Microsoft Azure Azure Metrics

Name: Azure Metrics API
Brand: Azure Metrics
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitynone1 EndpointsREST

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.

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 | sh

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 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

GET STARTED

Start building with Azure Metrics API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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.

Time to first call

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.