x-dtreferer header issue
Every so often, the x-dtreferer POST request header does not appear in a UserAction post. This results in the UserAction being "lost" and not appearing in the DynaTrace Client UI. Has anyone else run into this issue?
I have manually instrumented the JS agent into my application and, the vast majority of the time, I don't have this issue.
Do you have a web server farm? If so - is the web server agent installed on all web servers in the cluster? If one is missing it could explain that phenomenon in case a web request from the browser gets directed to a webserver that doesnt have a web server agent installed.
My testing was done with everything running on my local system (browser, Dynatrace agent, server, client). When I look at the browser-level traces, I see that the x-dtreferer POST request header is not there. Thus, even before it leaves the browser environment, the x-dtreferer is not even there. So it's as if the agent is not properly adding the header in the script.
Maybe a script blocker browser plugin? maybe a javascript error that deactivates our agent? Can you use the browser dev tools to see whether the browser could successfully download the dtagent.js and whether there are no js errors?
Community Member of the Month
April 2018
Announcing Dynatrace's Community Member of the Month for April 2018, Babar Q.! Click here to read more!