Skip to content

Send one app's alerts to its own channel

You’ll get: one source’s events skipping Default and going straight to a destination of their own — everything else keeps working exactly as before.

  • The source you want to split off already exists and is sending events.
  • The destination you want its alerts to reach — a dedicated Slack channel, a second Telegram chat, whatever it is — already exists too.

Rules run top to bottom, first match wins: InfraInbox checks each rule against an event in order, and the first one whose condition matches decides where the event goes — unless that rule is set to keep evaluating the ones below it too. Anything no rule catches falls through to Default.

On the source’s page, open the Notifications tab and click + Exception for this source: the new rule already has the source condition from step 2, and saving it brings you back to the source. (Or go to Notifications → Routing and create a custom rule.)

Under When an event looks like this, add a condition on the source field, is, and pick the source from the list. (If several sources belong to the same app — say, a few containers that all tag their events the same way — match on a metadata field or a tag instead: whatever field the events actually carry. The field list shows the metadata keys your recent events carried, with a few of their values.)

Under Do this with it, choose Open an incident, then under Who is told tick the destination this app’s alerts should reach (with Sound or Silent beside it). Leave Also apply the rules below unchecked if you want this to be the only place these alerts go — check it if you want them to reach this destination in addition to whatever the rules below (or Default) would otherwise send them to.

Save the rule.

New rules are evaluated in the order the list shows them, and you can drag a rule to reorder it. Make sure this rule sits above any other rule that would otherwise match the same events first — a rule further up always wins.

Open Notifications › Routing and pick the rule on the left: the coverage table on the right shows which destinations each severity reaches for a chosen source, so you can confirm this source now points where you expect before a real event arrives. The source’s Notifications tab lists the rule under step 1, and its Preview shows which step decides and who is told. Or use Preview routing for the source on its Overview, which opens Preview routing on a sample from that source; a rule’s editor tests your unsaved draft the same way: the result shows exactly which destinations would fire and why.

Once you’re confident, trigger (or wait for) a real event from that source and confirm it lands only where you intended.