Custom dashboards let you save focused views of ActionWatch instead of rebuilding the same filters every time.
Good uses for custom dashboards
- A dashboard for one team or service area
- A view centered on a small set of repositories
- A reliability-focused dashboard for unstable workflows
- A queue-pressure dashboard for a platform or developer productivity team
How to think about filters and date ranges
GraphQL-backed dashboard reads remain the source of truth. Filters and time ranges control which slice of that data the dashboard asks for; they are not separate copied datasets.
That means custom dashboards are best understood as saved product views, not exported reports. Keep them centered on repeat questions your team actually revisits.
When to keep using built-in dashboards
If the question is broad and common, the built-in dashboards are still the best default. Use custom dashboards when you keep narrowing to the same repositories, workflows, or patterns again and again.
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.