-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The otel::tracing log level is not set to the same or lower level than TRACING_LEVEL, which makes span.set_parent() invalid. #148
Comments
I release a new version of Bad new, this version is for opentelemetry 0.24 and the auto-bump version releases |
My tracing otlp tonic export setup works pretty fine but For other things I use My overcall tracing level is |
opentelemetry use static variables, you should not have multiple version of opentelemetry (else tracer could not be connected to your configured exporter,...) # Check only one version of opentelemetry_api should be used
# else issue with setup of global (static variable)
# check_single_version_opentelemtry:
cargo tree -i opentelemetry_api |
Before using this crate I have no results for For opentelemetry_sdk v0.24.1
├── opentelemetry-otlp v0.17.0
│ └── private-init v0.1.33
│ └── myservice v0.1.0 (/Users/user/Code/..)
├── opentelemetry-proto v0.7.0
│ └── opentelemetry-otlp v0.17.0 (*)
├── private-init v0.1.33
└── tracing-opentelemetry v0.25.0
└── private-init v0.1.33 |
Cargo.toml
The span generated before setting will not bring in the traceparent id of the http request:


After configuring the tagger log level, it can be normally associated with the incoming trace:
The text was updated successfully, but these errors were encountered: