Ingest Azure Monitor alerts 🔗
You can use Incident Intelligence ingest endpoints to ingest alerts from various third-party sources. In Incident Intelligence you can then create on-call schedules and incident workflows to route third-party incidents to responders. Use the Azure Monitor endpoint to forward Azure Monitor alerts to Incident Intelligence.
Azure Monitor ingest endpoint 🔗
To send Azure Monitor alerts to the ingest endpoint, make a POST call to the endpoint.
https://ingest.<REALM>.signalfx.com/v1/incidentintelligence/azure-monitor
For steps to obtain your realm see View your realm, API endpoints, and organization.
Request header 🔗
Header |
Required |
Description |
---|---|---|
X-SF-Token |
Required |
Authentication token. See Find and copy your API access token. Ensure that the token has INGEST listed under Authorization Scopes. |
Content-Type |
Required |
application/json |
Alert fields 🔗
The following fields are transformed as part of the common information model. All other included fields are included properties object in the transformed alert.
Field |
Required |
Type |
Description |
---|---|---|---|
alertRule |
Required |
String |
The alert rule name |
monitoringService |
Required |
String |
The monitoring service for the alert |
severity |
Required |
String |
The alert severity |
firedDateTime |
Required |
String |
Alert fired date and time. Send date and time in the Azure format (ISO 8601). It is transformed to the epoch long format for the |
JSON payload 🔗
Refer to the following example JSON payload for the Azure Monitor endpoint.
Example JSON payload:
{
"schemaId": "azureMonitorCommonAlertSchema",
"data": {
"essentials": {
"alertId": "<YOUR_ALERT_ID>",
"alertRule": "WCUS-R2-Gen2",
"severity": "Sev3",
"signalType": "Metric",
"monitorCondition": "Resolved",
"monitoringService": "Platform",
"alertTargetIDs": [
"<YOUR_ALERTTARGET_ID>"
],
"configurationItems": [
"wcus-r2-gen2"
],
"originAlertId": "<YOUR_ORIGINALERT_ID>",
"firedDateTime": "2019-03-22T13:58:24.3713213Z",
"resolvedDateTime": "2019-03-22T14:03:16.2246313Z",
"description": "",
"essentialsVersion": "1.0",
"alertContextVersion": "1.0"
},
"alertContext": {
"properties": null,
"conditionType": "SingleResourceMultipleMetricCriteria",
"condition": {
"windowSize": "PT5M",
"allOf": [
{
"metricName": "Percentage CPU",
"metricNamespace": "Microsoft.Compute/virtualMachines",
"operator": "GreaterThan",
"threshold": "25",
"timeAggregation": "Average",
"dimensions": [
{
"name": "ResourceId",
"value": "3efad9dc-3d50-4eac-9c87-8b3fd6f97e4e"
}
],
"metricValue": 7.727
}
]
}
}
}
}
Using this endpoint, your alert is ingested and transformed into the common event model for alerts in Incident Intelligence. This is an example of the transformed alert data that is saved as an alert in Incident Intelligence:
{
"id": "<YOUR_ID>",
"eventId": "<YOUR_EVENT_ID>",
"title": "Azure Monitor Alert for WCUS-R2-Gen2",
"source": "Platform",
"description": "",
"severity": "major",
"sourceType": "azure_monitor",
"orgId": "<YOUR_ORG_ID>",
"triggeredAt": 1553263104371,
"properties": {
"schemaId": "azureMonitorCommonAlertSchema",
"data": {
"essentials": {
"alertId": "<YOUR_ALERT_ID>",
"alertRule": "WCUS-R2-Gen2",
"severity": "Sev3",
"signalType": "Metric",
"monitorCondition": "Resolved",
"monitoringService": "Platform",
"alertTargetIDs": [
"<YOUR_ALERTTARGET_ID>"
],
"configurationItems": [
"wcus-r2-gen2"
],
"originAlertId": "<YOUR_ORIGINALERT_ID>",
"firedDateTime": "2019-03-22T13:58:24.3713213Z",
"resolvedDateTime": "2019-03-22T14:03:16.2246313Z",
"description": "",
"essentialsVersion": "1.0",
"alertContextVersion": "1.0"
},
"alertContext": {
"properties": null,
"conditionType": "SingleResourceMultipleMetricCriteria",
"condition": {
"windowSize": "PT5M",
"allOf": [
{
"metricName": "Percentage CPU",
"metricNamespace": "Microsoft.Compute/virtualMachines",
"operator": "GreaterThan",
"threshold": "25",
"timeAggregation": "Average",
"dimensions": [
{
"name": "ResourceId",
"value": "<YOUR_RESOURCE_ID>"
}
],
"metricValue": 7.727
}
]
}
}
}
}
}