Health and monthly reports

Every connected site is checked several times a day, which puts each site on a four to six hour rhythm. The verdict is a list of reasons, never a score out of a hundred:

• the site did not answer the last few checks;
• the site refused our key;
• PHP reached end of life and no longer gets security fixes;
• WordPress is behind the current release;
• WP-Cron is switched off, or its next run is overdue and has not moved;
• a client key appeared on the site that nobody in the workspace accepted.

One missed check is not an outage: the site keeps the state it had, because a host restarting is not a fault. The Sites list sorts by what needs attention.

Switch on alerts in Settings and you get one email per site when its state changes, carrying the same reasons.

The monthly report

Reports builds a month for a client group or for the whole workspace, from records made as they happened: checks answered and days down per site, the jobs that ran and who queued them, a count of every change by tool, what needs attention today, and the calls that were refused.

Take it as a print view, CSV or JSON, or switch on the monthly email and it goes out on the first, one per client group.

The client’s own copy

Under Client branding, put your own name, logo and two colours on a client group’s report. Then add that client’s own people to the group’s recipient list and switch the send on: on the first of the month they get the document, from you. There is no account for them, no sign-in and no link back into ReDock.

You can preview the whole thing, the same bytes the send uses, before anybody is on the list. A colour pair that would put pale text on a pale band is refused with the measured contrast ratio in the message, so nothing unreadable reaches a client. Nothing about one client ever appears on another client’s report.