mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Disable interval checking in "Push" monitor type #1656
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1656
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @m-primo on GitHub (Dec 19, 2022).
⚠️ 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
-1value.📝 Additional Context
No response
@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..
@mandatoryoption commented on GitHub (Nov 2, 2023):
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 on GitHub (Dec 8, 2023):
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
Is there a reason why increasing the limit is not possible?
@chakflying commented on GitHub (Dec 9, 2023):
24 days is the limit for the Javascript
setTimeoutfunction.@CommanderStorm commented on GitHub (Dec 9, 2023):
Blocked by https://github.com/louislam/uptime-kuma/pull/3447