History
History is the record of what happened to your monitors, newest first. Each entry is one event: a change you made, a change of status, a change in a certificate, or (on a monitor's own page) an alert sent about it. History is read-only, and visiting it marks nothing as read.
History keeps 90 days on every plan. That is separate from check history, the individual check results behind the Metrics chart and each monitor's check table, which your plan keeps for 30, 90, or 365 days (see Monitoring behavior).
The History page
History in the sidebar lists events across every monitor, 25 to a page. The tabs narrow it: All, Certificates (endpoint events), Domains, and Account (configuration changes, including changes to alert settings and the Slack mention, and to a monitor's configuration, and pauses CertWatch makes to enforce a plan's limit). The tab is kept in the page address, so a refresh or a shared link opens the same view. An Acknowledge from Slack is listed under the person's Slack name, as "Sam (Slack)". Older and Newer page through the list, and an event that arrives while you browse never shifts the page you are on.
The page lists configuration changes and monitoring events: changes to the monitor's status, new certificates, and checks that recovered. It does not list the alerts sent. Those are on each monitor's own History and in Alert history.
A monitor's History
Every monitor card has a History tab. It holds the same 90 days of events for that one monitor, with the alerts sent about it. The filter tabs are All, Your changes, Status, Certificate (Registration on a domain), and Alerts. The choice is kept in the page address. Show older events adds the next page of events below the ones you see. A removed monitor's events stay readable on the History page until they age out, labelled "(removed)" and without a link.
| Filter | What it shows |
|---|---|
| Your changes | Changes you made to the monitor: added, removed, paused, resumed, muted, unmuted, label edits, renewal mode choices, and acknowledgements given or withdrawn. Pausing that CertWatch does to enforce a plan's limit appears here too. |
| Status | Every change of status, and checks that recovered after failing or being delayed. |
| Certificate or Registration | A new certificate observed on an endpoint. CertWatch records no registration changes for a domain, so a domain's Registration filter has nothing to show. |
| Alerts | Each alert sent about the monitor, with its type, the message, the criteria that fired it, and a View alert link to its delivery details. |
Reading an entry
- Status entries read like "Certificate status: Urgent", with the Reason and the status it replaced: "5 days remaining; was Late for 3 days 4 hours". On a monitor's own History the duration appears when both ends of the stretch are in the list you are reading, and is left out rather than guessed when the earlier change is on an older page. The History page shows the reason and the earlier status without a duration. An expiry already past says how long ago, in hours on its first day ("13 hours ago; was Urgent"); hover over it for the exact time, in your time zone.
- New certificate observed says what was observed, not what it means, and is never an alert (see a new certificate). It notes when the new certificate cleared an earlier Urgent or Down status, and the status the new certificate arrived with. It appears only for a certificate the monitor has not served before on any of its addresses, so a server that alternates between two certificates shows one entry, not one per switch. A new certificate on only some of a hostname's addresses (a renewal still rolling out) gets its entry when the first address serves it; when those are not the addresses the status comes from, the entry names them and the status stays as it was.
- Checks recovered is about the checking, not the certificate: conclusive checks resumed after failed, partial, or overdue ones, and the entry says since when they had been failing or delayed.
- An alert entry's title is the alert type (Late, Urgent, Down, Unreachable, or Recovered) followed by "alert". Its Sent because line says what it was sent for: for a certificate, the Late or Urgent point in days and where it came from, such as "9 days remaining: expected renewal by default, as no renewal has been seen yet"; for a domain, the point it crossed, such as "within 30 days"; and "certificate could not be read" for an endpoint's Unreachable alert.
- Alert acknowledged and Acknowledgement withdrawn record Acknowledge: that an acknowledgement holds until its alert ends or a new status is announced, and that a withdrawn one's reminders resume. Older entries can also read Alerts snoozed until renewed, Snooze cancelled, or Snooze ended, from a hold CertWatch has since removed.
- Each entry ends with who made the change (System for what CertWatch observed itself) and the time.
While a monitor's scheduled checks are overdue, its status follows its last check and its certificate's or registration's dates (see Monitoring), and nothing is written to History while the checks are delayed. The next check that completes records the change of status, measured from the status the last check reported.