You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest versions (v2.6.7, v2.7.x) of ArgoCD are still using v1.11.1 version of opentelemetry libs, which contains a bug causing lots of useless messages in the log:
The main issue is the amount of these log messages affecting the logging backends. It was fixed and included in the following patch releasev1.11.2. As a mitigation, we exclude this message on the logging solution side with a filter.
To Reproduce
Configure --otlp-address to enable sending traces to the available tracing backend;
Checklist:
argocd version
.Describe the bug
Latest versions (v2.6.7, v2.7.x) of ArgoCD are still using
v1.11.1
version of opentelemetry libs, which contains a bug causing lots of useless messages in the log:The main issue is the amount of these log messages affecting the logging backends. It was fixed and included in the following patch release
v1.11.2
. As a mitigation, we exclude this message on the logging solution side with a filter.To Reproduce
--otlp-address
to enable sending traces to the available tracing backend;Expected behavior
As per this issue (open-telemetry/opentelemetry-go#3432) the log message is not needed.
The suggestion is to bump up the dependency from
v1.11.1
tov1.11.2
to avoid any OTLP surprises.Version
P.S. There's a closed dependabot PR already, but I'm happy to provide a PR as well if needed. 👍
Thanks! :)
The text was updated successfully, but these errors were encountered: