observability-engineer

This Skill helps design distributed tracing by instrumenting services with metrics, logs, and traces using OpenTelemetry. It enables end-to-end observability for root cause analysis across distributed systems.

Defining SLI and SLO alerting strategies involves establishing service-level indicators aligned with business impact. This ensures alerts trigger reliably during service degradation or outages.

You can integrate Prometheus and Loki with Grafana to build a comprehensive observability stack. This combination collects metrics and logs to enable dashboards and incident response workflows.

Creating runbooks and incident response workflows involves establishing playbooks and automated responses for outages. This ensures reliable operations and structured handling of service degradation.

This observability approach is explicitly applicable to distributed systems and enterprise workloads. It handles production-grade service onboarding, data retention, and complex reliability requirements.

Production-grade observability integrates metrics, logs, and traces to improve reliability and incident response. You need it when operating distributed systems requiring root cause analysis and reliable operations.