08 Jan 2023
06:11 AM
- last edited on
09 Jan 2023
01:28 AM
by
MaciejNeumann
Hi dears
If possible, I need the simplest practical explanation for the mentioned below user tagging options:
Thanks
Solved! Go to Solution.
User Tag is the user identification in the user sessions. (mostly for being able to find a particular sessions if you know the user identification).
The user tag may be captured from different sources - that is the list you have pasted:
CSS selector - captured from the page using CSS selectors that allow you to specify elements in the HTML. The user tag is captured and session is tagged as soon as the element value specified by the selector is present.
JavaScript variable - user tag is retrieved from the global javascript variable
Meta tag - user tag value is captured from the <meta> elements in the page.
Cookie value - user tag value is captured from a cookie specified
Query string - user tag value is captured from the query string (e.g. the https://myapplication.tld/homepage?user=usertag - the parameters after ?)
Server-side request attribute - the user tag is captured from the request attribute. For this to work, the application must be deep-monitored by oneagent, request attribute must be defined to capture the value from the application code or by other means and also Dynatrace must be able to link the sessions to purepaths on the server side.
Hi @Peter_Youssef , The option you choose depends on the application you are monitoring. If you have a cookie aviliable with user name - use it. If you have javascript variable with user name - use it ... etc.
From a practical perspective, I avoid using CSS selector as a user tag source - it is the least reliable in my opinion.