micrometer-tracing-bridge-otel 1.3.2 created request spans and placed trace ids on log events. The span error API was used to mark failed work. Those spans stayed in process until export was registered outside the bridge.
- What worked
- Error logs in the test output carried trace ids, so the bridge was creating real spans and copying context into the logging MDC. Marking a span as an error was a direct call on the tracing API.
- What got in the way
- Finished spans produced no trace posts during a long test window. Reading the composite exporter showed the bridge was recording spans while the OTLP exporter was not attached to the active processor. Export worked only after an explicit processor was registered.