Send one app's alerts to its own channel

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

Before you start

• 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.

How rules work

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 the default route.

1. Add a rule

Go to Notifications → Routing and click New rule.

2. Match the app

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.)

3. Route it

Under Do this with it, choose Open an incident, then add the destination this app’s alerts should reach. Leave Keep evaluating the rules below and add their destinations 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 the default route) would otherwise send them to.

Save the rule.

4. Put it where it needs to be

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.

Check it works

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. Or use Try an event with a sample event from that source: 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.

Next

• Routing rules and the default route — the full condition and action vocabulary.
• Silence alerts during maintenance if what you actually want is to hold this app’s alerts back temporarily, not reroute them permanently.