Skip to content

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.

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

Go to Notifications › Muting and, under Quiet hours, turn on Enable quiet hours. This is one window for the whole workspace, not per source or per destination: set From and To on the workspace’s clock.

Every destination has its own threshold, defaulting to Critical. The same Muting tab lists every destination under quiet hours with a Still gets through picker: change it right there, no need to open the destination (its edit page has the same setting), then Save once for the window and the pickers together. 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.

  • Outside the window, everything behaves as it did before — quiet hours only ever restrict, never widen, what a destination receives.
  • During the window, run Preview routing (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.