spring-fleet-logging-setup
Installation
SKILL.md
Fleet Logging Setup (logback convention)
Cross-service log correlation needs two things: every service writing to one
known directory, and trace keys (trace_id, span_id, sessionId, …) present
in each line. This skill installs a logback convention that guarantees both. It
is idempotent and opt-in per service.
What trace keys to use (2026)
- Primary: OpenTelemetry / Micrometer Observation. Add the
spring-boot-starter-actuator+micrometer-tracing-bridge-otel(or, on Spring Boot 4, the dedicatedspring-boot-starter-opentelemetry). The W3Ctraceparentheader is auto-propagated across HTTP/gRPC, and the Observation API automatically populates MDC keystrace_id(32-char hex) andspan_id(16-char hex). These are the modern, framework-default keys. - Fallback / legacy: sessionId, requestId. Keep them in the pattern for fleets that pre-date the Observation API or that propagate an application- level session id (auth, X-Request-Id) the user wants to correlate on.