Scheduled monitoring pause

[NickBootOne]

Is your feature request related to a problem? Please describe
If a Docker Container is being updated, I get a notification of all de Dockers Containers that gets an update.
This is also for backing up all the Containers

Describe the solution you'd like
A scheduled pause for the monitoring when the backup or update process is plannend

[hkpanchani]

It would be great to have repetitive scheduled maintenance.
One of our server is scheduled to maintain 2am every Saturday.

It would be great to auto pause monitor at 1:55 am to 2:05am.

[jtagcat]

GitHub Etiquette

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

[Saibamen]

IMO it will be nice to also create Incident in status page

[federicotravaini]

It would be great to have repetitive scheduled maintenance. One of our server is scheduled to maintain 2am every Saturday.

It would be great to auto pause monitor at 1:55 am to 2:05am.

this is absolutely a must have feature since many services have scheduled start-stop time

[simphide]

Any news regarding this feature request?

[bodzio4749]

Having scheduled downtimes is a super idea. I have a backup Synology server, which stays powered off most of the week. It is powered on by the master server only for a few hours on weekends to receive volume snapshots. Having a "normal down" and scheduled "uptime " states, based on the scheduled timetable, would be a perfect solution to a "negative" watch-only option.

[alexsahka]

Any news?
I have 8 Security Cameras doing a scheduled reboot every night. A scheduled pause for the monitoring is needed. Thanks.

[RyanWor]

Any news? I have 8 Security Cameras doing a scheduled reboot every night. A scheduled pause for the monitoring is needed. Thanks.

The only real workaround I've found for this right now is just to stop the uptime-kuma container during maintenance windows. Of course this is an extremely inelegant solution and not something that can be justified in a production environment if uptime-kuma were still monitoring other critical services but it is what it is right now. The application is still very new and it's far easier and better than most other things I've tried so I'll be patient until either monitor pause scheduling/downtime windows are implemented or an API is exposed to allow my scripts to pause/unpause monitors. Other possible alternatives could be filtering the alerts uptime-kuma outputs yourself through some method which doesn't pass certain alerts during certain time periods (but of course that kinda defeats the simplicity of uptime-kuma in the first place).

[chakflying]

Thinking about this, I see 2 ways of doing this.

• Literally as the title suggest, allow the user to define a time when monitor pause should be triggered, and a time when monitor resume should be triggered. This list is stored in database, then maybe there is a background job checking every minute which monitor should be paused and which should be resumed, and execute it.

• Allow the user to define the expected state of the monitor on a timeline. For example, the user can set 00:00 - 00:02, the target should be down. The monitor keeps running normally, but it will compare the checked state of the target with the expected state, and only send notification if they are different. This has the advantage of working nicely with the currently "inverted monitor" option, and the monitor keeps gathering data.

[RyanWor]

Honestly the best approach in my opinion would be something similar to how Uptime Robot implements schedules. You have certain named "maintenance windows" and similar to notifications they can be enabled/disabled per monitor. That way when you have Uptime Kuma monitoring a dozen or more services on the same host they can easily be assigned the same window dynamically since they'd be expected to be down together frequently.

Alternatively (or in addition too, something I wished UR had forever) is alerts can be chained. Example: If HostA ping monitor fails, don't alert on HostA-Service1, HostA-Service2, and HostA-Service3. One server down alert that mutes 20 more service down alerts would be extremely welcome and eliminate the vast majority of alerts I get for "known down" situations.

[Peppershade]

This is a must-have. The best way to do it is on a per monitor base. We have many services that have scheduled restarts at night, already woke me up once. The other way would be to disable the notification channel between a certain time. That would also be helpful enough.

[douglasparker]

I'm hoping PR #1213 gets implemented!

I really need maintenance windows to avoid email notification spam filling my inbox during backup and update windows.

[athornfam2]

Just adding to this... Would be nice to have a one-time and continuous start and stop monitoring option. Single use for maintenance and continuous use for VM's (example - a VPN server that's turned off after business hours to save on money).

[kristiandg]

Some additional desired behavior:

The ability to schedule a maintenance window, and indicate which monitors are impacted, so they don't alert during that time (selectable to not alert, alert maintenance start/end, and alert as normal).

When a maintenance schedule is created, at the start of the window, the impacted monitors (selected at the time of creation), will go into a new mode that shows "Maintenance" (could even do this by displaying the monitor with a quaint "construction barber pole yellow/black banner over the monitor, or a set of emojis).

For alerts, if set to start/end, alerts would be send at the beginning/end of the maintenance window only. If alert as normal was set, then it would still send alerts, but an added line would indicate it's currently in maintenance so the alert should be treated accordingly.

If accessible from the API, might even allow someone's existing ticketing system to auto build maintenance windows based on approved/scheduled change activity.