Skip to content

ezgh obs alerts notifications

List the notifications sent to contact points, with their attempts.

Updated View as Markdown
ezgh obs alerts notifications [--contact-point cp] [--owner rule:<rule>]... [--status s]... [--kind k]... [flags]

List the project’s notifications, newest first: one row per notification to a contact point, with its kind (firing, resolved, repeat, noData, error, test, confirm), status, the rule or SLO it’s about, how many alerts it carried and its delivery attempts. STATUS is queued or retrying (due), sent, failed, dropped or silenced; ERROR is the latest attempt’s. -o json has every attempt (the latest 20, and attemptsTotal when there are more).

--contact-point (ID, slug or name), --owner (rule:<rule> or slo:<id>), --status and --kind narrow the list; --owner, --status and --kind can be given more than once.

Part of ezgh obs alerts.

Examples

ezgh obs alerts notifications --contact-point "Platform on-call"
ezgh obs alerts notifications --status failed,due --owner rule:"High API latency"

Flags

Flag Type Default Description
--all boolean follow nextCursor through every page
--contact-point string only notifications to this contact point (ID, slug or name)
--cursor string start from this page (a previous page’s nextCursor)
--kind strings, comma-separated or repeated only these kinds: firing, resolved, repeat, noData, error, test or confirm (repeat, or comma-separate)
--limit int 25 items per page, 1 to 100
--owner string, repeatable only notifications about these rules or SLOs: rule:<rule> (ID, slug or name) or slo:<id> (repeatable)
--rule string only notifications about this rule (ID, slug or name); the same as --owner rule:<rule>
--status strings, comma-separated or repeated only these statuses: due, sent, failed, dropped or silenced (repeat, or comma-separate)

This command also takes the global flags.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close