Endpoint checks, restore tests, and a change log
- Endpoints: HTTP, TCP and TLS checks with answer time, uptime and certificate expiry; failures and expiring certificates become alerts and notifications; linked to a server for maintenance and tags - Restore tests: record when a backup was restored and how it went; failed tests always alert, overdue ones with a limit set; shown on the Backup coverage page - Change log: one filterable timeline made from the audit log and the incident record Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
c3bc6bbf72
commit
92726568b7
37 files changed
+6918
-21
No files matched your search
@@ -64,6 +64,14 @@ rest, and the alert starts over if it goes away and comes back. Problems under m
|
||||
informational never escalate. It is looked at every five minutes, so a step can arrive a few minutes after its time. Every escalation is written in the audit
|
||||
log (category *alert*, action *escalate*).
|
||||
|
||||
## Endpoint checks and restore tests
|
||||
|
||||
An **endpoint check** that fails several times in a row (the check's own number, 2 by default) is announced like any other server problem — under the *server offline,
|
||||
disk full …* switch (`healthAlerts`) — once when it starts, with a recovery message when it answers again; a certificate that is within its warning time is announced
|
||||
the same way. For routing they count as *Monitoring* (a check that fails) and *Expiry* (a certificate), and carry the tags of the server the check is linked to; maintenance on that
|
||||
server holds them back. A **restore test** that fails, or one that is overdue (when a limit is set), is on the Alerts page and in the incident record but is not sent as a
|
||||
notification of its own — it is something to look at when you are looking at backups.
|
||||
|
||||
## Push to a phone or browser
|
||||
|
||||
The fifth channel, **Phone and browser**, sends the same messages as the others to browsers that have asked for them — a phone with
|
||||
|
||||
Reference in new issue
Block a user