Severity sent in the payload is ignored

Question

We fire an alert trigger from our deploy pipeline and pass severity in the JSON body. No matter what we send, the incident always ends up with the severity we configured on the trigger itself. We send lowercase values like critical and warning.

Selin Yıldız · Accepted Answer

Correct, there are four levels and warning is not one of them. A practical mapping that most teams land on:

1. Your critical maps to CRITICAL.
2. Your error or page-worthy maps to HIGH. Note that everything MonoDuty creates automatically, such as a monitor going down or a heartbeat going overdue, is also HIGH, so this level will be your busiest.
3. Your warning maps to MEDIUM.
4. Your info or notice maps to LOW.

Send the value uppercase and it will be honoured. The other two body fields behave the same way: title and description override the trigger's predefined values when present, and fall back to them when omitted. Since the endpoint always answers 200 OK regardless, verify the mapping once by firing a test alert and checking the severity on the resulting incident.

Selin Yıldız · Answer

Hello Lukas, that pins it down almost completely. Severity values are case sensitive and uppercase only, and the accepted set is CRITICAL, HIGH, MEDIUM and LOW. There is no warning level. When the value you send is not in that set, it is silently discarded and the trigger's predefined severity is used instead, which is exactly the behaviour you are seeing.

Lukas Weber · Answer

So warning simply does not exist? What should we map it to?

Lukas Weber · Answer

Uppercase did it. Mapped warning to MEDIUM as suggested.

Severity sent in the payload is ignored

3 replies