starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Harmonogram/calendar of monitoring? #2367

New issue

Closed

opened 2026-02-28 02:52:13 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 02:52:13 -05:00

Owner

Originally created by @koles142 on GitHub (Jul 11, 2023).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Hi, I solid like to ask about harmonogram/calendar of monitoring. My case: I have a business and use a lot of mobile devices. I would like monitor it, because any failure in opening hours generate cost for me. After opening hours these devices are turned off. In this case every day I will have a lot of notifications, which are false for me.

✔️ Solution

Calendar in gui where I can define (per host) which monitored host can send me pushes eg.: Tablet in opening hours 8:00-16:00 can send me the push when has problem or is offline, but after this time not. Game changer will be possibilites check free days, holidays, christmas etc. with disabled norifications.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @koles142 on GitHub (Jul 11, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description Hi, I solid like to ask about harmonogram/calendar of monitoring. My case: I have a business and use a lot of mobile devices. I would like monitor it, because any failure in opening hours generate cost for me. After opening hours these devices are turned off. In this case every day I will have a lot of notifications, which are false for me. ### ✔️ Solution Calendar in gui where I can define (per host) which monitored host can send me pushes eg.: Tablet in opening hours 8:00-16:00 can send me the push when has problem or is offline, but after this time not. Game changer will be possibilites check free days, holidays, christmas etc. with disabled norifications. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:52:13 -05:00

closed this issue
added the
feature-request

A:maintenance
labels

deekerman commented

2026-02-28 02:52:19 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 11, 2023):

What is the difference to the schedulable maintenance mode currently implemented?

@CommanderStorm commented on GitHub (Jul 11, 2023): What is the difference to the schedulable maintenance mode currently implemented?

deekerman commented

2026-02-28 02:52:19 -05:00

Author

Owner

@koles142 commented on GitHub (Jul 12, 2023):

In currently schedulable maintenance I can’t set repeat every year, have only option every day and month. In this case I can’t set maintenance eg. every christmas or free days.

@koles142 commented on GitHub (Jul 12, 2023): In currently schedulable maintenance I can’t set repeat every year, have only option every day and month. In this case I can’t set maintenance eg. every christmas or free days.

deekerman commented

2026-02-28 02:52:19 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 12, 2023):

You can schedule it via cron:

https://crontab.guru/#_24-26_12*

@CommanderStorm commented on GitHub (Jul 12, 2023): You can schedule it via cron: - ![image](https://github.com/louislam/uptime-kuma/assets/26258709/c220432b-57f1-4e35-bbb9-62bd3d055815) - https://crontab.guru/#*_*_24-26_12_*

deekerman commented

2026-02-28 02:52:19 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Aug 1, 2023):

@koles142
I think the feature you are requesting is already implemented.
If you agree, could you please close this issue, as duplicates only create immortal zombies and are really hard to issue-manage.
If not, what makes this issue different from already implemented functionality?

@CommanderStorm commented on GitHub (Aug 1, 2023): @koles142 I think the feature you are requesting is already implemented. If you agree, could you please close this issue, as duplicates only create immortal zombies and are really hard to issue-manage. If not, what makes this issue different from already implemented functionality?

deekerman commented

2026-02-28 02:52:19 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 16, 2024):

@koles142
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #1984 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Feb 16, 2024): @koles142 We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #1984 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo) ⇒ I am going to close this as a duplicate.