Skip to content

ezgh obs silences create

Mute matching alert instances' notifications for a while.

Updated View as Markdown
ezgh obs silences create --matcher name=value... [--starts now|RFC3339] (--ends RFC3339 | --duration 2h) --comment text [flags]

Create a silence: while it’s active, alert instances whose labels match every --matcher send no notifications (they’re still evaluated, and shown as silenced). A matcher is name=value, name!=value, name=~regex or name!~regex (anchored RE2, as Alertmanager’s); at least one must not match an empty value, so a silence can’t mute everything by accident. Every instance carries the labels alertname (its rule’s name) and ezgh_rule (the rule’s ID), besides its own.

It starts now, or at --starts, and ends at --ends or after --duration: at most 30 days after it starts. --comment says why. When it ends (or is expired), instances still firing are notified at once.

Part of ezgh obs silences.

Examples

ezgh obs silences create --matcher service=api --duration 2h --comment "Database maintenance"
ezgh obs silences create --matcher alertname="High API latency" --matcher 'env!~stag.*' \
  --starts 2026-10-14T02:00:00Z --ends 2026-10-14T04:00:00Z --comment "Planned failover"

Flags

Flag Type Default Description
--comment string why (required)
--duration duration how long it lasts from its start, like 2h or 90m (instead of --ends)
--ends string when it ends (RFC 3339)
--matcher string, repeatable a label matcher: name=value, name!=value, name=~regex or name!~regex (repeatable; required)
--starts string now when it starts: now, or an RFC 3339 time

This command also takes the global flags.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close