Synthetic private locations come with a set of options you can configure to match your environment requirements. All these options can be found by running the below
docker run --rm datadog/synthetics-private-location-worker --help
The private locations configuration options can be then be passed as parameters to your JSON configuration file or as arguments in the launch command, like below:
docker run --rm -v $PWD/<MY_WORKER_CONFIG_FILE_NAME>.json:/etc/datadog/synthetics-check-runner.json datadog/synthetics-private-location-worker:latest --logFormat=json
Note: Arguments set in the launch command have precedence over the configuration file. However, these options are not stored and are consequently only prevalent for a given launch.
|String||Datadog site from which the private location pulls the test configuration and pushes the test results. Your |
|Boolean||Use host local DNS configuration first (e.g., the configuration from your |
|Array of Strings||DNS servers IPs to use in given order (e.g., |
--dnsflag on Docker, or
|Boolean||Prevent users from creating Synthetic tests on endpoints that are using reserved IP ranges (IANA IPv4 and IPv6 Special-Purpose Address Registry), unless for those explicitly set with the |
|Array of Strings||Grant access to specific IPs and/or CIDR among IP ranges blocked through |
|Array of Strings||Block access to specific IPs and/or CIDR in addition, or not, to the IP ranges blocked when setting the |
blacklistedRange parameters are now deprecated and should be replaced by the above listed ones.
|String||Proxy URL used by the private location to send requests to Datadog (e.g., |
|String||Proxy URL used by the private location to send test requests to the endpoint.|
|Boolean||Discard SSL errors when private location is using a proxy to send requests to Datadog.|
proxy parameter is now deprecated and should be replaced by
|Number||Maximum number of tests executed in parallel.|
|Number||Maximum test execution duration for API tests (in milliseconds).|
You can upload custom root certificates to your private locations to have your API and Browser tests perform SSL handshake using your own
.pem files. When spinning up your private location containers, mount the relevant certificate
.pem files to
/etc/datadog/certs, the same way your private location configuration file is mounted. These certificates are then considered trusted CA and used as such at test runtime.
Note: This feature is supported for versions 1.5.3+ of the private location Docker image.
|String||Format log output between |
|Number||Verbosity level (e.g., |
|Boolean||Display worker configuration parameters without secrets.|
|Boolean||Display full worker configuration parameters.|
Additional helpful documentation, links, and articles: