Microsoft Azure · OpenAPI Overlay 1.0.0
API Evangelist conversational phrasing for Microsoft Azure Metrics Advisor Anomaly Alerting API
8 actions
8 updates
phrasing
extends
openapi/microsoft-azure-anomalyalerting-api-openapi.yml
Generated by API Evangelist
Written by API Evangelist tooling for Microsoft Azure's API. It is a proposal applied on top of the contract, not a document Microsoft Azure publishes.
What the actions change
x-apievangelist-phrasing
Targets 8
$.info
$.paths['/alert/anomaly/configurations/{configurationId}'].get
$.paths['/alert/anomaly/configurations/{configurationId}'].delete
$.paths['/alert/anomaly/configurations/{configurationId}'].patch
$.paths['/alert/anomaly/configurations'].post
$.paths['/alert/anomaly/configurations/{configurationId}/alerts/query'].post
$.paths['/alert/anomaly/configurations/{configurationId}/alerts/{alertId}/anomalies'].get
$.paths['/alert/anomaly/configurations/{configurationId}/alerts/{alertId}/incidents'].get
OpenAPI Overlay
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
title: API Evangelist conversational phrasing for Microsoft Azure Metrics Advisor Anomaly Alerting API
version: 1.0.0
extends: openapi/microsoft-azure-anomalyalerting-api-openapi.yml
actions:
- target: $.info
update:
x-apievangelist-phrasing:
method: generated
generated: '2026-09-26'
generator: build-phrasing.py
label: Generated by API Evangelist
operations: 7
- target: $.paths['/alert/anomaly/configurations/{configurationId}'].get
update:
x-apievangelist-phrasing:
intent: Get an anomaly alerting configuration
effect: read
questions:
- What hooks and metric rules does a specific anomaly alert configuration use?
- Can I look up one alerting configuration by its id?
instructions:
- text: Get anomaly alerting configuration {configurationId}.
slots:
configurationId: path.configurationId
- text: Show the settings of alert configuration {configurationId}.
slots:
configurationId: path.configurationId
method: generated
generated: '2026-09-26'
- target: $.paths['/alert/anomaly/configurations/{configurationId}'].delete
update:
x-apievangelist-phrasing:
intent: Delete an anomaly alerting configuration
effect: destructive
questions:
- Can I remove an anomaly alert configuration I no longer want?
- What id do I need to delete an alerting configuration?
instructions:
- text: Delete anomaly alerting configuration {configurationId}.
slots:
configurationId: path.configurationId
- text: Remove the alert configuration {configurationId} so it stops firing.
slots:
configurationId: path.configurationId
method: generated
generated: '2026-09-26'
- target: $.paths['/alert/anomaly/configurations/{configurationId}'].patch
update:
x-apievangelist-phrasing:
intent: Update an anomaly alerting configuration
effect: write
questions:
- Can I change which hooks an existing anomaly alert notifies?
- How do I rename or re-split an alert configuration by dimensions?
instructions:
- text: Update alerting configuration {configurationId} to notify hooks {hookIds}.
slots:
configurationId: path.configurationId
hookIds: requestBody.hookIds
- text: Rename existing alert configuration {configurationId} to {name}.
slots:
configurationId: path.configurationId
name: requestBody.name
- text: Split alerts from configuration {configurationId} by dimensions {splitAlertByDimensions}.
slots:
configurationId: path.configurationId
splitAlertByDimensions: requestBody.splitAlertByDimensions
method: generated
generated: '2026-09-26'
- target: $.paths['/alert/anomaly/configurations'].post
update:
x-apievangelist-phrasing:
intent: Create an anomaly alerting configuration
effect: write
questions:
- How do I set up alerts when anomalies are detected on my metrics?
- Can one new alert configuration combine several metrics with a cross-metric operator?
instructions:
- text: Create an anomaly alerting configuration named {name} that notifies hooks {hookIds} using rules {metricAlertingConfigurations}.
slots:
name: requestBody.name
hookIds: requestBody.hookIds
metricAlertingConfigurations: requestBody.metricAlertingConfigurations
- text: Set up a new alert {name} across metrics {metricAlertingConfigurations} joined by {crossMetricsOperator}, sent to {hookIds}.
slots:
name: requestBody.name
metricAlertingConfigurations: requestBody.metricAlertingConfigurations
crossMetricsOperator: requestBody.crossMetricsOperator
hookIds: requestBody.hookIds
method: generated
generated: '2026-09-26'
- target: $.paths['/alert/anomaly/configurations/{configurationId}/alerts/query'].post
update:
x-apievangelist-phrasing:
intent: Query alerts fired by an alerting configuration
effect: read
questions:
- Which alerts did an anomaly alert configuration fire last week?
- Can I page through alerts for a configuration within a time window?
instructions:
- text: Find alerts from configuration {configurationId} between {startTime} and {endTime} using time mode {timeMode}.
slots:
configurationId: path.configurationId
startTime: requestBody.startTime
endTime: requestBody.endTime
timeMode: requestBody.timeMode
- text: Query up to {maxpagesize} alerts per page for configuration {configurationId} from {startTime} to {endTime} by {timeMode}.
slots:
maxpagesize: query.$maxpagesize
configurationId: path.configurationId
startTime: requestBody.startTime
endTime: requestBody.endTime
timeMode: requestBody.timeMode
method: generated
generated: '2026-09-26'
- target: $.paths['/alert/anomaly/configurations/{configurationId}/alerts/{alertId}/anomalies'].get
update:
x-apievangelist-phrasing:
intent: List anomalies behind a specific alert
effect: read
questions:
- What anomalies triggered a particular alert?
- Can I drill into the individual anomalies inside one alert?
instructions:
- text: List anomalies for alert {alertId} under configuration {configurationId}.
slots:
alertId: path.alertId
configurationId: path.configurationId
- text: Show the anomaly points behind alert {alertId} from configuration {configurationId}, skipping {skip}.
slots:
alertId: path.alertId
configurationId: path.configurationId
skip: query.$skip
method: generated
generated: '2026-09-26'
- target: $.paths['/alert/anomaly/configurations/{configurationId}/alerts/{alertId}/incidents'].get
update:
x-apievangelist-phrasing:
intent: List incidents behind a specific alert
effect: read
questions:
- Which incidents are grouped under a particular anomaly alert?
- Can I page through the incidents attached to one alert?
instructions:
- text: List incidents for alert {alertId} under configuration {configurationId}.
slots:
alertId: path.alertId
configurationId: path.configurationId
- text: Show {maxpagesize} incidents per page for alert {alertId} in configuration {configurationId}.
slots:
maxpagesize: query.$maxpagesize
alertId: path.alertId
configurationId: path.configurationId
method: generated
generated: '2026-09-26'
Work with this as data
Every overlay here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for openapi overlays
4 MCP tools reach this
find_overlaysBrowse and filter every overlay in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/microsoft-azure-anomalyalerting-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.