> For the complete documentation index, see [llms.txt](https://chaincontext.gitbook.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chaincontext.gitbook.io/help-center/running/analytics-alerts.md).

# Analytics & Alerts

{% hint style="info" %}
Track usage, monitor performance, and get notified when thresholds are hit.
{% endhint %}

## Analytics dashboard

Your project's **Analytics** tab shows:

* **Tool calls** — total calls per day, per tool
* **Latency** — average response time by tool
* **Error rate** — failed calls as a percentage
* **Recent activity** — last 20 events with timestamps

Data refreshes every 5 minutes. Historical retention depends on your plan:

| Plan    | Retention |
| ------- | --------- |
| Free    | 7 days    |
| Builder | 14 days   |
| Studio  | 30 days   |

## Usage limits

Each plan has a daily tool call limit. Limits are **soft-enforced**:

1. At **80% usage** — you receive an email alert
2. At **100% usage** — new tool calls return a rate-limit error until the next UTC day

Resource reads and prompt fetches have separate, higher limits.

## Email alerts

Configure alerts in your project settings:

* **Limit 80%** — approaching daily tool call limit
* **Limit hit** — daily limit reached
* **Error rate** — error rate exceeds threshold (e.g., > 5% over 5 minutes)

Alerts are sent via email (Resend) or webhook (POST to your URL).

## Webhook alerts

For programmatic alerting, configure a webhook URL. ChainContext sends a POST request with:

```json
{
  "type": "limit_80pct",
  "projectId": "proj-xxx",
  "projectSlug": "my-project",
  "current": 8000,
  "limit": 10000,
  "timestamp": "2026-03-10T12:00:00Z"
}
```