Severity and state mappings for Lightstep Observability

Alert priority and resolution state mapping between Lightstep Observability and Incident Response.

Lightstep Observability alert priority mapping

Lightstep Observability’s alert priority is based on the type of event that is fired. The source parameter indicates whether the alert type is metric or stream.

Streams alert

An alert is considered as Streams alert when the source parameter in the JSON payload is stream. The fields of interest for streams alerts is status.


Lightstep Observability payload field	Lightstep Observability payload value	Incident Response alert priority value
status	condition-violated	P2-Major

Metric alert

An alert is considered as Metrics alert when the source parameter in the JSON payload is metrics. The field of interest for metric alerts is status.


Lightstep Observability payload field	Lightstep Observability payload value	Incident Response alert priority value
status	Critical Threshold Violated	P1-Critical
	Warning Threshold Violated	P4-Low
	No Data Violation	P5-INFORMATIONAL

The default priority is P4.

Lightstep Observability resolution state mapping

The field of interest is status.


Lightstep Observability payload field	Lightstep Observability payload value	Incident Response alert resolution state value
status	Critical Threshold Violated	New
	condition-violated	New
	Warning Threshold Violated	New
	No Data Violation	New

There's no resolved state for Lightstep Observability.

Note: If you require any other severity and state mappings, use the Generic webhook integration.