Logstreem
Monitor history
GET

Monitor history

Past evaluations and state transitions — the data for a flappiness audit.

Every evaluation for the last 30 days. Counting transitions here is the honest way to find monitors nobody trusts any more.

GET/v1/monitors/{id}/history

Path parameters

idstringrequired

mon_….

Query parameters

sincedatetime

RFC 3339. Defaults to 24 hours ago.

stateenum

Filter by state.

okalertno_data

curl -X GET https://api.logstreem.com/v1/monitors/{id}/history \
  -H "Authorization: Bearer $LOGSTREEM_TOKEN"

Responses

200OK
{
  "object": "list",
  "data": [
    { "state": "alert", "value": 41, "at": "2026-09-05T18:02:11.000Z" },
    { "state": "ok",    "value": 7,  "at": "2026-09-05T18:22:11.000Z" }
  ],
  "has_more": false,
  "next_cursor": null
}
401Unauthorized
{
  "error": {
    "type": "authentication_error",
    "code": "missing_token",
    "message": "No API token provided.",
    "doc_url": "https://logstreem.com/docs/errors#missing_token",
    "request_id": "req_9f3c2a7b41de08c5b2e6"
  }
}
Try itsandbox