-
Notifications
You must be signed in to change notification settings - Fork 55
incompatibility with AWS XRay (via OpenTelemetry collector) #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
Comments
Thanks for the report. |
It is feasible to change the scheme kspan uses, at the cost of losing trace continuity across a restart of kspan. Or add some persistence mechanism to cover the restart. |
I updated the title. |
Yes, it's neat to have restart persistence by the virtue of consistent hashing. Maybe someone could think of this as a separate mode. By the way, very similar use timestamps seems to be mandated by the W3C spec also... |
I just thought it might be useful for folks to be know that the kspan trace IDs are currently not compatible with AWS XRay: open-telemetry/opentelemetry-collector-contrib#5257 (reply in thread)
The text was updated successfully, but these errors were encountered: