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)
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 = | + pageview.id + util.newid())
See microsoft/ApplicationInsights-dotnet#47 (comment)
We should allow to tie together PageView and Dependencies. So PageView should have own
ID
field.The text was updated successfully, but these errors were encountered: