# EvoTrail overview

EvoTrail gathers what happens across your EvoHub organization in one place. Its **Metrics** tabs show each product's numbers for a period you pick — alerts and response times, uptime, status page and docs readers, finished cards, retros held, spend — and its **Audit Logs** list who did what, in every product. This page covers Metrics; see [Audit Logs](https://docs.evohub.io/evotrail-audit-logs.md) for the trail.

Reading EvoTrail is free: it is never metered.

## Open EvoTrail

- Open the **Services** menu in the top bar and choose **EvoTrail**.
- On the home page, use the **EvoTrail** card under **Your Services**, or add the **EvoTrail** shortcut to **Quick actions** (see [Your home page](https://docs.evohub.io/your-home-page.md)).
- In a product, a link to EvoTrail (such as **View in EvoTrail**) opens that product's tab. From a docs site, changelog, status page or monitor, the tab opens already narrowed to it.

The products' own analytics screens have moved here. An old link to a docs site's, changelog's or status page's **Analytics** screen opens its EvoTrail tab instead.

## The tabs

The left-hand navigation lists **Overview**, **Usage**, and a tab for every product you may read, then **Audit Logs** under **Trail**.

| Tab | What it shows |
| --- | --- |
| **Overview** | What needs a look, each product's headline numbers, the incidents of the period and what they did to your status pages, and a timeline. |
| **Usage** | How much each product is used: actions, active people and teams, top actions and products nobody used. |
| **On-Call** | Alerts by severity, time to acknowledge and resolve, noisiest alerts and integrations, flapping alerts, notifications by channel, responder load (including off-hours and sleep-hours pages), incidents and postmortems. |
| **Uptime** | Uptime over time, every monitor with its SLA target, worst monitors, response time (typical and slowest 5%), downtime and time to recover, uptime by team. |
| **Status Pages** | Views and visitors per day, feed reads, AI readers, page types, product pages, subscriber growth and the incidents each page told its readers about. |
| **Docs** | Per site: **Overview**, **Search**, **AI readers**, **Feedback** and **Content gaps** (searches that found nothing and missing pages readers hit), filtered by version and language. |
| **Changelog** | Per changelog: views and visitors, What's new widget opens and clicks, reactions, feedback, feed reads, AI readers, entries, emails sent and subscriber growth. |
| **Board** | Cards finished per week, cycle time, cumulative flow, work in progress per list, overdue cards, review results and work by person. |
| **Retro** | Retros held by team, participation, cards, votes and comments, and action items created and completed. |
| **Billing** | Usage in the range, charged so far this month, free allowance left, the month-end estimate, EHU per day by product and spend per month. |

A product tab is offered only to people who may read that product, and each tab reads with your own permissions. **Billing** is shown only to people who hold the billing usage permission. A part of a tab that is not available yet says **Coming soon** instead of showing a guessed number.

## Pick the period

The bar at the top of every Metrics tab sets what all of its cards show:

- **Date range**: **Last 7 days**, **Last 30 days**, **Last 90 days**, **Last 12 months** or **Custom range**. A custom range can be up to 366 days. Ranges are whole days in UTC.
- **Compare with**: **No comparison**, **Previous period** (the same length just before) or **Same period last year**. Numbers then show their change against it, and some charts draw it as a dashed line.
- **Team** (on Overview, Usage, On-Call, Uptime, Board and Retro): **All teams**, **Organization-wide only**, or one team.
- **Share view** copies a link to exactly this view. Teammates who open it see it with their own permissions.

Under the bar, each product tab says how far back its data goes, for example "Daily figures are kept for 400 days; individual checks for 90".

## Overview

- **The attention line** appears only when something in the period needs a look: incidents opened, monitors that missed their SLA, monitors down right now.
- **Product cards** show each product's headline numbers with their change and a small trend, for example alerts and the median time to acknowledge, or cards finished and the median time to finish one. **Open →** goes to the product's tab. A product you have not started using says **Not in use yet** with a **Set it up** link.
- **Incident impact** lists every incident in the range: severity, when it started, time to acknowledge, time to resolve, how long until customers were told on a status page, status page views during the incident against the same hours a week earlier, new subscribers, monitor downtime on the same days, and the postmortem's state.
- **Timeline** puts incidents and monitor downtime above status page, docs and changelog views on one time axis, with changelog releases marked, so you can see what customers read while something was wrong. Each row has its own scale.

## Usage

**Usage** is built from the audit trail. It counts everything people, API keys and automation did in the products you can read:

- **Usage at a glance**: **Actions**, **Active people**, **Products in use** and **Quiet products**.
- **Actions per product** over time. Click a bar to open the Audit Logs at that time.
- **By product**: actions, change against the previous period, people and when the product was last used. Open a product to see its rows in the Audit Logs.
- **Top actions** and **Most active teams**.
- **Most active people**, visible to organization owners and administrators only, whatever a role holds.
- **Quiet products**: products you can read that nobody used in the period.

## AI readers

Status pages, docs sites and changelogs count how AI assistants and crawlers read them. Two numbers are kept:

- **AI reads** count each page once per assistant per day. A crawler fetching the same page, or `llms-full.txt`, fifty times in a day is one read; two pages, or two assistants on one page, are two.
- **AI requests** count every fetch.

The **AI readers** number shows reads. Its explanation gives the raw requests too, and says how many days of the period come from before reads were counted; those days count every request.

## Download a PDF report

Select **Download PDF** above any Metrics tab and choose **All products** or **Only** one product. The report uses the range, comparison, team and filters you have on screen, and includes only the products you may read. If none of them is yours to read, no PDF is made.

## CSV

Most cards and tables have a **CSV** button that downloads exactly the rows shown.

## How long data is kept

| Data | Kept for |
| --- | --- |
| Audit trail: changes | 365 days |
| Audit trail: activity, such as moving a card | 90 days |
| IP addresses and browser details on audit events | 90 days |
| On-Call alerts and their notifications | 1 year |
| Uptime daily figures | 400 days |
| Uptime individual checks (needed for latency detail) | 90 days |
| Status page, docs and changelog visit figures | Each site's own setting, 365 days unless changed |
| Docs page feedback | 2 years |
| Board cards and their activity | While the board exists; archived cards still count |

The audit trail periods are the same for every organization and cannot be changed.

## Permissions

| To | You need |
| --- | --- |
| Open EvoTrail's Metrics | `evotrail:metrics:read` (every default role), and for each product tab that product's read permission |
| Open the Billing tab | `billing:usage:read` |
| See **Most active people** | Organization owner or administrator |
| Open Audit Logs | `evotrail:audit:read` (Owner, Admin and Member by default) — see [Audit Logs](https://docs.evohub.io/evotrail-audit-logs.md) |

To read the same data with an API key, see the [EvoTrail API](https://docs.evohub.io/evotrail-api.md).

## Related

- [Audit Logs](https://docs.evohub.io/evotrail-audit-logs.md)
- [EvoTrail API](https://docs.evohub.io/evotrail-api.md)
- [Roles and permissions](https://docs.evohub.io/roles-and-permissions.md)
- [How billing works](https://docs.evohub.io/how-billing-works.md)