Dynatrace user tagging

Dynatrace user tagging DEFAULT

There are actually two different options to accomplish this. First is described in the URL and it's just a matter of configuration in Dynatrace UI. When you open the application settings, you can specify the user tag. With this option you can specify username based on four different options (Cookie name, Meta tag, Javascript variable or CSS selector) - all is done by the ruxitagent javascript code and you don't have to change anything in the page source code.


Second approach is to call the Javascript function (you supply the user name as the parameter):

dtrum.identifyUser()

With this approach you will need to modify the page source code to call this function.

I recommend to try the first option if possible. Use the second option only if the username cannot be obtained by on the the four methods above.

Please be aware that there is some user tag persistence across sessions the the UI. I'd recommend to clear your cookies when testing the user tag definition, since your sessions might have the AnonymousXXXXX tag even if your user tag definition is correct. (Happened to me few times). The usertag will correctly assigned for new sessions.

TEMPEST a.s., Slovakia, Dynatrace Master Partner

Sours: https://community.dynatrace.com/t5/Dynatrace-Open-Q-A/Configuring-User-Tag-on-Dynatrace-Managed/td-p/34743

Quite a few points there:

  1. Dynatrace uses the user tag you specify as well as a cookies for session correlation, in the settings for the application there is an option for a persistent cookie (rxVisitor) and sessions get tied to the same user when these match - there is no time limit for these
    1. https://www.dynatrace.com/support/help/shortlink/cookies#cookie-storage
  2. If a user opens to windows odds are the same persistent cookie would be present in both of those regardless of if they log in so those could be tied to the same user - it depends if you have that option enabled though
  3. (and 4) the location mapping is determined based on the IP address that we see for that session which needs to be a public IP address for it to happen automatically (you can do your own mappings of private IP addresses or to override public ones) and even for these public ones not all ranges can be mapped to the region level sometimes it is only country. But the tagging is not relevant here, just the IP address so I would see if those sessions have a different one reported

This looks like the sessions query page - it will be easier to see and make sense of a lot of this behavior if you look directly at some sessions and users - then you can see when 'anonymous' sessions are getting tied to the same user that is sometimes tagged and what the IP addresses are that we see. In sessions query they'll all show up as individual records and you need to try to do that mapping manually.

Sours: https://community.dynatrace.com/t5/Real-User-Monitoring/Mapping-of-User-tags-and-internalUserID-in-RUM/td-p/114477
  1. Female body outline clipart
  2. Denki pokemon
  3. Matthew kjv
  4. Warframe critical focus

Optimum user experience requires that you understand the journeys of all your application users across multiple web properties.

To group sessions based on individual users across entities and sessions, Dynatrace enables you to tag individual sessions that are captured with Dynatrace Real User Monitoring. This serves as an additional mechanism Dynatrace provides for applying user tags:

  • CSS selectors
  • Meta-tag capture
  • JavaScript variables
  • JavaScript tag API calls
  • (New) Server-side request attributes

Dynatrace already allows you to access the frontend information that you may need, but sometimes the data needed to tag sessions only resides on the server side and isn’t exposed to the frontend. Specifically, SSO solutions often hold such information without exposing it to the frontend. Now, as long as you have OneAgents deployed on your backend system, you can access the required tag information via server-side request attributes.

Sign up for the Preview

If you’re already leveraging Dynatrace Real User Monitoring and have Dynatrace OneAgents deployed on your backend systems, you can join the Preview to take advantage of this great new benefit of the Dynatrace full-stack monitoring solution. To join the program, your Dynatrace SaaS environment must be updated to version 1.161 (or version 1.162 for Dynatrace Managed environments).

Setup

You may have already defined one or more request-attribute capture rules. If not, to learn how to configure request attributes, have a look at our Request attributes: Simplify request searches & filtering blog post.

Once you have a request attribute configured, open up the settings for your application (Application settings > User tag) and click the Add tag (identifier) rule button.

List of user session tagging rules

Next, from the Expression type to capture drop list, select Server-side request attribute and the Request attribute name of the request attribute you want Dynatrace to use for user tagging.

Select request attribute to be used for user session tagging

Please keep in mind that certain service request attributes won’t be captured for each user action/user session as all corresponding server-side PurePaths may not be captured due to adaptive capture control.

If you join this Preview, this data-capture option will also be available in your environment for these upcoming capabilities:

  • Definition of user session properties (Release target: Dynatrace version 1.164)
  • Definition of user action properties (Release target: Q2 2019)
Sours: https://www.dynatrace.com/news/blog/user-tags-for-session-analysis-now-support-server-side-request-attributes-eap/
Configure Tag Manually/Automatically -Dynatrace

Hi Team,

I'm trying to apply user tagging on one of our application which is getting monitored under dynaTrace SAAS

The tag I'm getting in user session is like this, Sirname, Name ( alias ) | Logout but according to regex applied \bEmpId" value="([^"]*) in cleaning rule it supposed to give me only "alias".

The CSS selector result is (I checked it via browser),

<div class="middle-header-content">
Surname, Name ( Alias ) <span>|</span> <a href="Logout.htm" class="logout" data-step="9" data-intro="Click here to Logout"></a>
<a href="Logout.htm" data-step="9" data-intro="Click here to Logout"><img src="images/custom/Logout.png" style=" vertical-align: middle; margin-top: -6px;" alt="logout" title="logout">Logout</a>
<input type="hidden" name="empName" id="empName" value="Sirname, Name ( alias ) ">
<input type="hidden" name="emailAdd" id="emailAdd" value="[email protected]">
<input type="hidden" name="mobileNo" id="mobileNo" value="4712683461">
<input type="hidden" name="repManagerFullName" id="repManagerFullName" value="">
<input type="hidden" name="EmpId" id="EmpId" value="alias">
<input type="hidden" name="Gender" id="Gender" value="GM">

</div>

I don't know why it is showing such abnormal result. Please help.

BR,

AK

Sours: https://community.dynatrace.com/t5/Real-User-Monitoring/User-Tagging-in-Dynatrace-SAAS-showing-inappropriate-result/td-p/69632

Tagging dynatrace user

.

Mastering Dynatrace Session and User Action Properties for Enhanced Business Analytics

.

You will also be interested:

.



218 219 220 221 222