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...
For any HTTP Response code errors, follow the troubleshooting steps here.
For connection issues, check Firewall Constraints and allowlisting for Synthetic Monitoring
Error
Detai...
We can use the Crypto JS library code on Pre/Post execution script for the AES Encryption and Decryption in Synthetic HTTP Monitor. To do this we need to add the functions in to the pre/ po...
Summary
Private Synthetic Locations installed on Linux machines depend on certain packages and dependencies being available. The installation or update will fail if the necessary package...
Getting started
Synthetic Monitoring documentation index page
Create an HTTP monitor
Create a single-URL browser monitor
Record a browser clickpath
Create a NAM Monitor SaaS ...
For editing a browser monitor in script mode rather than as a clickpath, please see the documentation on correct script formatting: Script mode for Browser Monitors. Note: Ctrl + Spacebar will provid...
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
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...
