What problem does it solve? Spring Boot microservices within a team often end up with inconsistent logging configurations, missing request correlation IDs, and mismatched Prometheus metric tags, making cross-service debugging painful. This Skill applies one canonical observability setup to every Spring Boot 4.x / Java 25 service so logs, MDC context, and metrics look identical everywhere. ## Core Features & Use Cases - Canonical logback-spring.xml: Configures a readable console pattern for the local profile and JSON output to Logstash via an async TCP appender for all other profiles. - MDC request correlation: Creates an MdcRequestFilter that injects requestId and path into the MDC for every HTTP request, plus a mandatory JUnit test suite to verify it. - Prometheus metrics tagging: Configures the management block so every metric carries an application tag matching spring.application.name. - Optional distributed tracing: Prepares traceId and spanId MDC keys so OpenTelemetry can be activated later for Grafana Tempo or Jaeger without touching the logging config. - Use Case: When onboarding a new microservice, run this Skill to audit the existing logging state, apply the team's standard logback-spring.xml and MDC filter, and verify Prometheus metrics are correctly tagged. ## Quick Start Apply the team's standard observability setup with Logback, MDC request tracing, and Prometheus metrics to this Spring Boot 4 microservice.