Recent up/down transitions (latest fires and resolutions), node names joined.

GET

/api/v1/alerts/transitions

curl --request GET \
  --url https://example.com/api/v1/alerts/transitions \
  --header 'Authorization: Bearer <token>'

Only limit is documented, though the handler borrows the history query type: this endpoint reads no cursor, and advertising one would promise paging it does not do.

Authorizations

• bearer

Parameters

Query Parameters

limit

integer format: int64

How many transitions to return (default 12)

Responses

200

The latest fires and resolutions; empty when this deployment keeps no history

Media typeapplication/json

Array<object>

One recent state-change row (a fire = into an alert state; a resolve = recovery to ok).

object

at_unix_ms

required

integer format: int64

name

required

string

node_id

required

string format: uuid

resolved

required

True = recovery (→ ok); false = went into the alert state.

boolean

severity

required

How serious an alert is. Variants are declared low → high so the derived Ord ranks Critical above Warning above Info.

string

Allowed values: info warning critical

state

required

The current state of a monitored node or check.

string

Allowed values: ok warning critical unknown unreachable maintenance

Example

[
  {
    "severity": "info",
    "state": "ok"
  }
]

401

No valid bearer token

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}

403

Role lacks the read permission

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}