Only critical alerts at night

You’ll get: warnings and lower held back overnight, while critical alerts (or whatever threshold you choose) still notify you immediately — every event still shows up in the inbox either way.

Before you start

• A workspace on InfraInbox, with at least one destination already set up.

1. Set the window

Go to Notifications → Quiet hours. This is one window for the whole workspace, not per source or per destination: set Starts, Ends and the time zone it should use.

2. Set each destination’s threshold

Every destination has its own Quiet-hours threshold (on the destination’s edit page), defaulting to Critical. During the window you just set, a notice below a destination’s threshold is held back for that destination; the rest still notify normally.

• Leave a destination at Critical (the default) to only wake you up for the worst events.
• Raise a noisy destination’s threshold if even critical-only is still too much at 3am for that particular channel.
• Set a destination to the lowest severity if you want it to ignore quiet hours entirely — a status screen or a log channel, say.

Different destinations can use different thresholds: your phone’s push can stay at Critical while a Slack channel you only check in the morning stays fully open around the clock.

Check it works

• Outside the window, everything behaves as it did before — quiet hours only ever restrict, never widen, what a destination receives.
• During the window, send a Try an event (or a real test event) at a severity below a destination’s threshold: the incident still opens and appears in the inbox, but that destination doesn’t get a notification for it. The activity timeline records it as skipped for quiet hours.
• A test at or above the threshold still notifies immediately, quiet hours or not.

Next

• Quiet hours — the full reference.
• Tame a flapping monitor if what’s keeping you up isn’t the time of day but a check that won’t stop flipping.