> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/configuration-guide/monitoring.md).

# Monitoring

Configure monitoring rules for log spikes, user impact spikes, and governor limits in Pharos Admin.

Monitoring in Pharos detects **patterns** rather than individual errors. While [notifications](https://docs.pharos.ai/configuration-guide/notifications.md) alert you when a specific issue or log is created, monitoring watches for **spikes** — sudden increases in error volume or user impact over short time windows.

Monitoring rules are configured in **Pharos Admin → Monitoring** and operate exclusively on log records. When a spike is detected, Pharos creates an **Event** record and can trigger notification actions (Slack, Teams, PagerDuty, Email, Webhook).

{% hint style="info" %}
For conceptual details on how monitoring works, see [Monitoring Overview](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/monitoring.md).
{% endhint %}

***

## In This Section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>📋 Monitoring Rules</strong></td><td>Configure spike and user impact spike detection — thresholds, intervals, and field grouping.</td><td><a href="https://docs.pharos.ai/configuration-guide/monitoring/logs.md">Logs</a></td></tr><tr><td><strong>⚡ Governor Limits Monitoring</strong></td><td>Set up governor limit monitoring for API usage, storage capacity, and CPU time.</td><td><a href="https://docs.pharos.ai/configuration-guide/monitoring/limits.md">Limits</a></td></tr><tr><td><strong>📊 Event Monitoring</strong></td><td>Configure Salesforce Event Monitoring for security and compliance events.</td><td><a href="https://docs.pharos.ai/configuration-guide/monitoring/events.md">Events</a></td></tr></tbody></table>

***

{% hint style="info" %}
**Start simple:** Create one spike rule with a threshold of 10 errors in 1 minute, grouped by the `Hash 1` fingerprint field. This catches any single issue that suddenly starts failing at high volume — a common indicator of outages or integration failures. Add user impact rules and limit monitoring as you mature.
{% endhint %}
