timetable not to do checks #567

New issue

Closed

opened 2026-02-28 01:50:46 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 01:50:46 -05:00

Owner

Originally created by @rubvaz on GitHub (Nov 16, 2021).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

Hello, you are doing a very good job but I think that a new feature that give the option to configure down times where the checks should not be done.

✔️ Solution

Have a time table where we can set the time where we do not want the monitor to notify a down.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @rubvaz on GitHub (Nov 16, 2021). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description Hello, you are doing a very good job but I think that a new feature that give the option to configure down times where the checks should not be done. ### ✔️ Solution Have a time table where we can set the time where we do not want the monitor to notify a down. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 01:50:46 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 01:50:52 -05:00

Author

Owner

@deefdragon commented on GitHub (Nov 17, 2021):

Duplicate of #900 (#233) for scheduled downtime for notifications, and #191 for periodic scheduled downtime

@deefdragon commented on GitHub (Nov 17, 2021): Duplicate of #900 (#233) for scheduled downtime for notifications, and #191 for periodic scheduled downtime

deekerman commented

2026-02-28 01:50:52 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 4, 2023):

This issue is resolved as maintenance periods offer this scheduling behaviour.
It is unclear when they were added, but it has been a while ^^

=> closing as resolved

@CommanderStorm commented on GitHub (Dec 4, 2023): This issue is resolved as maintenance periods offer this scheduling behaviour. It is unclear when they were added, but it has been a while ^^ => closing as resolved