Built-in dashboards are intentionally persona-driven. They are not random collections of charts.
What they are for
Each built-in dashboard is meant to answer a familiar kind of question, such as:
- Are failures rising?
- Which repositories are becoming noisy or unstable?
- Where is queue delay or runner waste dragging delivery?
- What needs immediate attention right now?
How to choose the right one
- Start with the dashboard that matches the decision you are trying to make.
- Use overview-oriented dashboards when you want a broad operating picture.
- Use more diagnostic dashboards when you already know something feels wrong and you need detail.
What built-in dashboards are not
They are not meant to cover every possible slice of data for every team. When the built-in dashboards prove the product has the signal you need, custom dashboards are where you shape that signal around your own workflows and ownership boundaries.
Ready to use the product?
Jump from the docs into the app.
If you already have the GitHub App installed, open ActionWatch now and start with real data. If not, install the app first and come right back.