ddd4j-boot Observability

Overview

Covers Actuator, liveness/readiness, metrics, trace, logging, monitor, and OpenTelemetry uniformly, not split per artifact. Before use, confirm the maintenance line through ddd4j-boot-version-selection.

When to Use

• Configuring Actuator exposure and separating liveness from readiness probes, with readiness aggregating real dependency checks.
• Wiring metrics (and the ddd4j metrics bridge) so domain and framework counters actually increment.
• Setting up tracing with OpenTelemetry and verifying the collector/exporter truly receives spans — not just that the SDK initializes.
• Deciding log formats and correlation (trace IDs in logs) across a Boot line's logging setup.
• Reviewing exporter lifecycle: exporters must have owners with idempotent close so shutdown does not drop or corrupt telemetry.
• Diagnosing "monitoring is configured but empty": beans present, endpoints responding, yet the backend shows no data.

When NOT to Use

Do not use this skill when: