Docs

Analytics

What this screen is for

Analytics turns individual deployments into trends: how often you ship, how often it goes wrong, how long recovery takes, and who is doing what. It answers the questions a single environment page cannot — is this getting better?

Before you start

To do this You need
Open the page env-by-branch.dev.workflow.read

Data accumulates from deployment and workflow history, so a new install shows little until it has run for a while. An empty chart on a fresh platform is expected, not broken.

Opening it

  1. Deploy › Analytics in the sidebar.

Direct URL: /ebb/analytics

The shortcut in the environment header is stale

Every environment dashboard shows an Analytics icon that is greyed out with the tooltip “Analytics - Coming Soon”. That button is out of date — Analytics has shipped. Use the sidebar entry.

The interface

📸 Screenshot Placeholder: The Analytics dashboard on the DORA Metrics tab. Mark: (1) the four tabs, (2) a metric card with its delta indicator, (3) the chart area.

Tab What it answers
Environment History What has happened to environments over time
DORA Metrics Deployment frequency, lead time, change failure rate, time to restore
Deployment Overview Volume and outcome of deployments
User Activity Who is deploying, and how much

Metrics show a delta against the previous period. The delta is usually more useful than the absolute number — “twelve deployments” means nothing on its own; “twelve, down from thirty” means something.

Walkthroughs

Check whether reliability is improving

  1. Deploy › Analytics › DORA Metrics.
  2. Read change failure rate and time to restore together. Frequency going up while failure rate holds steady is a genuine improvement; frequency up and failure rate up is just more deployments.

Find out what has been happening to an environment

Environment History — use this when someone asks “when did staging start misbehaving?” and nobody kept notes.

See who is deploying

User Activity — useful for spotting a bus factor of one, or a team that has stopped shipping without anyone noticing.

Scenario

Preparing for a quarterly review, without cherry-picking.

  1. DORA Metrics — take all four. Reporting deployment frequency alone is the classic mistake: it is the easiest to improve and the least meaningful on its own.
  2. Deployment Overview — get the volume and the outcomes. This is where a rise in frequency is revealed as either real throughput or repeated retries of the same failing deployment.
  3. Environment History — pick out the incidents. Line them up against the failure-rate trend so the numbers have a story attached.
  4. User Activity — check the load is spread. A team where one person performs every deployment has a risk that no DORA metric surfaces.
  5. Note where data is thin. A metric with two data points is not a trend, and presenting it as one is how a review produces a bad decision.

When it doesn’t work

Symptom Cause How to check Fix
Analytics is not in the submenu Missing env-by-branch.dev.workflow.read Access Explorer Ask for a role granting it
The in-environment Analytics button is greyed out Stale UI — the button says “Coming Soon” although the page has shipped — Use the sidebar entry
Charts are empty Not enough history yet How long the install has been running Expected on a new install
Numbers look wrong after adding an environment The new environment contributes its own history Environments Compare like-for-like periods
A metric moved sharply with no obvious cause Often a retry storm rather than real change Deployment Overview Read volume and outcome together

Next