Channels supported
Slack
Per-channel delivery for insights, RCAs, and action approvals.
Microsoft Teams
Per-channel delivery for the same update types.
PagerDuty
Promote critical insights to on-call pages. Configurable severity thresholds.
A weekly digest and account notices, sent to each member’s account email. Turn email on or off in your notification settings. Per-event alerts by email are not available yet.
Linear
Turn RCAs into tickets with one click.
Webhooks
POST to any endpoint. For routing into your own internal systems.
Events you can route
Routing rules
Every rule has four fields: event type, scope (environment, namespace, tag), severity threshold, and destination. A few shapes worth knowing.Per-service Slack routing
Per-service Slack routing
Route payments-related insights to
#payments-ops, platform insights to #platform, everything else to #rubixkube.On-call escalation
On-call escalation
Insights at Critical severity in prod environments page PagerDuty. Everything else stays in chat.
RCA-to-ticket
RCA-to-ticket
Every verified RCA in prod opens a Linear ticket in the on-call team’s queue. Details and link back to the report auto-populated.
Weekly email digest
Weekly email digest
Each member gets a weekly digest email with a summary of the week. Route individual insights to chat or PagerDuty instead.
Controls that keep signal-to-noise high
Severity thresholds
Start strict. Loosen if something important slipped through.
Quiet hours
Suppress non-critical routes outside business hours.
Deduplication windows
Similar insights within a window collapse into one notification.
Snooze and acknowledge
Silencing an insight in Slack or Teams syncs back to the console.
Related guides
Integrations
Connect Slack, Teams, Linear, and PagerDuty.
Magic Insights
Where the events you route originate.