This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
This guide aims to be able to find the WebSocket errors that occur during the execution of a synthetic monitor.
In order to see the information mentioned, it would be necessary to download...
Summary
This article provides the most common error codes seen in Dynatrace Synthetic browser monitors, along with note on the behavior and some troubleshooting suggestions.
For an...
Summary
Most scenarios can be recorded automatically using the Dynatrace Synthetic Recorder. There are some cases where a little scripting can make a script dynamic or do things not availa...
Summary
Synthetic Browser Clickpath events can time out if a site is very slow. Sometimes, extending the time allowed for a Synthetic action to complete can improve a Monitor's availabilit...
Summary
Background XHRs can be seen in Synthetic Monitors as the only XHR for some events, making them actions and billable.
Classic licensing documentation DPS documentatio...
Summary
Since version 122, by default, Chromium blocks third party cookies. If a site needs these to run as expected, they will need to be enabled for the Browser Monitor.
Problem ...
Summary
In some scenarios, a recorded click event doesn't work during recorder playback, and this may be because the relevant element needs a combination of events to complete an action. We ca...
Summary
The Entities API endpoint /api/v2/entities and Grail return a property 'isEnabled' for each Synthetic Monitor. This status is reflected in the Dynatrace Synthetic app in the...
Problem
While trying to record a new Synthetic monitor using the Dynatrace Synthetic Recorder, either by clicking record again, for an existing monitor, or record clickpath, for a...
Summary
In transitioning the Dynatrace Synthetic Recorder to MV3, JavaScript injection is now based on the Fetch API protocol.
If you've enabled Capture performance metrics for pages loaded...
