What problem does it solve? Spring Boot services often ship without consistent metrics, logs, and traces, making production incidents hard to debug and SLOs impossible to measure. This Skill standardizes the three observability pillars so every service emits uniform, queryable signals. ## Core Features & Use Cases - Metrics with Micrometer + Prometheus: Enforces naming conventions (<service>.<domain>.<verb>), bounded tag cardinality, and correct use of Counters, Timers, and Gauges via a Filter + Recorder pattern. - Structured JSON logs with MDC: Configures Logback with logstash-logback-encoder, propagates traceId/spanId/callerId through MDC across async executors and Reactor pipelines, and defines log-level governance rules. - Distributed tracing with OpenTelemetry: Wires the Micrometer tracing bridge and OTLP exporter, sets sampling rates per environment, and standardizes W3C TraceContext propagation. - SLI/SLO conventions and dashboards as code: Defines availability, latency, and freshness targets with burn-rate alerting, plus Grafana dashboards and Prometheus alert rules stored in the repo. - Use Case: When creating a new Spring Boot microservice, apply this Skill to get production-grade metrics, JSON logs with correlation IDs, and distributed traces wired consistently from day one. ## Quick Start Apply the observability skill to wire metrics, structured logging, and tracing into my new Spring Boot service.
