Session properties missing in the new RUM Experience

[Aaron_Schultz]

• Summary
• Problem
• Troubleshooting steps
• Resolution
• What's next

Summary

This article applies to Dynatrace SaaS customers using Real User Monitoring (RUM). It explains why session and action properties configured in RUM Classic are not visible in the new RUM Experience, and how to reconfigure them so they appear correctly.

Problem 

After you turn on the new RUM Experience, session and action properties that were previously visible in the RUM Classic view are no longer visible in the new RUM Experience view.

This is expected behavior. Session and action properties configured in RUM Classic are not automatically migrated to the new RUM Experience. They must be reconfigured manually using the new event and session properties configuration.

Troubleshooting steps

If you are simply not seeing session properties in the new RUM Experience, follow these steps to confirm the problem matches this article before proceeding to the resolution.

Step 1: Confirm properties have not already been configured in the new RUM Experience

1. In Dynatrace, go to Experience Vitals > Overview > Web.
2. Select the affected frontend application.
3. Select the Settings tab.
4. Select Capture properties.
5. The page has two sections:
   • Captured event properties: lists properties captured automatically from the page using CSS selectors, DOM attributes, cookies, or JavaScript variables. A counter shows how many are configured out of the 100-property limit.
   • Allowed API-reported properties: lists properties reported via the JavaScript API. A counter shows how many are configured out of the 200-property limit.
6. Check both sections for the properties you expect to see. If both sections show "No properties configured," no event or session properties have been set up for this application in the new RUM Experience.

If both sections show no properties configured, follow the resolution steps below.

Resolution

RUM Classic and the new RUM Experience use separate property configuration models. Reconfigure your session and action properties as event and session properties directly in the new RUM Experience. The same capture methods are available (CSS selectors, JavaScript variables, cookies, and more), so you can re-create your existing properties using the new configuration interface.

1. In Dynatrace, go to Experience Vitals > Overview > Web.
2. Select the frontend application you want to configure.
3. Go to Settings > Capture properties.
4. Select Add property and configure each property using the appropriate capture method:
   • CSS selector: extracts a value from a DOM element
   • DOM attribute: reads an attribute from a DOM element
   • Cookie: retrieves a cookie value
   • JavaScript variable: reads a value from the window object or a JavaScript variable
5. If your RUM Classic configuration used the JavaScript API to report properties, add those property names to the allowlist under the API-reported properties section. Property names must use only letters (A–Z, a–z), numbers (0–9), underscores (_), and dots (.), and must be prefixed with event_properties. or session_properties. in your code.
6. Repeat for each application and each property you want to carry over from RUM Classic.

Note: Steps within a single property definition run in sequence, with each step passing its output to the next. This allows you to chain operations, such as reading a cookie value and then parsing it as JSON.

After configuration, session properties are visible at the individual user session level. To view them, go to Experience Vitals and open a specific user session.

Note: Session properties are not available on live sessions. If you cannot find the properties, make sure the session is complete before checking. 

fetch user.sessions
| fields session_properties
| limit 10

For a full reference on the new configuration options, see Event and session properties for web.

What's next

If this article did not help, open a support case, mention that this article was used, and provide the following in the case (include a direct link for each item where possible):

• Screenshot of the Session and action properties page in RUM Classic for the affected application
• Screenshot of the Capture properties page in the new RUM Experience for the same application
• The name of the affected web application or frontend

Additional resources:

• Session and action properties (RUM Classic)
• Event and session properties for web (new RUM Experience)