Find traces related to session/user actions

[clc]

We are having some issues with some services not being correlated correctly to a useraction.

In the good old Appmon it was easy to see since all purepaths/webrequest/services it was not able to correlate to a user action was still in the session just greyed out.

Are there any easyway to find all services/purepaths that are not correct correlated to a usersession/useraction in Dynatrace?

-Claus

[AntonPineiro]

Hi,

Maybe using request attributes to enrich/add user action information to requests.

And then, you can filter traces with those request attributes.

Best regards

[clc]

We could extract a unique session id and tag the individual services, but it will not be able to use it for traces with multible services used and thats almost all our traces so can use it in this case.

[benjamin_mullan]

@clc I have had stitching issues with web front end calls to backend api calls when they are on a different domain. I found the dtCookie value was different on every single backend call for a single user/session. I believe this is a FE coding issue (but that's a guess an not my expertise) instead I utilized the following "Use the x-dtc header" instead of the cookie base approach. 

https://www.dynatrace.com/support/help/platform-modules/digital-experience/web-applications/initial-...

Another thing to check is if you are exceeding the "Adaptive traffic management" limits. I'm not entirely sure if this can be a culprit for stitching issues or not, I'm assuming it is but hopefully someone can confirm that. 

You should have a dashboard in your tenant called OneAgent Traces - Adaptive traffic management. This has some handy info around the ATM limits in your environment.

[clc]

Sessions are ok and all useraction within a usersession is in the visit, issue is some webrequest er not stitched correctly to useraction. So we have issue with purepaths that encounters a error but because they are not stitched to a useraction it seems all ok, and im having problem tracing it back to a session since I can not find a unique trace id for a useraction/usersession, but guessing that there must be for correlation.

No issues with to many purepaths/load so no adaptive traffic issues seen in our environment. 

[gbaudart]

Hi @clc 
In certain cases, if you use agentless and if you activate cross-origin, it may be necessary to pass the x-dtc header into CORS in order to be able to link user actions (or errors) to backend traces.

documentation link : https://docs.dynatrace.com/docs/platform-modules/digital-experience/web-applications/initial-setup/l...