Course contentsShow
← Cloud and Infrastructure
Lesson 2100 of 2,98945. Observability - Dashboards and SLOsFree lesson

Dashboard Purpose and Audience

Define dashboard objectives, target users, and use cases to ensure effective information delivery.

Dashboard Purpose and Audience

You'll learn how to define dashboard objectives, identify target users, and clarify use cases to maximize information delivery effectiveness.

Why Purpose and Audience Matter

A dashboard without a clear purpose is like a map with no destination. Before building any observability dashboard—whether in Grafana, Kibana, or your tracing backend—you must answer two fundamental questions: What problem does this solve? and Who will use it?

Dashboards serve different needs:

  • Operational dashboards help on-call engineers diagnose incidents in real-time
  • Executive dashboards provide high-level health and SLO compliance at a glance
  • Debugging dashboards let developers drill into traces, logs, and metrics for root-cause analysis
  • Capacity planning dashboards inform infrastructure teams about growth trends

Aligning Design with Audience

Different users need different information density and complexity:

On-call Engineers need actionable metrics front-and-center: error rates, latency percentiles, current alerts. They want fast answers during incidents, not aesthetic beauty.

Developers require correlation between application traces (OpenTelemetry spans), logs (from ELK/Loki), and metrics. They need drill-down capability more than summaries.

Executives want traffic lights: green/yellow/red status indicators, SLO burn rates, and business KPIs. Overwhelming them with Prometheus queries defeats the purpose.

Capacity Planners focus on trends over weeks or months—CPU usage growth, storage consumption—not minute-by-minute fluctuations.

Define Before You Build

Start every dashboard project by documenting:

  1. Primary objective (e.g., "detect payment service outages within 30 seconds")
  2. Target user role(s)
  3. Key decisions this dashboard informs
  4. Acceptable update latency (real-time vs. hourly rollups)

Key Takeaway: Effective dashboards align their metrics, layout, and refresh rates with specific user roles and decision-making needs—generic "kitchen sink" dashboards serve no one well.