Description
As with the Telemetry and Tracing options enabled, we specify OTLP port where the telemetry data is sent. However as nobody listens on that port, we have multiple warning seen in the logs.
2026-01-20 16:33:21,417 WARNING [io.quarkus.opentelemetry.runtime.exporter.otlp.sender.VertxGrpcSender] (vert.x-eventloop-thread-3) Failed to export TraceRequestMarshaler. The request could not be executed. Full error message: Connection refused: localhost/127.0.0.1:4317
It'll be good to have a separate CR created with the telemetry/tracing settings and not use it as the default for all Operator tests.
Value Proposition
Avoid unnecessary warning logs in all operator tests
Goals
- Clean up logs
- Improve readability
Non-Goals
N/A
Discussion
No response
Notes
No response
Description
As with the Telemetry and Tracing options enabled, we specify OTLP port where the telemetry data is sent. However as nobody listens on that port, we have multiple warning seen in the logs.
It'll be good to have a separate CR created with the telemetry/tracing settings and not use it as the default for all Operator tests.
Value Proposition
Avoid unnecessary warning logs in all operator tests
Goals
Non-Goals
N/A
Discussion
No response
Notes
No response