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

PageView should have own ID for proper correlation #361

SergeyKanzhelev opened this issue Dec 5, 2016 · 3 comments

PageView should have own ID for proper correlation #361

SergeyKanzhelev opened this issue Dec 5, 2016 · 3 comments


Copy link

See microsoft/ApplicationInsights-dotnet#47 (comment)

We should allow to tie together PageView and Dependencies. So PageView should have own ID field.

Copy link

It seems like maybe PageViewTelemetry should derive from OperationTelemetry, just the same as the other types that have their own ID? DependencyTelemetry and RequestTelemetry are contextual operations that similarly contain traces, exceptions, etc. and PageViewTelemetry.Id would be assigned to root operation ID of associated dependencies via depTelem.Context.Operation.Id which is exactly how operations are nested under other OperationTelemetry as roots (e.g. RequestTelemetry)

Copy link

jpiyali commented Jan 16, 2019

This is actually available already today. For each new page in browser, unique id is set for page, that is also propagated as part of dependency data for outgoing requests in dependency id (id = | + + util.newid())

@jpiyali jpiyali closed this as completed Jan 16, 2019
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

4 participants