List the alarm's observed state transitions newest-first.

GET

/v1/projects/{projectId}/observability/alarms/{alarmId}/history

Code sample: Shell / cURL

curl --request GET \
  --url 'https://stratum.example.com/v1/projects/example/observability/alarms/example/history?limit=100' \
  --header 'Authorization: Bearer <token>'

• A Stratum cluster endpoint.

Cursor-paginated. Ordered transition_at DESC, id DESC — the id is not decoration: two transitions inside one timestamp tick would otherwise have an arbitrary relative order, and a cursor on that boundary makes a client see a row twice or miss one entirely.

When nextPageToken is present there are more rows; pass it back as page_token. Its absence means the last page. A token that cannot be parsed is treated as no token — you get the first page rather than a 400, since a client never constructs the value itself.

Authorizations

• bearerAuth

Parameters

Path Parameters

projectId

required

string

/^p-[a-z0-9-]+$/

alarmId

required

string

/^al-[a-z0-9]{1,32}$/

Query Parameters

limit

integer

default: 100 >= 1 <= 500

page_token

string

Opaque cursor from a previous response’s nextPageToken. Omit for the first page.

Responses

200

Transitions.

Media typeapplication/json

object

items

required

Array<object>

One observed alarm state flip.

object

id

required

string

/^ast-[a-z0-9]{1,32}$/

alarmId

required

string

projectId

required

string

fromState

Empty on the first observation of an alarm.

string

Allowed values: insufficient_data pending ok alarm

toState

required

string

Allowed values: insufficient_data pending ok alarm

transitionAt

required

string format: date-time

reason

string

vmalertEval

Vmalert evaluation snapshot (value, threshold, samples). Optional.

object

key

additional properties

any

auditEventId

Cross-link to a config-change audit event. Empty on pure state flips.

string

nextPageToken

string

Example

{
  "items": [
    {
      "fromState": "insufficient_data",
      "toState": "insufficient_data"
    }
  ]
}

404

Resource not found.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}