on 13 Jan 2025 10:00 AM
Dynatrace Synthetic Browser Monitors can be manually or automatically assigned to a RUM Application. In some cases automatic assignment does not occur as expected
Issue | Solution | Tasks | Alternative(s) |
---|---|---|---|
Browser monitor not automatically assigned | Resolve injection issues | Check injection | Manually assign the Browser Monitor |
When a Browser Monitor is executed on a page that has RUM injection, the Dynatrace Synthetic Player sees the RUM injection and applies the Application configuration to the Browser Monitor. The benefit of this, over manual assignment, is that, as well as being able to show the Availability in the RUM application, the Browser Monitor sessions will be seen in the Application as made by a Synthetic user, and you can then analyze them using Session Segmentation, and you can see any related traces.
Clicking on Perform Waterfall Analysis for an action in a Session, will take you to the step in the relevant execution in Synthetic Monitoring
The link works in reverse also. Browser Monitor executions link to the relevant User Action in the RUM Application. Clicking on the user action link, a clickable url in blue, will open the relevant User Action details page.
To view traces from a Browser Monitor, open an execution and click on the relevant event. Scroll down to the 'Detailed breakdown' section and click on Traces tile, as shown here
Where a Browser monitor is not showing as automatically assigned to a RUM Application, the following steps can be used to find and resolve the cause.
Confirm that the jsAgent script tag is the first script node on the page.
This is only a requirement for Synthetic, so RUM injection would still work for Real users even when this is not the case.
For manually injection applications, you will need to work with the team performing the injection to ensure the jsAgent script tag is the first script loaded.
If manual injection is being used, confirm that the jsAgent script filename matches expected format:
<name>_<featurehash>_<version>.js
or <appid>_complete.js
If you have resolved any issues highlighted above but are still not seeing any Synthetic sessions in your RUM Application, then please open a chat or Support ticket and provide the following information: