Preparing for a DevOps interview that covers Grafana? These questions come up again and again - here are strong, concrete answers.
Q: What is Grafana and why use it?
Grafana visualizes data from Prometheus, Loki, Elasticsearch and dozens of other sources in shared dashboards, and unifies alerting across them - dashboards defined as code where you want it.
- One pane of glass across metrics, logs and traces
- Dashboards and alerts as code (provisioning) for reproducibility
- A vast library of community dashboards to start from
Q: What are the best practices you follow?
- Provision data sources and dashboards as code from Git
- Design a few focused dashboards per service, not one giant wall
- Standardize variables and folders so teams find things fast
Q: What mistakes have you seen?
- Click-built dashboards that live only in the database and vanish on rebuild
- Overloaded dashboards nobody can read during an incident
- Alerting split between Grafana and other tools with no clear owner
Q: Show a basic configuration
Provision a data source as code so it is reproducible.
# provisioning/datasources/prometheus.yaml
apiVersion: 1
datasources:
- name: Prometheus
type: prometheus
access: proxy
url: http://prometheus:9090
isDefault: trueWant senior help putting Grafana to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.