From 59f2e245b3d1fb5197ed93e785649772d82a68ef Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 16 Mar 2026 13:03:10 -0400 Subject: [PATCH] [DOCS-13651] Add warning for custom schedules and decommissioned hosts Co-Authored-By: Claude Sonnet 4.6 --- .../guide/why-did-my-monitor-settings-change-not-take-effect.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/monitors/guide/why-did-my-monitor-settings-change-not-take-effect.md b/content/en/monitors/guide/why-did-my-monitor-settings-change-not-take-effect.md index 3a1f1013fd0..31369ae441a 100644 --- a/content/en/monitors/guide/why-did-my-monitor-settings-change-not-take-effect.md +++ b/content/en/monitors/guide/why-did-my-monitor-settings-change-not-take-effect.md @@ -25,6 +25,8 @@ When a host is renamed at the operating system (OS) level or decommissioned, the The old hostname remains in an alert state until the retention period expires, after which it automatically ages out and disappears from the monitor. **Note**: The old hostname will no longer appear in **Infrastructure > Hosts**, but will continue to be evaluated by monitors until the retention window passes. +
If a Custom Schedule is applied to a monitor, decommissioned hosts continue to be evaluated past the standard retention window. For more information, see Custom Schedules.
+ ### Workarounds If you need to remove the old hostname from alerts before the retention period expires, you can use one of the following workarounds: