Grafana — dashboards, variables, annotations and alert channels — CI/CD, GitOps, DevSecOps & Observability

Grafana is the standard visualisation layer for Prometheus, Loki, Jaeger, and dozens of other data sources, providing dashboards, alert rule management, and notification routing in a single platform. While Prometheus excels at collecting and querying metrics, its built-in expression browser is not designed for the multi-panel, interactive, real-time dashboards that operations teams need for incident response. Grafana transforms Prometheus queries into visualisations that tell a story: the request rate dropping, the error rate spiking, and the P99 latency climbing in the same time window confirm a single degradation event.

Four Grafana capabilities are essential for production observability: dashboard variables that make a single dashboard panel template work across all services and environments, annotations that mark deployment and incident events on time-series graphs for contextual correlation, provisioning that manages datasources and dashboards as code without manual UI configuration, and unified alerting with contact points and notification policies that route alerts to the right team through the right channel. Together they turn a Prometheus metric store into a complete observability platform.

Analogy🏏Cricket

Think of it like cricket: Imagine the BCCI's team management system for an international tour with matches in three different countries simultaneously. Rather than a coordinator manually managing each match day's logistics, the system reads the official tour schedule document and automatically dispatches the right squad, equipment, and support staff to each venue. When the tour schedule changes—a match is rescheduled, a squad member is replaced—the system detects the change and updates the arrangements automatically. Just as the tour management system uses the official document as the source of truth and orchestrates multiple concurrent deployments to multiple venues, ArgoCD uses the Git repository as the source of truth and orchestrates multiple concurrent Application syncs to multiple clusters. Just as the system provides a dashboard showing which venues are 'ready', 'delayed', or 'degraded', ArgoCD provides a dashboard showing which Applications are Synced, OutOfSync, or Degraded. This reveals why ArgoCD is valued at scale: managing dozens of applications across multiple clusters manually is operationally equivalent to coordinating an international cricket tour by phone.