Severity and state mappings for Prometheus
Alert priority and resolution state mapping between Prometheus and Incident Response.
Prometheus alert priority mapping
Prometheus’s alert priority is based on two fields in the payload. The fields of interest
are:
alerts[0].labels.severityalerts[0].status
| Prometheus payload field | Prometheus payload value | Incident Response alert priority value |
|---|---|---|
| alerts[0].labels.severity | critical | P1-Critical |
| warning | P4-Low | |
| ok | P5-INFORMATIONAL | |
| alerts[0].status | resolved | Clear/0 |
Prometheus resolution state mapping
The field of interest is: alerts[0].status
| Prometheus payload field | Prometheus payload value | Incident Response alert resolution state value |
|---|---|---|
| alerts[0].status | resolved | Closing |
| New |
Note: If you require any other severity and state mappings, use the
Generic webhook integration.
Prometheus payload to alert field mapping
| Incident Response alert field | Prometheus payload field |
|---|---|
| Priority | alerts[0].labels.severity |
| State | alerts[0].status |
| Source URL | alerts[0].generatorURL |
| Source | prometheus |
| Node | alerts[0].labels.instance If alerts[0].labels.instance is
ip-xxx-xx-x-xx.us-east-2.compute.internal:9100, node will be the part before the
colon. For example, in this case, node is
|
| Message key | alerts[0].fingerprint |
| Metric type | alerts[0].labels.type |
| Metric name | alerts[0].labels.metricName |
| Resource | alerts[0].labels.resource |
| Alert description | alerts[0].annotations.description |
| Additional info | Prometheus original payload |