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

Task 6268904: [JS] Provide options for populating the SDK operation id during initialization #1704

Closed
MSNev opened this issue Nov 2, 2021 · 0 comments

Comments

@MSNev
Copy link
Collaborator

MSNev commented Nov 2, 2021

Currently, during initialization of the SDK we populate the operation id to a random value.

However, there are some customers that are looking to join the initial server side request (the one that returns the page) with the requests that are sent from the browser.

This is especially important as part of auto attach options when the customer will want to join the requests.

The customer expects to see the same operation_Id values for the requests (server-side) and pageView (client-side) telemetries when visiting a URL in their application. This behavior is described in the official documentation here:

https://docs.microsoft.com/en-us/azure/azure-monitor/app/correlation#example

In the doc's example, for a single page visit the request has an operation_Id of STYz and the pageView also has an operation_Id of STYz.

@MSNev MSNev added this to the 2.7.1 (Future Release) milestone Nov 2, 2021
@MSNev MSNev self-assigned this Nov 2, 2021
@MSNev MSNev removed this from the 2.x.x (Next Release) milestone Dec 6, 2021
@MSNev MSNev added this to the 3.(beta).x (~v3.0.0) milestone May 27, 2022
@MSNev MSNev modified the milestones: 3.(beta).x (~v3.0.0), 3.0.0 Apr 11, 2023
@MSNev MSNev added the fixed - waiting release PR Committed and waiting deployment label Apr 11, 2023
@MSNev MSNev modified the milestones: 3.0.0, 3.x.x (Future Release) Apr 12, 2023
@MSNev MSNev modified the milestones: 3.x.x (Future Release), 3.1.x Dec 7, 2023
@MSNev MSNev added waiting - CDN deployment released - NPM and removed fixed - waiting release PR Committed and waiting deployment labels Feb 15, 2024
@MSNev MSNev closed this as completed Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant