From 7b195a3f8091bd58f4a6061b8f9a6f3b32211eb9 Mon Sep 17 00:00:00 2001 From: Juliana Almeida <50844569+julinvictus@users.noreply.github.com> Date: Mon, 3 Aug 2026 14:59:11 -0700 Subject: [PATCH] Update note on default monitors for private locations Clarified the behavior of default monitors when a private location is deleted and recreated. --- content/en/synthetics/platform/private_locations/monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/synthetics/platform/private_locations/monitoring.md b/content/en/synthetics/platform/private_locations/monitoring.md index 47c5d4ccb91..3f40c8d8202 100644 --- a/content/en/synthetics/platform/private_locations/monitoring.md +++ b/content/en/synthetics/platform/private_locations/monitoring.md @@ -44,7 +44,7 @@ By default, no handle is set in these monitors. To be alerted in case one of you Monitors in the {{< ui >}}Monitors{{< /ui >}} tab either have a group that corresponds to your private location ID or are tagged with `location_id:`. -> **Note:** Default monitors are created **only once**, when the first private location is created. Deleting a private location and creating a new one does **not** recreate the default monitors. +> **Note:** Default monitors are created **only once**, when the first private location is created. Deleting a private location and creating a new one does **not** affect the existence of those default monitors. They will continue existing when no PL exists and will start reporting when a new PL is created. ## Monitor your private locations with the Datadog Agent