Audit logs

Audit logs record every configuration change made in your project: what changed, who made the change, and when. They give owners and compliance teams a complete, attributable history of the account.

What gets logged

• Monitor changes: created, edited, paused, resumed, or deleted monitors.
• Status page incidents: created, updated, resolved, edited, or deleted, from the dashboard or the API, with the type of each published update. Updates published over the API also record their text.
• Status page settings: services, page access (password, Google sign-in, SSO on or off, the SSO connection used, allowed email domains), maximum session length, subscriber notifications, and subscription channels.
• Status page SSO connections: created, updated, configured (identity provider settings), or deleted.
• Subscribers and sessions: subscriber imports and removals by your team, from the dashboard or the API, and revoked reader sessions.
• Alerting changes: escalation policies, on-call schedules, and notification channels.
• Team changes: teammate invitations, removals, and role updates.
• Dashboard SSO: SSO configuration changes and SSO sign-ins.
• Integration changes: connected or removed integrations.
• API keys: keys created or deleted. Changes made with an API key, over the REST API or the MCP server, appear as ApiKeyWriteAction entries with the key as their target. A read-only key that attempts a change leaves an ApiKeyPermissionDenied entry.

What each entry contains

Every entry records the action that was performed, who performed it, and a precise timestamp. A change made in the dashboard shows the teammate's email. A change made with an API key shows the key's name and the IP address the request came from. This makes it easy to answer questions like "who disabled this monitor last Tuesday" or "when was this escalation policy changed".

Common use cases

• Compliance: provide an audit trail for SOC 2, ISO 27001, or internal security reviews. Logs can be exported for compliance reporting.
• Incident retros: reconstruct configuration changes that happened around an incident.
• Debugging alerting: find out when and by whom an escalation policy or notification channel was modified.
• Offboarding: review the activity of a teammate before removing them from the project. See Invite teammates.

Access and permissions

Audit logs cover activity across the whole project.

Plan availability

Audit logs are available on the Business plan.

Next steps