Observability Unified Dashboard

Purpose & When-To-Use

Purpose: Design comprehensive observability dashboards that unify metrics, logs, and traces using the Four Golden Signals framework (Latency, Traffic, Errors, Saturation), automate correlations across telemetry signals via OpenTelemetry, track SLO compliance, and configure Grafana 11 with automatic drill-down from alerts to root cause.

When to Use:

• You need a single pane of glass for monitoring distributed systems (microservices, cloud-native apps).
• You want to implement SRE best practices (Golden Signals, SLO tracking, error budget management).
• You have multiple telemetry sources (Prometheus, Loki, Tempo, Jaeger, CloudWatch, Datadog) and need unified visibility.
• You need automatic correlation from high-level metrics (latency spike) → detailed logs (error messages) → distributed traces (slow span).
• You're migrating from tool-specific dashboards (separate Prometheus/Grafana, ELK, Jaeger UIs) to a unified platform.
• You require real-time SLO compliance tracking with burn rate alerts.

Orchestrates:

• observability-slo-calculator: Computes SLO compliance, error budgets, and burn rates.
• observability-stack-configurator: Deploys Prometheus, Loki, Tempo, Grafana stack.

Complements:

• database-postgres-architect, database-mongodb-architect, database-redis-architect: Adds database-specific metrics (query latency, cache hit rate).
• cloud-kubernetes-architect: Integrates k8s metrics (pod restarts, resource saturation).