Showcase Your Grafana Skills with a GitHub README Badge

Use this markdown in your README:

![Grafana](https://img.shields.io/badge/Grafana-F46800?style=for-the-badge&logo=grafana&logoColor=white)

The #F46800 is Grafana's official orange from their brand guidelines. The grafana logo identifier renders Grafana's distinctive logo from Simple Icons. This orange badge naturally pairs with Prometheus (the most common Grafana data source) and Kubernetes in a DevOps and monitoring-focused profile.

Grafana proficiency ranges from consumer to creator of dashboards:

• Dashboard building: Creating panels with time-series, stat, gauge, bar chart, and table visualizations
• Query language: Writing PromQL (for Prometheus), Elasticsearch DSL, SQL, or Flux (for InfluxDB) within Grafana panels
• Alerting: Grafana Unified Alerting with notification channels (Slack, PagerDuty, OpsGenie)
• Templating: Dashboard variables for dynamic filtering by environment, region, or service
• Annotations: Marking deployments and incidents on time-series graphs for correlation
• Grafana as Code: Provisioning dashboards via YAML (Grafana Provisioning) or Grafonnet/Jsonnet
• Loki integration: Log visualization alongside metrics from Prometheus

Building dashboards that tell a coherent operational story — not just throwing all metrics on a single panel — demonstrates data visualization judgment beyond raw technical capability.

Grafana is the visualization layer for multiple data backends:

• Cloud-native stack: Grafana + Prometheus + Loki + Alertmanager + Kubernetes
• Time-series stack: Grafana + InfluxDB + Telegraf
• Database monitoring: Grafana + PostgreSQL + Redis + Elasticsearch
• Business intelligence: Grafana + PostgreSQL/MySQL + custom SQL dashboards

Grafana's scope has expanded significantly beyond infrastructure monitoring — it is now used for business metrics dashboards, IoT data visualization, and even database query results visualization. Mentioning non-standard Grafana data sources in your experience (like PostgreSQL business metrics or custom API data sources) signals versatility beyond the typical Prometheus-only Grafana usage.

Grafana dashboard configuration is stored as JSON — GitHub does not count JSON in language statistics. Grafana provisioning files (YAML) are also invisible to language counters. However, repositories containing organized Grafana dashboard JSON files and provisioning configurations demonstrate infrastructure-as-code practices for observability.

For pinned repositories, a monitoring stack repository with Grafana dashboards (stored as version-controlled JSON), Prometheus configuration, and Docker Compose setup is a complete DevOps portfolio piece. Include screenshots of your Grafana dashboards in the README — visual evidence of well-designed operational dashboards communicates monitoring expertise far more effectively than code listings.