Skip to main content
GET
Get alert firing

Authorizations

Authorization
string
header
required

Use an Observe API key from the management console. The key selects the project and must grant the permission listed on the operation. Keep this key on your server.

Path Parameters

alertFiringID
string
required

A transition of the firing (format atr-<number>).

Response

The firing.

One firing of an alert, from the evaluation that switched it to firing to the one that switched it to another status. Severity changes while firing belong to it. An alert that fires again after it ended, also after a stretch without data, starts a new firing.

id
string
required

The transition that fired the alert (format atr-<number>).

alert
object
required
firedMs
integer<int64>
required

When the alert switched to firing.

durationMs
integer<int64>
required

How long the alert was firing, up to now while it still is.

transitions
object[]
required

The firing's transitions, oldest first: the breach that made it pending, if any, the one that fired it, its severity changes and the one that ended it.

Maximum array length: 500
notifications
object[]
required

What was sent from the start of the firing to its end, oldest first.

Maximum array length: 1000
pendingSinceMs
integer<int64>

When the breach that led to the firing began. Absent when it fired without a pending period.

endedMs
integer<int64>

When the firing ended. Absent while the alert is still firing.

endStatus
enum<string>

The status the alert switched to when the firing ended. Absent while it is still firing.

Available options:
normal,
pending,
no_data,
error
endReason
string

Why the firing ended, the reason of the transition that ended it: recovery, a no-data reason or rule_changed. Absent while it is still firing.

previousFiringID
string

The alert's firing before this one (format atr-<number>). Absent when there is none.

nextFiringID
string

The alert's firing after this one (format atr-<number>). Absent when there is none.