question

Daniil K. avatar image
Daniil K. asked ·

"dtSa" cookie in Dynatrace RUM

Hello, everyone. Recently, doing one of the software service configuration in NAM, I had troubles recognizing the real-user operations context by HTTP request/response template. In this particular application front-end design, this context appeared near the end of 20...30kB request POST body - too far to detect it with NAM staying within the reasonable capacity demand.

We have this application instrumented with Dynatrace RUM as well. Occasionally, I have noticed that after instrumentation every client machine started adding "dtSa" and other useful cookies, where I could easily read the operation context. Something like this:

dtSa=true|C|-1|Search|-|1552289535339|89322004_714|http://....

Fourth parameter ("Search" in this case) is exactly what I need for NAM configuration.

Apparently, Dynatrace doesn't use this information in its reporting. The only documentation I could find regarding this cookie refers to "Application Monitoring & UEM" solution. It seems like this is an idle inherited option. Maybe I miss something.

I have few questions regarding this finding:

Can I build a long-term NAM operation context detection strategy relying on this cookie parameter?

Is there plans to enable operation context recognition in Dynatrace with this cookie?

oneagentRUMnamuser actions
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Alexander S. avatar image
Alexander S. answered ·

Hi, the cookie format and the content of the cookies might change. Some information in the cookies are also depending on the configuration of the RUM application.

What is the use case you want to solve? Why do you want to monitor the same application with NAM and RUM?

Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Daniil K. avatar image
Daniil K. answered ·

RUM and NAM have some point of overlapping functionality but they are far not identical. NAM (if configured in a right way) still has much wider, accurate and more focused view at real-users perception. In includes network component. In my practice of using these two solutions together we already had cases when real-users were suffering from noticeable server-side performance degradation and NAM fairly triggered an alert in those cases, but it was missed in Dynatrace RUM statistics.
In our case NAM is helping us to recognize what is bothering real users the most, while Dynatrace shows the root cause where it can (it is far not 100% of cases).
This cookie is very helpful to discover what actually end-user hits at the particular form of the application and what is the response time.

Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions session replay diagnostic tools permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX timestamp action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android