Skip to content
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

Distributed tracing in EventGrid #13592

Closed
lmazuel opened this issue Sep 4, 2020 · 0 comments
Closed

Distributed tracing in EventGrid #13592

lmazuel opened this issue Sep 4, 2020 · 0 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Event Grid Messaging Messaging crew

Comments

@lmazuel
Copy link
Member

lmazuel commented Sep 4, 2020

Track2 SDK will auto-populate W3C headers traceparent/tracestate. However, in the case of EventGrid this is not enough:

  • If the request content-type is Cloudevent and tracestate/traceparent are not populated in the event
  • Then we want to copy the traceparent/tracestate into the CloudEvent extensions

Suggestion of implementation is a policy that would go after the DistributedTracing policy (otherwise we don't yet have the traceparent/tracestate values), but free to each dev to figure this out.

@lmazuel lmazuel added Event Grid Client This issue points to a problem in the data-plane of the library. labels Sep 4, 2020
@lmazuel lmazuel added this to the [2020] October milestone Sep 4, 2020
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-python that referenced this issue Mar 25, 2021
cdn track2 configure (Azure#13592)

* cdn track2 configure

* cdn only track2 config

* fix

Co-authored-by: Yan Zhang (WICRESOFT NORTH AMERICA LTD) <v-yanzhang@microsoft.com>
Co-authored-by: 00Kai0 <sunkaihuisos@gmail.com>
@lmazuel lmazuel added the Messaging Messaging crew label Apr 12, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Grid Messaging Messaging crew
Projects
None yet
Development

No branches or pull requests

2 participants