legacy_alerts

Get alert by ID.

“evalMatches” data in the response is cached in the db when and only when the state of the alert changes (e.g. transitioning from “ok” to “alerting” state). If data from one server triggers the alert first and, before that server is seen leaving alerting state, a second server also enters a state that would trigger the alert, the second server will not be visible in “evalMatches” data.

get/alerts/{alert_id}

Request

  • Base URL
    /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /api/alerts/{alert_id}
  • Auth
    • HTTP basic
    • or API key in header Authorization

Path parameters

alert_idstring required

Response

(empty)

Createdstring date-time
DashboardIdinteger
EvalDataJson
ExecutionErrorstring
Forinteger
Frequencyinteger
Handlerinteger
Idinteger
Messagestring
Namestring
NewStateDatestring date-time
OrgIdinteger
PanelIdinteger
SettingsJson
Severitystring
Silencedboolean
Statestring
StateChangesinteger
Updatedstring date-time
Versioninteger

Changes

No recorded changes to this operation across all 2 revisions of this API.