Slack listeners

A listener watches a Slack channel and creates an OpShift alert whenever a message matches a configured rule. It's useful for outage chatter that originates in Slack — a customer complaint, a deploy bot, a third-party status page mirror — that you want to route through the same on-call pipeline as your real alerts.

Anatomy of a listener

• Channel — the Slack channel to watch. The OpShift bot must be invited.
• Match rules — keyword list, regex, or sender filter. Listeners use a Sentry-style rule editor identical to webhook filter rules.
• Severity — what severity the resulting alert carries.
• Cooldown — minimum time between two alerts from the same listener, to prevent a noisy channel from flooding on-call.

Example: page on the word "outage"

Configure a listener on #status-updates with the rule:

IF message contains "outage" (case-insensitive)
AND sender != opshift-bot
THEN create alert at sev2

When someone posts "customer reports outage on checkout" in that channel, OpShift creates a sev2 alert with the message body as the description and routes it through your notification policies.