spring-observability

What problem does it solve?

Spring services often ship with unclear logs, missing trace context, and metrics that don’t answer real operational questions; this Skill adds consistent observability so issues can be diagnosed quickly and reliably.

Core Features & Use Cases

• Structured logging with correlation context: Logback JSON or console output with MDC keys (e.g., traceId, spanId, userId, requestId) so every event can be tied to a request across threads.
• Distributed tracing and method-level spans: OpenTelemetry-based instrumentation plus Micrometer tracing/bridge patterns using @Observed to capture timing and contextual metadata.
• Metrics and actuator visibility: Micrometer counters/timers/gauges and Actuator endpoint configuration for health, metrics, Prometheus scraping, and log level controls.
• Use case: When an order API fails intermittently, enable this Skill to correlate request logs with trace IDs, time critical methods, expose Prometheus metrics, and add health indicators that pinpoint failing dependencies.

Quick Start

Enable spring-observability in your Spring Boot 4.x service by adding the stated observability dependencies and wiring MDC correlation, @Observed tracing, and Micrometer/Actuator metrics as shown in the skill instructions.