Disable interval checking in "Push" monitor type #1656

Open
opened 2026-02-28 02:28:34 -05:00 by deekerman · 5 comments
Owner

Originally created by @m-primo on GitHub (Dec 19, 2022).

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

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

API, UI Feature, Other

🔖 Feature description

A suggestion to disable the interval checking in Push Monitor Type; to be only called when the url get called.

✔️ Solution

I recommend a checkbox in front of the "Heartbeat Interval", when checked it'll disable interval checking.

Alternatives

  • An alternative to that checkbox, to allow the interval input to accept a literal -1 value.

📝 Additional Context

No response

Originally created by @m-primo on GitHub (Dec 19, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type API, UI Feature, Other ### 🔖 Feature description A suggestion to disable the interval checking in `Push Monitor Type`; to be only called when the url get called. ### ✔️ Solution I recommend a checkbox in front of the "**Heartbeat Interval**", when checked it'll disable interval checking. ### ❓ Alternatives - An alternative to that checkbox, to allow the interval input to accept a literal `-1` value. ### 📝 Additional Context _No response_
Author
Owner

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

This would essentially make the Push monitor basically brain-dead

=> It could never notify for missing intervals/missing pushes
=> I doubt that this is what you want..

@CommanderStorm commented on GitHub (Aug 4, 2023): This would essentially make the Push monitor basically brain-dead => It could never notify for missing intervals/missing pushes => I doubt that this is what you want..
Author
Owner

@mandatoryoption commented on GitHub (Nov 2, 2023):

This would essentially make the Push monitor basically brain-dead

=> It could never notify for missing intervals/missing pushes
=> I doubt that this is what you want..

I found myself wanting this specific feature, and I'll explain how I think it could be useful.

I have a backup server that runs only when actually preforming backups of the data from my main server. On my backup server is a script that runs checks every other time it is booted. I might not bring this server online for over a month because there is no new data to sync. If my script detects and error, I would then push a different status.

Currently the limit for intervals is 24 days, so its entirely possible I could exceed that. Realistically I dont care if the server is down because it doesnt need to remain online all the time.

I could invert the status and only call the push url when an issue is detected but ideally I'd only like to see a green when a check was run and no issues were found.

Its an edge case I know but one I think there is some value in.

@mandatoryoption commented on GitHub (Nov 2, 2023): > This would essentially make the Push monitor basically brain-dead > > => It could never notify for missing intervals/missing pushes > => I doubt that this is what you want.. I found myself wanting this specific feature, and I'll explain how I think it could be useful. I have a backup server that runs only when actually preforming backups of the data from my main server. On my backup server is a script that runs checks every other time it is booted. I might not bring this server online for over a month because there is no new data to sync. If my script detects and error, I would then push a different status. Currently the limit for intervals is 24 days, so its entirely possible I could exceed that. Realistically I dont care if the server is down because it doesnt need to remain online all the time. I could invert the status and only call the push url when an issue is detected but ideally I'd only like to see a green when a check was run and no issues were found. Its an edge case I know but one I think there is some value in.
Author
Owner

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

This would essentially make the Push monitor basically brain-dead

Not only would this make the monitor basically brain dead, this would make it useless as it would be up all the time.
=> #1386 is needed to be functional

Currently the limit for intervals is 24 days, so its entirely possible I could exceed that

Is there a reason why increasing the limit is not possible?

@CommanderStorm commented on GitHub (Dec 8, 2023): > This would essentially make the Push monitor basically brain-dead Not only would this make the monitor basically brain dead, this would make it useless as it would be up all the time. => #1386 is needed to be functional > Currently the limit for intervals is 24 days, so its entirely possible I could exceed that Is there a reason why increasing the limit is not possible?
Author
Owner

@chakflying commented on GitHub (Dec 9, 2023):

24 days is the limit for the Javascript setTimeout function.

@chakflying commented on GitHub (Dec 9, 2023): 24 days is the limit for the Javascript `setTimeout` function.
Author
Owner

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

Blocked by https://github.com/louislam/uptime-kuma/pull/3447

@CommanderStorm commented on GitHub (Dec 9, 2023): Blocked by https://github.com/louislam/uptime-kuma/pull/3447
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1656
No description provided.