Skip to content

[DOCS-13651] Add warning for custom schedules and decommissioned hosts #35304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
estherk15 wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −0
Open

[DOCS-13651] Add warning for custom schedules and decommissioned hosts #35304

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/en/monitors/guide/why-did-my-monitor-settings-change-not-take-effect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<div class="alert alert-danger">If a Custom Schedule is applied to a monitor, decommissioned hosts continue to be evaluated past the standard retention window. For more information, see <a href="/monitors/guide/custom_schedules">Custom Schedules</a>.</div>

### Workarounds

If you need to remove the old hostname from alerts before the retention period expires, you can use one of the following workarounds:
Expand Down
Loading