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

# Analytics Dashboard

> Track code review metrics across your organization: PRs reviewed, merge times, addressed rates, critical bugs caught, and upvote/downvote ratios.

The Analytics dashboard gives you visibility into review activity, comment quality, and team performance. Access it from the **Analytics** link in the sidebar.

<Frame>
  <img src="https://mintcdn.com/greptile/K9D4AfJzUy9sOdP6/images/analytics-dashboard.png?fit=max&auto=format&n=K9D4AfJzUy9sOdP6&q=85&s=d822c7e2bced2febb0a49a6aece38de7" alt="Analytics dashboard overview" width="2400" height="1342" data-path="images/analytics-dashboard.png" />

  <figcaption>Analytics dashboard</figcaption>
</Frame>

## Filters

Use the filter bar at the top to scope analytics data.

| Filter       | Options                                               | Notes                   |
| ------------ | ----------------------------------------------------- | ----------------------- |
| Teams        | All teams, or select specific teams                   | Organization level only |
| Repositories | All repositories, or select specific repos            |                         |
| Authors      | All authors, or select specific authors               |                         |
| Time period  | Last 7 days, Last 30 days, Last 60 days, Last 90 days |                         |

Click **Export** to download the current analytics data.

At the team level, the Teams filter is hidden since data is already scoped to that team.

## Summary cards

Four headline metrics appear at the top:

| Metric                   | Description                                                     |
| ------------------------ | --------------------------------------------------------------- |
| **PRs Reviewed**         | Total pull requests reviewed by Greptile in the selected period |
| **Avg Merge Time**       | Average time from PR open to merge                              |
| **Addressed rate**       | Percentage of Greptile comments that were addressed by authors  |
| **Critical bugs caught** | Number of critical issues flagged by Greptile                   |

## Charts

Each chart includes a time series and a leaderboard sidebar showing the top repositories for that metric.

### PRs reviewed

A time series of pull requests reviewed per day. The leaderboard shows **Top repos by review count**.

### Critical bugs caught

Tracks critical issues flagged over time. Filter by severity level:

| Severity     | Description                       |
| ------------ | --------------------------------- |
| All Severity | All issues regardless of priority |
| P0           | Highest severity                  |
| P1           | High severity                     |
| P2           | Medium severity                   |

The leaderboard shows **Repos with most critical bugs**.

### Addressed rate

Shows the percentage of Greptile comments addressed by PR authors over time, with an average trend line. The leaderboard shows **Top repos by addressed rate**.

### Average time to merge

Tracks how long PRs take to merge. Toggle between **Mean** and other aggregation methods. The leaderboard shows **Top repos by merge time**.

### Greptile comments

Displays upvote and downvote percentages for Greptile's review comments, with a ratio chart over time. Switch between **Upvote/Downvote Ratio** and other comment metrics. The leaderboard shows **Most upvoted comments**.

## Using analytics to improve reviews

* **Low addressed rate?** Your rules may be too noisy. [Adjust strictness](/code-review/controlling-nitpickiness) or refine [custom standards](/code-review/custom-standards).
* **High critical bug count in a repo?** Consider lowering the strictness threshold for that repo to catch more issues early.
* **High downvote ratio?** Review your [custom context](/code-review/custom-standards) rules and [train the learning system](/code-review/training-the-learning-system) with consistent reactions.
* **Long merge times?** Identify bottleneck repos from the leaderboard and investigate process or review load issues.