Skip to content

Commit 48e5d7a

Browse files
authored
Update alerts-common-schema-test-action-definitions.md
1 parent c54bf68 commit 48e5d7a

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

articles/azure-monitor/alerts/alerts-common-schema-test-action-definitions.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -71,20 +71,20 @@ Any alert instance describes the resource that was affected and the cause of the
7171

7272
| Field | Description|
7373
|:---|:---|
74-
| alertId | The unique resource ID that identifies the alert instance. |
75-
| alertRule | The name of the alert rule that generated the alert instance. |
76-
| Severity | The severity of the alert. Possible values: Sev0, Sev1, Sev2, Sev3, or Sev4. |
77-
| signalType | Identifies the signal on which the alert rule was defined. Possible values: Metric, Log, or Activity Log. |
78-
| monitorCondition | When an alert fires, the alert's monitor condition is set to **Fired**. When the underlying condition that caused the alert to fire clears, the monitor condition is set to **Resolved**. |
79-
| monitoringService | The monitoring service or solution that generated the alert. The fields for the alert context are dictated by the monitoring service. |
80-
| alertTargetIds | The list of the Azure Resource Manager IDs that are affected targets of an alert. For a log alert defined on a Log Analytics workspace or Application Insights instance, it's the respective workspace or application. |
81-
| configurationItems | The list of affected resources of an alert. The configuration items can be different from the alert targets in some cases, for example, in metric-for-log or log alerts defined on a Log Analytics workspace. The configuration items are the actual resources that send the telemetry and not the workspace. This field is used by IT service management systems to correlate alerts to resources in a configuration management database. |
82-
| originAlertId | The ID of the alert instance, as generated by the monitoring service generating it. |
83-
| firedDateTime | The date and time when the alert instance was fired in Coordinated Universal Time (UTC). |
84-
| resolvedDateTime | The date and time when the monitor condition for the alert instance is set to **Resolved** in UTC. Currently, only applicable for metric alerts.|
85-
| description | The description, as defined in the alert rule. |
86-
|essentialsVersion| The version number for the `essentials` section.|
87-
|alertContextVersion | The version number for the `alertContext` section. |
74+
| `alertId` | The unique resource ID that identifies the alert instance. |
75+
| `alertRule` | The name of the alert rule that generated the alert instance. |
76+
| `Severity` | The severity of the alert. Possible values: `Sev0`, `Sev1`, `Sev2`, `Sev3`, or `Sev4`. |
77+
| `signalType` | Identifies the signal on which the alert rule was defined. Possible values: `Metric`, `Log`, or `Activity Log`. |
78+
| `monitorCondition` | When an alert fires, the alert's monitor condition is set to `Fired`. When the underlying condition that caused the alert to fire clears, the monitor condition is set to `Resolved`. |
79+
| `monitoringService` | The monitoring service or solution that generated the alert. The fields for the alert context are dictated by the monitoring service. |
80+
| `alertTargetIds` | The list of the Azure Resource Manager IDs that are affected targets of an alert. For a log alert defined on a Log Analytics workspace or Application Insights instance, it's the respective workspace or application. |
81+
| `configurationItems` | The list of affected resources of an alert. The configuration items can be different from the alert targets in some cases, for example, in metric-for-log or log alerts defined on a Log Analytics workspace. The configuration items are the actual resources that send the telemetry and not the workspace. This field is used by IT service management systems to correlate alerts to resources in a configuration management database. |
82+
| `originAlertId` | The ID of the alert instance, as generated by the monitoring service generating it. |
83+
| `firedDateTime` | The date and time when the alert instance was fired in Coordinated Universal Time (UTC). |
84+
| `resolvedDateTime` | The date and time when the monitor condition for the alert instance is set to `Resolved` in UTC. Currently, only applicable for metric alerts.|
85+
| `description` | The description, as defined in the alert rule. |
86+
|`essentialsVersion`| The version number for the `essentials` section.|
87+
|`alertContextVersion` | The version number for the `alertContext` section. |
8888

8989
**Sample values**
9090
```json

0 commit comments

Comments
 (0)