Scheduled report emails
The four reports HowlOps can email your workspace, what each one contains, and how to turn any of them on or off.
HowlOps can email your workspace four scheduled summaries. All of them are configured in one place — Settings → Notifications, under the daily brief card — and all of them go to the same audience: every verified owner and admin of the workspace, plus any extra addresses you add (see below). Members do not receive them.
None of these are alerts. An outage pages you through your notification channels; these are summaries you read afterwards.
When they arrive
The daily brief has its own delivery time. The other three share one schedule, set under Settings → Notifications: a weekday and a time for the weekly cadences, a day of the month for the monthly ones, all in your workspace's timezone. Defaults are Monday, 08:00, and the 1st.
The day of the month stops at 28 on purpose. A report anchored to the 30th would silently skip February, and a report that skips a month is worse than one that arrives two days early.
A report you have just switched on waits for its next anchor rather than sending immediately, so the first one you receive covers a period your workspace actually lived through.
The four reports
Daily brief
Off by default. You choose the delivery time and timezone.
One email each morning covering the previous 24 hours: how many incidents there were, how many are still open, the average time to resolve them, which hours of the day they landed in, and the monitors with the lowest uptime. Incident causes are shown in plain language rather than the checker's internal codes.
If your workspace has quiet hours configured, the Include incidents that fired during quiet hours switch decides whether incidents that started inside that window are counted. When they are excluded, the email says so, so a filtered count can never be mistaken for a quiet night.
Weekly uptime report
On by default. Fires on your configured weekday and time; the cadence is fixed at once a week.
A verdict against your uptime target, the monitors with the lowest availability, and what got worse compared with the week before. See Weekly uptime report for the detail.
Uptime and alerting report
Off by default. Weekly or monthly, on the schedule above.
The report to send to whoever asks whether you are meeting your commitments: overall uptime with a comparison against the previous period, a verdict against your SLA target, average response time, the period's longest outage with its cause, per-day uptime bars, and a per-monitor table sorted worst first that combines alerts and incidents.
Set your target in SLA target (%) on the same settings card. It defaults to 99.9%.
Workspace report
Off by default. Weekly or monthly, on the schedule above. Requires a paid Uptime plan.
The operational counterpart to the uptime report: who was on call and how often they were paged, the median time they took to acknowledge, notifications broken down by channel, configured integrations with when they were last seen, and SMS/voice fair-use.
Fair-use is counted over the whole calendar month rather than the report's period, because a fair-use cap is a billing-cycle concept. The email says so where the numbers appear.
On a plan without the required capability the toggle is disabled and the settings page says why, rather than accepting a setting that would never send anything.
Sending reports to an address without an account
A shared mailbox, an alias, or a ticketing address can receive the reports without being given access to HowlOps. Add it under Settings → Notifications → Extra report recipients, up to ten per workspace.
Adding an address sends nothing. The address receives one confirmation email and decides for itself; until it confirms, the entry shows as waiting for confirmation and receives no reports. That is deliberate — we will not start mailing an address because somebody typed it into a form.
A confirmed extra recipient gets every report the workspace has switched on, in the workspace owner's language, and can stop them at any time with the unsubscribe link in any of them.
Turning a report off
There are two controls and they are not the same.
The switches under Settings → Notifications turn a report off for the whole workspace. Nobody receives it.
The unsubscribe link in the email turns that one report off for the one address that
clicked it. Everyone else on the workspace keeps getting it, and the address that clicked keeps
getting the other reports. It appears both as a link in the message and as the
List-Unsubscribe header your mail client's own unsubscribe button uses.
If you unsubscribe by accident, Settings → Notifications → Daily digest lists what your address has unsubscribed from and gives you a Resume button for each.
Two states are not self-service, because they are not preferences. If the address hard-bounced, we stop sending to it entirely until the mailbox is fixed. If it was reported as spam — or it unsubscribed before per-report opt-outs existed — every non-critical email to it stays stopped. Both are shown on the same settings card and both are cleared by support, not by a button.
What is never held back
Monitor alerts, escalation pages, password resets, email verification, MFA and billing notices are transactional. They are not affected by any switch on this page, and unsubscribing from reports never silences them.
Was this page helpful?