# Analytics

The Analytics page provides aggregated metrics and charts that summarize your project's traffic patterns, rule effectiveness, and performance over time.

## Key metrics

The following KPIs are displayed at the top of the Analytics page:

| Metric                 | Description                                                                                  |
| ---------------------- | -------------------------------------------------------------------------------------------- |
| **Total requests**     | The total number of API calls processed in the selected time range.                          |
| **Blocked rate**       | The percentage of requests that were blocked by inbound or outbound rules.                   |
| **Error rate**         | The percentage of requests that resulted in an error.                                        |
| **P95 latency**        | The 95th percentile response time, meaning 95% of requests completed faster than this value. |
| **Rule trigger count** | The total number of times any rule was triggered across all requests.                        |

## Using the Analytics page

1. **Select a project** using the project selector at the top of the page (same pattern as the Logs page).
2. **Choose a time range** to control the period of data shown in all metrics and charts.
3. **Review the KPI cards** for a high-level summary.
4. **Examine the charts** to see how each metric trends over time within the selected range.

## What to look for

Analytics helps you answer common operational questions:

* **Monitor traffic patterns** — See how request volume changes throughout the day or week. Identify peak usage periods.
* **Track rule effectiveness** — Check the blocked rate and rule trigger count to understand how often your rules are firing and whether they are catching the traffic you expect.
* **Identify spikes in blocked requests** — A sudden increase in the blocked rate may indicate a new pattern of misuse, or it may mean a rule is too aggressive and needs tuning.
* **Spot performance issues** — Watch the P95 latency metric for degradation. If latency is climbing, it may point to upstream model slowdowns or increased payload sizes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.collieai.io/monitoring/analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.