Severity and state mappings for Honeybadger

Alert priority and resolution state mapping between Honeybadger and Incident Response.

Honeybadger alert priority mapping

The field of interest is event.

Honeybadger payload field Honeybadger payload value Incident Response alert priority value
event occurred P2-High
assigned P2-High
commented P2-High
resolved P0-Clear
unresolved P2-High
up P0-Clear
down P1-Critical
check_in_missing P5- INFORMATIONAL
check_in_reporting P0-Clear
Severity can be set by end user manually for Error monitoring critical P1-Critical
major P2-High
minor P3-Moderate
warning P4-Low
ok P5- INFORMATIONAL
clear P0-Clear

In Error monitoring, you can set your severity manually in the context field by adding the following lines to the code in the try block while installing the library in your system (For example, severity: minor). Otherwise, defaultseverity will be mapped to the alert once the alert is triggered.

Honeybadger.setContext({ 
    tags: { 
        "severity": "critical"
    } 
}); 

This will reflect at the end of the payload. Payload will contain the following object:

"context": { 
    "tags": { 
        "severity": "critical" 
      } 
} 
Note: There are six possible options that the user can use to set the severity manually: critical, major, minor, warning, ok, and clear. If you define any other options, you will get an error in the severity.

Honeybadger resolution state mapping

The field of interest is event.

Honeybadger payload field Honeybadger payload value Incident Response alert resolution state value
event resolved Closed
up
check_in_reporting
events other than these New
Note: If you require any other severity and state mappings, use the Generic webhook integration.