---
title: "Grafana | Skills We Assign For | Azendo"
description: "Grafana as a dashboard layer — dashboards people actually use, and the Azendo roles assigned for observability work."
url: "https://azendo.co/skills/grafana/"
---

[Skills](https://azendo.co/skills/) Observability 

# Grafana.

Grafana is an open-source dashboarding and alerting tool that visualises data from many sources — Prometheus, cloud metrics, databases and logs — in one place. It is the display layer rather than the collection layer.

## Where Grafana fits on a long engagement.

Because Grafana reads from whatever you already have, it avoids a migration. That is its main practical advantage and the reason it survives in estates that have changed monitoring backends twice.

Most Grafana installations accumulate dashboards nobody looks at. A useful one answers a specific question — is the service healthy, is the queue draining, did the release change anything — and dashboards built to display everything answer none of them. Pruning is more valuable than adding.

## What an assigned team does with Grafana.

Dashboards accumulate faster than they are read. A panel built for one incident three years ago is still on the wall, and the view somebody actually needs at 3am is four clicks away behind twelve that nobody uses.

Curation is the work, and it needs somebody who knows which questions get asked. That is a reliability assignment rather than a tooling one, scoped under [DevOps managed services](https://azendo.co/services/cloud-and-devops/).

## What we use Grafana for.

* One dashboard per real question Replacing a wall of panels with views that support an actual decision during an incident.
* Dashboards as code Definitions version-controlled so they can be reviewed and restored, not rebuilt from memory.
* Alerting on symptoms Alerts tied to what users experience rather than to every underlying metric.

## How Grafana capacity is assigned.

Dashboard and alerting work is assigned under DevOps as a service, alongside whichever collection stack you already run. The four steps from brief to first sprint are described in [four steps](https://azendo.co/how-it-works/).

## Roles we assign Grafana for

* [Site Reliability Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/site-reliability-engineer/)
* [Performance Test Engineer QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/performance-test-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)
* [QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in observability

* [New Relic — skill we assign for](https://azendo.co/skills/new-relic/)
* [APM — skill we assign for](https://azendo.co/skills/apm/)
* [distributed tracing — skill we assign for](https://azendo.co/skills/distributed-tracing/)
* [Database query profiling — skill we assign for](https://azendo.co/skills/database-query-profiling/)
* [SLO and error budget design — skill we assign for](https://azendo.co/skills/slo-and-error-budget-design/)
* [Prometheus — skill we assign for](https://azendo.co/skills/prometheus/)
* [OpenTelemetry — skill we assign for](https://azendo.co/skills/opentelemetry/)
* [CloudWatch — skill we assign for](https://azendo.co/skills/cloudwatch/)

## Tell us what your roadmap needs Grafana for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)