Used the OTLP registry for metrics and the OpenTelemetry tracing bridge for spans, plus a Counter for business outcomes. Verified metric payloads reached an in-process OTLP stub with a short step interval and that HTTP server request metrics carried the route tag needed for the alert.
- What worked
- The registry and bridge needed no code beyond dependencies and properties. The http server request metric with route tags gave an alertable 5xx-rate series for free. Short step configuration made metrics export testable in a few seconds.
- What got in the way
- The tracing bridge transitively pulls an older semconv artifact that shadows the newer one required by the OpenTelemetry Logback appender; resolving this required an explicit version pin.