Skip to content

DevOps dashboards

DevOps dashboard examples

Three dashboards for an engineering team: the four DORA measures by team with the incidents behind them, whether roadmap work is on track, and where engineering effort goes against plan. Open any of them to see it in full, then use it as a template for your own data.

Project Status dashboard: Percent Complete, Actual Hours, Budget and Cost Variance tiles, above Status by project.
Project Portfolio dashboard: Budget, Actual Cost, Cost Variance and Percent Complete tiles, above Budget by portfolio.
Engineering Delivery dashboard: Deploys, Lead time (hours), Change failure rate, Time to restore (hours) and Incidents tiles.

All figures are sample data.

The examples

Three DevOps dashboard examples and templates

Click a board to see all of it. Click Use template to start your own copy in Mammoth. All figures are sample data.

  1. Engineering Delivery dashboard: Deploys, Lead time (hours), Change failure rate, Time to restore (hours) and Incidents tiles.
    Sample data

    DevOps dashboard

    How often does each team ship, and how often does a release break?

    • Deploys
    • Lead time (hours)
    • Change failure rate
    • Time to restore (hours)
    Use template
  2. Project Status dashboard: Percent Complete, Actual Hours, Budget and Cost Variance tiles, above Status by project.
    Sample data

    Engineering roadmap status dashboard

    Is the roadmap work on track?

    • Percent complete
    • Actual hours
    • Budget
    • Cost variance
    Use template
  3. Project Portfolio dashboard: Budget, Actual Cost, Cost Variance and Percent Complete tiles, above Budget by portfolio.
    Sample data

    Engineering effort dashboard

    Is engineering effort going where it was planned?

    • Budget
    • Actual cost
    • Cost variance
    • Percent complete
    Use template

Definition

What a DevOps dashboard is

A DevOps dashboard is one screen that shows how well an engineering organisation ships software: how often each team deploys, how long a change waits between commit and production, how often a release breaks something, and how long it takes to recover. The data usually comes from the CI/CD pipeline, the Git host and the incident tool.

  • The four DORA measures

    Deploys, lead time, failure rate and restore time.

  • By team

    One fast, fragile team cannot hide in the average.

  • From your tools

    CI, Git and incident exports, joined once.

The metrics

The metrics a DevOps dashboard is built from

Eight numbers. Most depend on a definition agreed first, such as what counts as a failed deploy.

  • Deployment frequency

    How often does each team ship?

    What the data needs

    One row per production deploy with team and time. Count deploys, not merges, because a merge that waits a week has not shipped.

  • Lead time for changes

    How long does a change wait to reach production?

    What the data needs

    Commit time and the time of the deploy that shipped it. Use the median, since one forgotten branch distorts the average.

  • Change failure rate

    How often does a release break something?

    What the data needs

    Deploys and the ones that needed a fix or rollback. Agree the rule once, or each team counts failure its own way.

  • Time to restore

    How long does recovery take?

    What the data needs

    Incident start and resolution times. Clock it from when users were hurt, not from when someone noticed.

  • Incidents

    How many things went wrong in production?

    What the data needs

    Incidents by team, service and severity from the on-call or incident tool.

  • Changes merged

    How much work is flowing through?

    What the data needs

    Merged pull requests by team and week. More merges with flat deploys means changes are queueing.

  • Work in progress

    How much is started but not done?

    What the data needs

    Open tickets by status from the tracker. Too much in progress slows everything else.

  • Planned against unplanned work

    How much time goes on fixes and support?

    What the data needs

    Effort tagged as planned or unplanned. Unplanned work that grows quarter on quarter is the roadmap shrinking.

How to build one

How to build your own DevOps dashboard

From one of the examples above to a live dashboard on your own data.

  1. 1

    Pick a template

    Start from any of the three boards above.

  2. 2

    Add your data

    Upload a spreadsheet, or connect one of 100+ tested connectors.

  3. 3

    Clean it once

    Fix and combine your data once. Mammoth repeats those steps for you.

  4. 4

    Set it to refresh

    The dashboard updates on a schedule and flags data that fails a check.

  5. 5

    Share the link

    Public, password-protected or sign-in only, on every plan.

Start with a template

14-day Pro trial · No credit card

FAQ

DevOps dashboard questions

Last reviewed against the template catalogue.

What should a DevOps dashboard show?
How fast and how safely changes reach production. That means deploy frequency, lead time for changes, change failure rate and time to restore by team, with the incidents behind them. The first board covers those; the others show whether planned work is moving.
What are the DORA metrics?
Four measures from the DevOps Research and Assessment programme: deployment frequency, lead time for changes, change failure rate and time to restore service. Two measure speed and two measure stability, which is why they belong on one board.
How do I build a DevOps dashboard?
Start with deploys, the measure every pipeline already logs. Then follow five steps.
  1. Export deployments from the CI/CD tool with team, service, time and outcome.
  2. Join each deploy to the commits it shipped, for lead time.
  3. Export incidents with their start, end and the deploy that caused them, where known.
  4. Check one week's deploy count against the pipeline before anyone relies on the board.
  5. Refresh daily, and give each team a view filtered to its own services.
Should DORA metrics compare teams?
Compare a team with its own past first. Teams own different systems, and a payments team should deploy more carefully than an internal tools team. The by-team charts are there to spot a team that is struggling, not to rank them.
Where does DevOps data come from?
Usually GitHub or GitLab, a CI/CD tool, an incident or on-call tool, and Jira for planned work. Mammoth has 100+ tested connectors, and can also connect to anything with a REST API. You combine the sources once, and Mammoth repeats the same steps on every refresh.
Can every engineer see it without a licence?
Yes. Dashboard viewers are unlimited and free on every Mammoth plan, including the free one, so every engineer and manager can open it at no per-viewer cost. Only the people building the dashboards count as platform users.

Build the DevOps dashboard you actually need.

Start from one of these templates or your own spreadsheet. Share it with as many people as you like, free.

  • ✓ 14-day Pro trial
  • ✓ No credit card
  • ✓ Viewers always free