-
Notifications
You must be signed in to change notification settings - Fork 69
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
Support CloudEvents Traceparent Extension #452
Comments
Hey @grant - so to be quite honest, this extension has been a bit confusing to me, and I have had different expectations. To try and clarify, I posted in the #cloudevents slack about it. https://cloud-native.slack.com/archives/C9DB5ABAA/p1639507801025900 My expectation is that all extension attributes are encoded in the same way as other attributes. That is, they appear in the incoming HTTP request headers prefixed with Let's see if we get any response from others on that Slack query. |
@grant I am pretty sure that the SDK is doing the right thing based on discussion in the Slack link above. There is also an open PR to the Distributed Tracing Extension that we should be aware of cloudevents/spec#912. |
This issue is stale because it has been open 30 days with no activity. |
Closing as obsolete |
Describe the Bug
Some HTTP requests may follow the CE traceparent extension. Currently, the default way of parsing this extension does not work as expected.
Concretely, this extension / attributes (
traceparent
,tracestate
):https://github.com/cloudevents/spec/blob/v1.0/extensions/distributed-tracing.md
Steps to Reproduce
index.js
package.json
Send HTTP request:
Observe no
traceparent
field:Note: The
traceparent
header does not need to have ace-
prefix.Expected Behavior
HTTP.toEvent
should parse this documented extension attribute and populate the attribute in the CloudEvent object.traceparent
extensionActual Behavior
traceparent
extensionHTTP.toEvent
doesn't seem to parse this extensionThe text was updated successfully, but these errors were encountered: