Insights

Insights shows how reviews land across your organization. Every view has the same filters: a time range (presets or custom dates, up to a year), repositories, teams and authors. Hover the information mark next to any figure to see exactly what it counts and how many pull requests, findings or runs it is based on.

You see only the repositories you can read. When your organization shows analytics in aggregate only, per-author breakdowns are left out.

Views

View	What it shows
Overview	Median cycle time split into its stages, and pull requests reviewed, findings posted, findings accepted (fixed by a later commit or at merge, a resolved thread or a “fixed” reply, or agreed with by more 👍 than 👎; the same figure as on Home), time to first review, credits used, credits per pull request and merge-gate blocks, each against the period before.
Quality	How often findings are accepted, by category, severity and repository, over time; false positives from your team’s feedback; how many candidate findings the verifier stopped before posting; feedback, learning and knowledge use.
Velocity	Median and 90th percentile time from open to first review, to approval and to merge; review latency over time; pull requests opened and merged; each repository and team; and the slowest merges.
Risk	Change-risk scores and levels over time, hotspot files and modules by findings and lines changed, the code that calls what a pull request changes, and the merge gate.
Cost	Credits by work type and repository, the model spend behind reviews, and this month’s budget burn-down with a forecast. Credits by tier, cost per review and the budget itself are in Billing → Usage.
Teams	Teams or business units side by side: throughput, findings and acceptance, time to first review, cycle time and credits; adoption by source.

Overview, Quality, Velocity, Risk, Cost and Teams are part of advanced insights, included in the Team plan and above. The findings behind the figures are under Pull requests → Findings, and security trends under Security → PR reviews.

Every chart has a table view and a Download CSV button with exactly the rows it draws. Select a bar, a segment or a period to open the findings or pull requests behind it. The filters are in the address bar, so a link opens the same view for a colleague.

Time to first approval is recorded from code-host approval events and lines changed per file from reviews, so each starts filling in from when your organization runs this release. Business units come from Settings → Ownership.

Export

Choose Export data at the top of Insights, then pick a view or a raw table (reviews, findings, pull requests or usage) and CSV or JSON. The current filters apply.

• Views, and raw tables for up to 31 days, download straight away.
• Longer raw exports run in the background. They appear in the list with their status; the file can be downloaded for 7 days. Background exports need object storage on self-hosted installations.

Every download is recorded in the audit log.

Weekly email

Turn on Weekly email on the Exports tab to get last week’s numbers against the week before, every Monday morning (UTC). It covers the repositories you can read when it is sent, and you can turn it off from the same place or the link in the email.

API and BI tools

All views are available from the API (/api/v1/orgs/{org}/analytics/..., see the API reference). For a BI tool, create an API key under Settings → API keys and tick Insights only: the key gets the analytics.read scope and can read Insights views and downloads, nothing else. Use GET /api/v1/orgs/{org}/analytics/data?dataset=findings&format=csv&from=…&to=… to pull a table on a schedule.