Skip to content

rrezartprebreza/spring-boot-skills / skills/spring-boot-4/production-observability

production-observability

Verified

Use when adding service-wide Spring Boot 4 Actuator, Micrometer Observation and Tracing, OpenTelemetry or OTLP export, structured logging, health probes, dashboards, or alerts. Combine with ai-observability only for Spring AI-specific token, prompt, and model telemetry.

Production Observability

Instrument user-visible operations and operational boundaries, not every method.

Baseline

  • Add the Boot 4 Actuator starter and one metrics registry selected by the platform.
  • For OpenTelemetry tracing over OTLP, use spring-boot-starter-opentelemetry and Boot's management.opentelemetry.tracing.export.otlp.* properties.
  • Use Micrometer Observation for application metrics and traces.
  • Prefer Micrometer APIs over direct OpenTelemetry APIs in application code.
  • Export metrics and traces through OTLP when an OpenTelemetry collector is the platform boundary.
  • Expose only required actuator endpoints and secure non-public endpoints.

Observation conventions

  • Name observations by stable operation, such as orders.create.
  • Use low-cardinality key values for metrics and high-cardinality values only for traces.
  • Never tag metrics with user IDs, entity IDs, URLs containing IDs, or exception messages.
  • Register a ContextPropagatingTaskDecorator for async executor boundaries.
  • Enable Reactor automatic context propagation only deliberately and test it.
  • Avoid annotating already instrumented MVC controllers or repositories with @Observed.

Health and readiness

  • Keep liveness independent from remote dependencies.
  • Put traffic-critical dependencies in readiness groups.
  • Give custom health checks strict timeouts and stable detail keys.
  • Keep sensitive health details hidden from unauthenticated callers.

Logging and alerts

  • Emit structured logs correlated with trace and span IDs.
  • Redact credentials, tokens, personal data, prompts, and request bodies by default.
  • Alert on service-objective symptoms: error ratio, latency, saturation, or queue lag.
  • Include a runbook and service/dependency identity in every actionable alert.

Examples

  • See examples/good-observation.java, examples/good-observability.yml, and examples/bad-observation.java.

Official sources

Gotchas

  • Agent uses high-cardinality IDs as metric tags - reserve them for traces or logs.
  • Agent directly configures an OpenTelemetry SDK and disables Boot integration accidentally - prefer Boot and Micrometer support.
  • Agent exposes all actuator endpoints - expose the minimum and secure them.
  • Agent ties liveness to a database or broker - dependency outages can trigger restart loops.
  • Agent loses trace context in @Async work - register context propagation explicitly.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall