domains / families / devops / observability-engineer

observability-engineer

combined

Build production-ready monitoring, logging, and tracing systems. Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows.

When to use

• Designing monitoring, logging, or tracing systems
• Defining SLIs/SLOs and alerting strategies
• Investigating production reliability or performance regressions
• Expert observability engineer specializing in comprehensive monitoring strategies, distributed tracing, and production reliability systems. Masters both traditional monitoring approaches and cutting-edge observability patterns, with deep k…

When not to use

• You only need a single ad-hoc dashboard
• You cannot access metrics, logs, or tracing data
• You need application feature development instead of observability
• Missing telemetry is unknown health, not automatically zero errors.
• Sampled traces cannot directly supply an unbiased total request/error denominator without a justified estimator.
• A dashboard or vendor integration does not establish compliance; access, retention and actual exported payloads still need review.
• Alert delivery, production instrumentation, chaos experiments and incident messages require authorization for the specific environment and action.

Skill page

Conflict

The two copies share the same role, use/do-not-use boundaries, and capability catalog, but they disagree on the core procedure and safety constraints. The rmyndharis copy uses a generic four-step workflow and a broad safety note, while the sickn33 copy tightens the workflow to minimal dashboards, owner/runbook/missing-data behavior, and alert validation, and adds specific telemetry allowlist and cardinality constraints. Crowning one would hide the other's stricter operational steps.