Forum Discussion

Evgeniy_Bytsenko's avatar
Evgeniy_Bytsenko
Copper Contributor
Feb 04, 2019

Correlation between pageViews and requests (operation_Id) across all sub-request to Web API services

We have an angular app which is used UI for users and several web API services from which the angular app gets data. All of those web API services, the angular is included, send information into the same application insights (AI). We are trying to correlate requests and page views between angular app and web API services. Do to so, we used documentation on Microsoft docs site and did as it said but without any success.

The issue comes when we try to unite request and pageviews tables in AI. We can not unite those because of operation_Id and operation_ParentId containment. 

 

For example (how it works now):

1. We are on some page, on that page we call ai.trackPageView() (info appears on AI)

pageViews (table) contains -> operation_Id ==  tPn1I

2. From that page, we call web API service method (in cookies we have ai_user and ai_session)

3. On the server side (info sent to AI where ai_user and ai_session got from cookies as expected) and  

requests (table) -> operation_Id == operation_ParentId == 552e023f7f66e74aa19b0029c477d95e

but we expected (at least one operation_Id or operation_ParentId to be ==  tPn1I)

 

To set up application insights and to enable to use correlation we used documentation links:

https://docs.microsoft.com/en-us/azure/azure-monitor/app/asp-net
and
https://docs.microsoft.com/en-US/azure/azure-monitor/app/correlation

---

Has somebody faced this issue and has it have some workaround or maybe the exact path to solving that issue?

No RepliesBe the first to reply