Private locations allow you to monitor internal-facing applications or any private URLs that aren’t accessible from the public internet. They can also be used to create a new custom Synthetics location.
The private location worker is shipped as a Docker container, so it can run on a Linux based OS or Windows OS if the Docker engine is available on your host and can run in Linux containers mode.
By default, every second, your private location worker pulls your test configurations from Datadog’s servers using HTTPS, executes the test depending on the frequency defined in the configuration of the test, and returns the test results to Datadog’s servers.
Once you create a private location, the process of configuring a Synthetics API test from that private location is completely identical to that for Datadog managed locations.
In the Datadog app, hover over UX Monitoring and select Settings -> Private Locations. Add a new private location:
Fill out the Location Details and click Save and Generate to generate the configuration file associated with your private location on your worker.
Copy and paste the first tooltip to create your private location configuration file.
Note: The configuration file contains secrets for private location authentication, test configuration decryption, and test result encryption. Datadog does not store the secrets, so store them locally before leaving the Private Locations screen. You need to be able to reference these secrets again if you decide to add more workers, or to install workers on another host.
Launch your worker as a standalone container using the Docker run command provided and the previously created configuration file:
docker run --init --rm -v $PWD/worker-config-<LOCATION_ID>.json:/etc/datadog/synthetics-check-runner.json datadog/synthetics-private-location-worker
If your private location reports correctly to Datadog, you will see the corresponding health status displayed if the private location polled your endpoint less than five seconds before loading the settings or create test pages:
In your private locations list, in the Settings section:
In the form when creating a test, below the private locations section:
You will also see private location logs populating similar to this example:
2019-12-17 13:05:03 [info]: Fetching 10 messages from queue - 10 slots available 2019-12-17 13:05:03 [info]: Fetching 10 messages from queue - 10 slots available 2019-12-17 13:05:04 [info]: Fetching 10 messages from queue - 10 slots available
You are now able to use your new private location as any other Datadog managed locations for your Synthetics API tests. This is specifically useful to monitor any internal endpoints you might have.
https://www.shopist.io/, which is a test web application.
For a more advanced setup, use the command and see
Learn more about Private Locations below:
docker run --rm datadog/synthetics-private-location-worker --help and check
After you set up your private location: