Analytics & Reporting
Isurus provides built-in analytics powered by a QuestDB time-series backend. Metrics are collected automatically as you push code, open issues, merge pull requests, and run CI pipelines. No extra configuration is needed to start collecting data.
Overview
Analytics are organized into these categories:
- Velocity — commit and contributor activity, pull request throughput
- Issues — open/close rates, backlog trends, response times
- CI/CD — pipeline success rates, average durations, compute minutes used
- Traffic — VCS pull (clone/fetch) and push activity over the wire
- Releases — published release frequency, asset download rate, and top assets
- People — top committers, issue closers, and PR mergers for the selected range
Metrics are collected automatically and queried on demand when you view a dashboard.
Viewing Analytics
Repository Analytics
Navigate to any repository and click the Analytics tab in the repository navigation bar. The repository dashboard shows metrics scoped to that single repository.
Organization Analytics
Navigate to any organization and click Analytics in the organization navigation bar. The organization dashboard aggregates metrics across all repositories in the organization.
2D and 3D Views
Every analytics dashboard — both repository and organization — offers two ways to view the same data. A 2D / 3D toggle sits at the top of the Analytics tab:
- 2D (default) — the standard flat dashboard of charts, tables, and summary cards described throughout this page.
- 3D — an interactive, fly-around view that renders the same metrics as navigable 3D charts. Drag to orbit, scroll to zoom, and use the arrow keys to move between charts; press Esc to return to the 2D dashboard.
Both views draw from the same underlying metrics and honor the same time range selector, so switching between them never changes what you are looking at — only how it is presented. The 3D view follows your active light/dark theme. Analytics (in either view) is visible to organization members; the toggle appears only on the Analytics tab.
If QuestDB is not configured on your instance, analytics degrade gracefully and the dashboards appear empty rather than erroring.
Time Range Selector
All analytics dashboards include a time range selector at the top of the page. Choose from:
| Range | Description |
|---|---|
| 7d | Last 7 days |
| 30d | Last 30 days (default) |
| 90d | Last 90 days |
| 1y | Last 12 months |
| All | All available data |
Changing the range updates all charts and summary cards on the page immediately.
Available Metrics
Velocity
Velocity metrics measure development activity over time.
| Metric | Description |
|---|---|
| Commits | Number of commits pushed, grouped by day or week |
| Active contributors | Unique authors who pushed commits in the period |
| Pull requests opened | PRs created in the period |
| Pull requests merged | PRs merged in the period |
| Merge time (median) | Median time from PR open to merge |
The commit chart shows a bar graph over the selected time range. Hovering over a bar shows the exact count and date.
Issues
Issue metrics track the health of the issue tracker.
| Metric | Description |
|---|---|
| Issues opened | New issues created in the period |
| Issues closed | Issues transitioned to Closed state |
| Backlog | Count of Open issues at the end of the period |
| Response time (median) | Median time from issue creation to first comment |
| Resolution time (median) | Median time from issue creation to close |
The backlog trend line shows how the count of open issues has changed over time.
CI/CD
CI/CD metrics help you understand pipeline health and resource usage.
| Metric | Description |
|---|---|
| Success rate | Percentage of pipelines that completed successfully |
| Average duration | Mean pipeline duration (wall clock) |
| Compute minutes | Total CI minutes consumed across all pipelines |
| Pipelines run | Total number of pipelines executed |
| Failure rate by step | Which steps fail most often (repo and org views) |
The success rate is displayed as a gauge and as a trend line over the selected time range.
Traffic
Traffic metrics count VCS wire operations (HTTP and SSH), not web pageviews.
| Metric | Description | Surfaces |
|---|---|---|
| Pull & push rate | Pulls and pushes per day (or coarser bucket for longer ranges) | Repo, org, admin |
| Top repositories | Repos ranked by total pull+push count in the selected range | Org (within org), admin (instance-wide) |
A pull is recorded when a client clones or fetches; a push when history is uploaded. Anonymous public clones are included (with no user id). Counts appear after the analytics relay writes staged events into QuestDB (typically within about a minute).
Releases
Release metrics track how often you publish and how often assets are downloaded.
| Metric | Description | Surfaces |
|---|---|---|
| All-time downloads | Sum of per-asset download_count from Postgres (not limited by the range selector) |
Repo, org, admin |
| Release frequency | Published releases per day (or coarser bucket for longer ranges); draft creates are excluded | Repo, org, admin |
| Download rate | Attachment downloads per day over the selected range | Repo, org, admin |
| Top downloaded assets | Assets ranked by download count in the selected range | Repo, org, admin |
All-time totals come from the existing Postgres counters on each release attachment, so the summary card is useful immediately even before time-series history has accumulated. Frequency and download-rate charts appear after the analytics relay writes staged release / release_download events into QuestDB (typically within about a minute). Anonymous asset downloads are included.
People
People leaderboards rank who contributed most in the selected time range. Available on repository, organization, and admin analytics.
| Leaderboard | Description | Identity |
|---|---|---|
| Top committers | Authors ranked by commit count | VCS author string from the commit (name/email as recorded by Git/Hg/Fossil). Not necessarily a forge account. |
| Top issue closers | Users ranked by issues closed | Forge user (actor_id → display name) |
| Top PR mergers | Users ranked by pull requests merged | Forge user (actor_id → display name) |
Identity caveats
- Commit authors ≠ forge users. A person can appear under several committer strings (different emails, bots, force-pushed rewrites). Matching author strings to accounts is not performed on this tab.
- Issue closers and PR mergers are forge accounts that performed the close/merge action in the UI or API. They may differ from the person who authored the commits in the merged PR.
- Empty tables mean no events of that type in the range (or analytics has not yet relayed events into QuestDB). Counts appear after the relay flush (typically within about a minute).