> ## 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, 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** tab. It has two tabs: **PR Reviews** (review activity and quality metrics) and **Bugs Caught** (a searchable table of every issue Greptile has flagged). ![Analytics dashboard overview](https://mintcdn.com/greptile/K-FC2J_U4wd5OfKX/images/analytics-dashboard.png?fit=max\&auto=format\&n=K-FC2J_U4wd5OfKX\&q=85\&s=b49122f5744d3625d96b7c34a2bcc783) Analytics dashboard ## 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 | This week, This month, This quarter, This year, All time, Custom | | 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 | | - | - | | **Total PRs** | Reviewed pull requests merged in the selected period | | **Total Reviews** | Reviews Greptile ran in the selected period | | **Avg Merge Time** | Average time from PR open to merge | | **# of bugs caught** | Bugs Greptile flagged, and in how many repos | ## Charts Each chart pairs a time series with a leaderboard sidebar for that metric. ### PRs Reviewed by Greptile A time series of pull requests reviewed per day. Switch the metric between **PRs reviewed**, **Total reviews**, **Avg reviews / PR**, **Median comments / PR**, and **Mean comments / PR**. The leaderboard shows **Top Repos by Review Count**, or **PRs With Most Comments** for the comments-per-PR metrics. ### Bugs Caught Tracks issues flagged over time, stacked by severity. Filter by severity level: | Severity | Description | | - | - | | All Severity | All issues regardless of priority | | P0 | Must fix before merge: security, data-loss, or severe crash risk | | P1 | Real defect in changed code | | P2 | Non-blocking quality feedback | The leaderboard shows **Repos with most bugs**. **See all bugs caught** opens the Bugs Caught tab. ### Average Time to Merge Tracks how long PRs take to merge. Toggle between **Mean** and **Median**. The leaderboard shows **Top Repos by Merge Time**. ### Top Contributors Merged PRs split by PR author. The leaderboard lists the top contributors and the repositories they shipped to. ### Addressed Rate The percentage of Greptile comments on closed or merged pull requests that were addressed — by follow-up code changes or positive feedback (marked helpful, positive reaction, or net upvotes). Shown over time with an average trend line. The leaderboard shows **Top repos by addressed rate**. ### Comment Ratings Upvote and downvote totals for Greptile's review comments, with a ratings chart over time. The leaderboard shows **Most Upvoted Comments**. ## Bugs Caught tab Stat cards break findings down by severity — **All bugs**, security issues, **P0**, **P1**, and **P2** — above a table of every finding. | Column | Description | | - | - | | Finding | The issue Greptile flagged | | Severity | P0, P1, or P2, plus a security marker | | Pull request | Repo and PR where it was flagged | | Status | Open or Addressed | | Date | When it was flagged | Search by text, repo, PR title, author, or file. Filter by severity, security, status, repo, or author. Click a row to open the finding on its pull request (findings from CLI or branch reviews have no pull request link). ## Using analytics to improve reviews * **Low addressed rate?** Your rules may be too noisy. [Adjust strictness](https://www.greptile.com/docs/code-review/controlling-nitpickiness.md) or refine [custom standards](https://www.greptile.com/docs/code-review/custom-standards.md). * **High 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](https://www.greptile.com/docs/code-review/custom-standards.md) rules and [train the learning system](https://www.greptile.com/docs/code-review/training-the-learning-system.md) with consistent reactions. * **Long merge times?** Identify bottleneck repos from the leaderboard and investigate process or review load issues. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.