Skip to main content

Alert Transitions

Page Outline

Returns the state transition history for a specific monitoring alert, showing how it moved between states (triggered → acknowledged → resolved) and which users acted on it.

Base Path: /api/v1/models

Method: GET

Path: /{model_id}/monitoring/alerts/{alert_id}/transitions

Auth: Requires a valid Bearer token (Authorization: Bearer <JWT>)

Path Parameters

ParameterTypeDescription
model_idstringUnique identifier of the model
alert_idstringUnique identifier of the monitoring alert

Behavior

  • Returns the complete lifecycle of an alert from initial trigger through all subsequent state changes.
  • State transitions are recorded when users acknowledge or resolve alerts, or when the system auto-resolves them (e.g., drift score drops below threshold).
  • Includes metadata about automatic vs. manual resolution.
  • Returns HTTP 404 if the alert or model is not found.
  • Returns HTTP 403 if the caller does not have access to the model's monitoring data.

Response

Returns an AlertTransitionHistory object.

{
"alert_id": "alt-001",
"model_id": "mdl-7f3a19bc",
"type": "data_drift",
"feature": "monthly_spend",
"transitions": [
{
"from_status": null,
"to_status": "active",
"reason": "PSI score 0.24 exceeded threshold 0.20",
"actor": "system",
"timestamp": "2026-03-12T08:00:00Z"
},
{
"from_status": "active",
"to_status": "acknowledged",
"reason": "Under investigation",
"actor": "user-001",
"timestamp": "2026-03-12T09:15:00Z"
},
{
"from_status": "acknowledged",
"to_status": "resolved",
"reason": "PSI score returned to 0.06, below threshold",
"actor": "system",
"timestamp": "2026-03-13T00:00:00Z"
}
]
}