Dynatrace allows you to define custom string, numeric, and date properties for your monitored user actions and user sessions. Property values are then captured as part of each of your users’ journeys. Property values can be leveraged for unrivaled visibility into all the details of your users’ interactions with your application.
Below you can find the steps for defining such properties as well as related examples. To acquire a deeper understanding of how to use the session properties, visit Leverage user session properties.
Note: Currently, Dynatrace supports defining session and action properties for web applications only.
How to define action and session properties
User action and session properties are specific to each application. To define a property
From the navigation menu, go to Applications and select your application.
Click the Browse (…) in the top left corner and select Edit.
From the menu on the left, select Session and user action properties.
Click Add property.
For all expression types, you need to specify a Key, which is essentially the name of the property. The Key value is also used to identify and later locate the property in USQL. Allowed characters for Key values are
Optionally, define a Display name for the property to be used in the UI.
In case you want to restrict the captured values, you can define a clean-up rule for the property by enabling Apply cleanup rule and specifying a regular expression. The regex will be applied to the captured value, which means that if you try to capture a string that is for example 1000 characters long, only the first 100 characters will be captured and the regex will be applied to these 100 characters.
Click Save property.
Here are some sample definitions that work for our easyTravel Customer Frontend sample application.
In this example, the property
member_statuscaptures loyalty program membership status.
The numeric property
averagepersonpricecaptures the average price per person of a journey booked using easyTravel.
authorcaptures the name of the developer of the easyTravel application from a metadata tag.
appversionduring the session.
You can integrate Adobe Analytics with Dynatrace to facilitate collaboration among the different teams in your business. To find out how you can do this, visit Tightening the communication within BizDevOps with Adobe Analytics & Dynatrace.
The number of properties is limited to 10 string, 5 numeric, and 5 date properties per application.
Property capture begins only after enablement of specific property capture rules.
String properties are limited to a 100 characters before applying the clean-up rule.