Alerts that repeat every week

This article is for anyone who gets the same InfraNest alert or sees the same server restart, week after week, and wants InfraNest to stop treating it as a surprise.

#Overview

• Some alerts aren't actually news — a nightly backup that spikes CPU, or a weekly update that restarts a server.
• InfraNest watches for patterns: the same alert firing at the same hour on the same day of the week, three weeks running or more, and still happening in the last week.
• When it spots a pattern, it offers a fix under Watch better on the Monitors page, and on the server's Alerts & rules tab.
• Real problems are never hidden — only the expected, repeating noise is quieted.

#Quiet a repeating alert rule

Use this when the same alert rule keeps firing at the same time every week (for example, CPU alerts every night at the same hour).

1. Look for a suggestion such as CPU on db-01 alerts at the same time, week after week under Watch better on the Monitors page, or on the server's Alerts & rules tab.
2. Read the details — when it fired, how many weeks running, and how high the metric normally goes the rest of the week. If you marked past incidents as Expected, your own note (such as "nightly backup") is shown back to you.
3. Select Stay quiet only then.
4. Confirm the choice.

From then on, that rule on that server stays quiet at that time only — for example, every day from 02:00–03:00 — and keeps its usual threshold for the rest of the week.

NoteStaying quiet doesn't hide trouble that lasts. If the breach is still happening when the quiet time ends, you're alerted then. Outside the quiet time, the rule alerts exactly as before, and only that one rule on that one server is affected.

You can also set this directly from the rule: on the server's Alerts & rules tab, the rule's Last 30 days card shows a Stay quiet only then button whenever it detects the same pattern.

TipInfraNest only offers a quiet time when the rest of the week stays under the alert line. If the server crosses the line at other hours too, you may be offered a different fix instead, since a quiet time wouldn't help.

#See or remove a quiet time

1. Go to the server's Alerts & rules tab.
2. Find the rule — if it has a quiet time, its row shows something like Quiet: every day, 02:00–03:00.
3. To remove it, select the × beside it (Alert then again).

Each change is recorded in the Audit Log as Quiet times changed, along with what the setting was before.

#Handle a server that restarts at the same time every week

Use this when a server reboots at the same hour on the same day, week after week (usually its own update process).

1. Look for a suggestion such as web-01 restarts at the same time every week under Watch better on the Monitors page, or on the server's Alerts & rules tab.
2. Choose one of two options:
   • Add a weekly window — opens the maintenance form, already filled in for that server, day, and hour. Review it and select Save.
   • Reboot safely instead — opens the server with Reboot safely set to the server's quietest time, which may be a different day and hour than its current restart time. Check the time shown in the dialog, then confirm.
3. If you choose Reboot safely instead, also switch off the server's own automatic restart, so it doesn't restart twice.

Nothing changes until you save the window or confirm the scheduled reboot.

#Tips

• Times shown are in your workspace's timezone — the same one used for maintenance windows.
• A restart that InfraNest itself performed (a reboot you scheduled, or one run by an automation) is never counted toward a pattern.
• A suggestion disappears once the pattern has a quiet time or window set, or once it stops happening for a week.
• Selecting Not needed hides a suggestion for the whole workspace. Select Show again to bring it back.