Azure Alertsmanagement Alertsmanagement

Connector for the azure-alertsmanagement-alertsmanagement API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://management.azure.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• alerts_metadata — GET /providers/Microsoft.AlertsManagement/alertsMetaData — List alerts meta data information based on value of identifier parameter.
• operations_list — GET /providers/Microsoft.AlertsManagement/operations — List all operations available through Azure Alerts Management Resource Provider.
• actionrules_listbysubscription — GET /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/actionRules — Get all action rule in a given subscription
• alerts_getall — GET /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts — List all existing alerts, where the results can be filtered on the basis of mult
• alerts_getbyid — GET /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId} — Get a specific alert.
• alerts_gethistory — GET /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/history — Get the history of an alert, which captures any monitor condition changes (Fired

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: alerts_metadata
# (attach an 'oauth' credential to the task — no inline secrets)