Skip to main content
Episodes contain alert noise minute to minute. The digest is the other half: the durable fix for a flapping signal is almost always upstream, in the monitor’s own threshold or check, and the digest is a weekly, ranked answer to “which monitors should we go fix.”

What’s in it

The weekly digest is off by default. An organisation owner or admin can opt in under Settings → Incident Policies → Alert noise, choose the delivery weekday, time, organisation timezone, minimum re-fire count, and the active organisation members who should receive it. When enabled, Warrn sends one organisation-wide email for the completed calendar week, grouped by team, to the selected recipients:
  • The headline numbers: total flaps across the team’s signals, how many times those signals paged someone, and how the week compares to the previous one.
  • A ranked list of the noisiest signals, loudest first. Each entry shows the signal and its service, how many times it flapped that week, its total fire count, and a link straight to the alert.
  • A “never acknowledged” marker on signals nobody has ever acked. These are your strongest candidates for deletion or retuning: they page, and no one has ever once cared.
  • A snoozed marker on signals someone has quieted. Snoozing hides pages, not the problem, so snoozed signals stay in the digest until the source is fixed.
Counts are strictly per week, from the alert timeline. A signal that flapped 40 times last week and 5 times this week shows 5 and an improving trend, so the digest rewards fixes instead of dragging history around.

Delivery and eligibility

The digest does not send when there is nothing to say:
  • A signal appears only if it re-fired at least the configured threshold during that calendar week (3 by default).
  • Teams with no qualifying signals are omitted. If no team has a qualifying signal, no email is sent.
  • Only active members selected by an owner or admin are eligible recipients. A member who is removed or deactivated before delivery is skipped.
  • Recipient choices are snapshotted when a digest run is created, so changing the setting does not silently redirect an already-created digest.
The delivery schedule is organisation-wide rather than per team. Warrn evaluates organisations through the shared organisation-maintenance schedule, but each organisation keeps its own enabled flag, weekday, local delivery time, timezone, threshold, and recipients.

Preview and history

Owners and admins can generate a week-to-date or last-completed-week preview without changing the delivery schedule. The Alert noise page keeps the five most recent digest runs available to view and download as HTML or CSV. A manual preview is stored like a scheduled run, but it is not emailed unless an admin explicitly sends it.

Acting on it

When the digest lands, the workflow is: open the loudest never-acked signal, follow the link, and fix or delete the monitor behind it. One of those a week compounds fast.