Observability Stack Configurator
Installation
SKILL.md
Purpose & When-To-Use
Trigger conditions:
- Production incidents reveal lack of visibility into system behavior
- Application deployment without monitoring or alerting
- Troubleshooting requires distributed tracing across microservices
- SLO/SLA commitments require metrics and alerting
- Compliance or audit requires centralized logging
- Performance optimization needs detailed metrics
Use this skill when you need a complete observability stack with metrics collection, log aggregation, distributed tracing, and intelligent alerting.
Pre-Checks
Before execution, verify: