/cc @brunobat (opentelemetry,tracing), @radcortez (opentelemetry,tracing)

We face the same issue.

We have set these settings:

quarkus.management.enabled=true
quarkus.management.host=localhost
quarkus.management.port=9002
quarkus.management.root-path=/management

The requests to /management/health and /management/metrics are being recorded now, which produces a lot of unnecessary traces.

I would like to work on this

Ok @b3lix, go for it.

Whats the current status of this? Otherwise I would like to give this a go.

@b3lix, Do you mind if @nielsvhaldvb works on this?

@brunobat @nielsvhaldvb hello, I dropped this effort, so yes go ahead please, and good luck.

@nielsvhaldvb Do you still plan to work on this?

I have a similar issue, with Quarkus 3.15.1 LTS and quarkus.management.enabled=true:

• I can see traces being collected for http://0.0.0.0:9000/metrics endpoint each time Prometheus polls the metrics.
  We're setting quarkus.micrometer.export.prometheus.path=/metrics to override the default path.

• I don't see traces being collected for http://0.0.0.0:9000/q/health.
  But when the health check fails, I see an MDC traceId value in the log (using [traceId: %X{traceId}] in the log handler format), which would indicate some OpenTelemetry instrumentation is happening: <io.smallrye.health> [traceId: e35b0092f23fd6f05b867be6a5161c6f] SRHCK01001: Reporting health down status: {"status":"DOWN","checks":[{"name":"SmallRye Reactive Messaging - readiness check","status":"DOWN","data":{"receiver-channel":"[KO] - No partition assignments for channel receiver-channel","emitter-channel":"[OK]" }}]}

I created #45300 that should hopefully address this problem.