List a project's alert instances
Pending, firing and noData instances, and those resolved in the last 15 minutes, with the silences that mute them, in the instance order: firing, noData, pending, silenced, resolved, then the newest activeAt first, then fingerprint. silenced is a display state: a pending, firing or noData instance that an active silence matches (state keeps its underlying state). total counts the instances the filters keep. limit is 1-100 (default 50). A content read: unrecorded. 404 while alerting isn't offered (the console hides Alerting then).
https://obs.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/obs/alertsAuthorization
Path parameters
Query parameters
Returns
200
A page of alert instances.
- truncatedbooleanrequired
True when the filters keep more instances than one request reads (20,000, the most severe state and the newest activeAt first): total is then a lower bound and paging ends early. The filters that narrow the read are owner, severity, q, label name=value and name!=value, and state other than silenced; label regular expressions and state=silenced are applied to the instances read.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.