Audit logs

When a warning was missed, inspect what changed.

Audit logs help teams review changes to monitors, channels, roles, invites, and billing-sensitive settings before the next renewal cycle.

See securityTeam workspaces

Audit trail

Certificate changes stay inspectable

Evidence kept

Monitor edits, route changes, team updates, and review states remain visible after the incident.

Monitorapi.example.com threshold changed
RouteWebhook test delivered
ReviewOwner acknowledged
Monitor, route, member, and workspace events
Audit trail

Workspace settings and recent changes stay inspectable.

Settings shows plan defaults, alert thresholds, account controls, and recent audit rows for monitor, route, member, and policy changes.

01

Workspace and monitor changes

Audit history covers changes that can affect whether a certificate warning reaches the right person.

Audit rows worth checking
ChangeWhy it matters during review
Monitor paused or deletedA hostname may have stopped checking before the renewal window.
Alert threshold changedWarnings may have moved later than the team expected.
Slack channel removedUrgent events may no longer reach the watched path.
Import committedNew client or production hostnames may have entered coverage.
Role updated or invite acceptedResponsibility or access may have shifted before the event.
02

Useful during cleanup

Audit rows make stale channels, old invites, and risky access changes easier to review before the next certificate deadline.

03

Review after incidents

After a missed warning, audit rows help teams confirm whether a monitor was paused, a route changed, a channel failed, or access moved during a handoff.

  • Use audit rows to reconstruct setup changes before the event.
  • Use them to clean up stale channels and access.
  • Use them to inspect routine setup changes before the next renewal.
FAQ1 answer

  1. What does audit history cover?

    Audit history covers workspace, monitor, alert channel, invite, role, and billing-sensitive changes that affect certificate monitoring.

Related3 pagesSecurityReview public-probing, private-key, webhook-signing, and access boundaries.View page page
DocsWebhook docsVerify signed webhook payloads and replay tolerance.PagePrivacySee what account, monitor, and delivery data the service stores.
Review access and changes

Keep certificate monitoring visible when settings change.

Use team workspaces for shared access and audit history when more than one person touches monitors or channels.

See team workspacesRead security