📑 I have found these related issues/pull requests
#3447 – An old PR (almost 3 years) that was not merged/finished, which worked on a technical limitation that caused Uptime Kuma to only allow a maximum of 24 days of interval.
But I did not find an open Issue/PR related to my feature request, that I could like/+1.
So I wanted to create a ticket to track that need/desire.
🔖 Feature description
It would be great if Heartbeat Interval allows for more than just 24 days. Specifically at least 30 days.
Use-Case: A cron/scheduled task that runs once per month (e.g. a big backup) that reports its success (once a month).
✔️ Solution
The Heartbeat Interval field/input for the Monitor Type Push needs to accept 30 days or more as a value.
❓ Alternatives
A potential workaround is combining it with the Retries setting, which only turns the monitor yellow/orange.
But this gives you a wrong picture about this status monitor and you need to know that it might just be yellow/orange, because 30 days are not yet 'done' etc.
📝 Additional Context
No response
📑 I have found these related issues/pull requests
#3447 – An old PR (almost 3 years) that was not merged/finished, which worked on a technical limitation that caused Uptime Kuma to only allow a maximum of 24 days of interval.
But I did not find an open Issue/PR related to my feature request, that I could like/+1.
So I wanted to create a ticket to track that need/desire.
🔖 Feature description
It would be great if Heartbeat Interval allows for more than just 24 days. Specifically at least 30 days.
Use-Case: A cron/scheduled task that runs once per month (e.g. a big backup) that reports its success (once a month).
✔️ Solution
The Heartbeat Interval field/input for the Monitor Type Push needs to accept 30 days or more as a value.
❓ Alternatives
A potential workaround is combining it with the Retries setting, which only turns the monitor yellow/orange.
But this gives you a wrong picture about this status monitor and you need to know that it might just be yellow/orange, because 30 days are not yet 'done' etc.
📝 Additional Context
No response