louislam / uptime-kuma

A fancy self-hosted monitoring tool
https://uptime.kuma.pet
MIT License
54.98k stars 4.95k forks source link

Disable interval checking in "Push" monitor type #2440

Open m-primo opened 1 year ago

m-primo commented 1 year ago

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

🏷️ 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

📝 Additional Context

No response

CommanderStorm commented 1 year ago

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..

mandatoryoption commented 9 months ago

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.

CommanderStorm commented 8 months ago

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?

chakflying commented 8 months ago

24 days is the limit for the Javascript setTimeout function.

CommanderStorm commented 8 months ago

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