Shift-handover digest
The digest is a shift handover: the problems now, what went wrong and what changed in the period, new best-practice findings, what expires soon, availability and unknown devices. You can read it on demand (the Reports page, or ask Claude) or have it emailed on a schedule (set by an admin on the Notifications page). It is assembled from what SZ-MCP already stores, with no controller calls and no AI model.
What is in a digest?
Section titled “What is in a digest?”Up to nine sections, in this order:
| Section | Contents |
|---|---|
| Problems now | Counts of critical, warning and unknown problems, how many are unhandled, and the worst 20, each with why it is handled (acknowledged, downtime …) |
| Since the last digest | HARD problems that began in the period (up to 30), whether each recovered, and the number of acknowledgements and downtime windows |
| Changes | Changes on the controller (admin audit log), configuration drift, writes made through SZ-MCP and inventory changes, with who made them and the newest 25 |
| Best practice | Findings on the latest configuration snapshot, and which are NEW since the last scheduled digest. Shown only once a snapshot exists |
| Expiring within 30 days | Certificates and licences, or “Nothing.” |
| Availability | Per device type, with devices below the 99.9% target. Shown only when there is data |
| Unknown devices | Devices on the network that are neither registered nor allowed by an unknown-device rule. Shown only when there are some |
| Notes | Anything the digest could not gather |
The first scheduled digest has nothing to compare best-practice findings with, and says so. Changes to client, radio and port inventory are left out of Changes: they would drown the rest.
How do I read it on demand?
Section titled “How do I read it on demand?”On Monitor › Reports, the Digest card shows it for the last 24 hours, 3 days or 7 days. Pick the Period and click Show. Markdown opens the same digest as a Markdown file. Every member of the organisation can do this. Times are shown in the scheduled digest’s time zone if one is set, otherwise UTC.
Claude uses history.digest. It covers the last 24 hours by default
(sinceHours, or since and until as epoch milliseconds), at most 8 days.
It can render times in any IANA zone (tz, for example 'Europe/London'). It
returns a headline and a text ready to read out or paste.
How do I have it emailed?
Section titled “How do I have it emailed?”An admin sets a schedule on the Digest card under Configure › Notifications.
- Open Configure › Notifications and find the Digest card (“a shift handover by email”).
- Choose Every day or week, and for a week On which day.
- Choose At an hour and a Time zone. The defaults are 07:00 on Mon (for weekly), in your browser’s time zone.
- Under Addresses, enter one address per line, up to 20.
- Leave Send the digest on, and click Save digest.
- Click Send a test to check delivery.
Only admins and the owner can save, test or remove a digest. Other members see the card read-only. An organisation has one digest schedule.
An address that is not a member’s sign-in email gets a confirmation email
first, as for alert email contacts, and is skipped until it confirms (see
Email contacts). The
card lists each address’s status. The subject reads
[SZ-MCP digest] <organisation>: <headline>.
Send the digest off pauses the schedule. Remove deletes it.
When is a scheduled digest sent?
Section titled “When is a scheduled digest sent?”Once per slot, at the chosen local hour. SZ-MCP checks every minute, and the local time follows daylight saving.
- A scheduled digest covers the time since the previous one: a day for a daily digest, a week for a weekly one, never more than 8 days.
- A slot that is missed by more than 6 hours (an outage) is skipped, not sent late. The next slot covers the gap, up to the 8 days.
- Email goes only to members’ sign-in addresses and confirmed addresses. When none of the addresses can be mailed, the send fails with “not sent: no confirmed address”.
- The card shows Last sent and, after a failure, the reason. The send is also
logged under Recent deliveries as
digest.
Send a test sends a digest of the last day (or week) at once. It does not
move the schedule or the “new findings” baseline, and it is logged as
digest:test.
What limits and errors apply?
Section titled “What limits and errors apply?”| Limit or message | When |
|---|---|
| 5 test sends an hour per organisation, shared with the other alert test sends | Up to 5 test sends an hour. |
| 20 reports a minute per organisation, shared with alert quality, post-mortems and MOP documents (on-demand digest) | at most 20 reports a minute |
Schedule: … | An unknown time zone |
A digest covers at most 8 days. | Claude asked for a period over 8 days with since and until (a longer sinceHours is refused by its argument check) |
Email is not available on this server. | Shown on the card when the server cannot send email |