> ## Documentation Index
> Fetch the complete documentation index at: https://docs.persistence.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts and activity

> Monitor incidents and audit important workspace changes.

Alerts identify operational conditions that need attention. Activity records important workspace and system events so a team can understand what changed and who or what initiated it.

<Frame caption="Activity history can be searched and filtered across agent, campaign, integration, user, usage, and system events.">
  <img src="https://mintcdn.com/persistence-ai/vTPO-R7syJyo2N_1/images/dashboard/activity.png?fit=max&auto=format&n=vTPO-R7syJyo2N_1&q=85&s=0c52af3776d4d346cf49e1e2c052402b" alt="Persistence Alerts and Activity dashboard showing a filtered workspace activity history" width="640" height="360" data-path="images/dashboard/activity.png" />
</Frame>

## Review an alert

Use severity, status, date, resource type, and saved filters to narrow the incident list. Open an incident to review the affected resource, start time, acknowledgement, resolution, and related activity.

Create alert rules only for conditions that have a clear owner and response. Snooze an alert when investigation is already in progress, and unsnooze it when notifications should resume.

## Audit activity

Use **Activity** to review events such as agent configuration changes, campaign starts or failures, integration changes, role changes, import failures, and usage or cost events. Pair an activity entry with the relevant agent version, campaign, conversation, or integration record when investigating.

<Note>
  An activity record explains that an event occurred. It does not replace provider logs, conversation details, or an incident-response record when deeper evidence is required.
</Note>