We generate a lot of dashboards acting as windows to the metrics we use to monitor GitLab.com. Most of our dashboards are generated from Jsonnet in the runbooks repository. Anyone can contribute to these, adding new dashboards or modifying existing ones.
When adding new dashboards for your stage groups, tagging them with
stage_group:<group name> cross-links the dashboard on other
dashboards with the same tag. You can create dashboards for stage groups
directory. Directories can’t be nested more than one level deep.
To see a list of all the dashboards for your stage group:
- In Grafana, go to the Dashboard browser.
- To see all of the dashboards for a specific group, filter for
Some generated dashboards are already available:
- Stage group dashboard: a customizable dashboard with tailored metrics per group.
- Error budget detail dashboard: a dashboard allowing to explore the error budget spend over time and over multiple SLIs.
By default, all the times are in UTC time zone. We use UTC when communicating in Engineering.
All metrics recorded in the GitLab production system have one-year retention.
You can also zoom in and filter the time range directly on a graph. For more information, see the Grafana Time Range Controls documentation.
On each dashboard, there are two filters and some annotation switches on the top of the page.
Some special events are meaningful to development and operational activities. Grafana annotations mark them directly on the graphs.
|filter||Filter the selective Prometheus data sources. The default value is |
|filter||Filter the environment the metrics are fetched from. The default setting is production (|
|filter||Filter metrics by stage: |
|annotation||Mark a deployment event on the GitLab.com SaaS platform.|
|annotation||Mark a canary deployment event on the GitLab.com SaaS platform.|
|annotation||Mark the time point when a feature flag is updated.|
Example of a feature flag annotation displayed on a dashboard panel: