-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a cron monitore #1482
Comments
I don't think this will be a thing for uptime kuma. Its more for web things like websites, dns records and so one but not for cronjobs. |
I think this is a great idea. I don't see why uptime-kuma couldn't be used to monitor cronjobs, it would do the job just fine. If there are push monitors, why not time range push. |
That's what I think too. The time interval alone is not sufficient for monitoring the status of the task. |
It would be great to have an api that would allow to send POSTs to know if our cronjob was successful or not. A bit like betteruptime does |
This comment was marked as spam.
This comment was marked as spam.
I'm also interested in this functionality, similiar to what cronitor does: https://cronitor.io/cron-job-monitoring I the feature itself would be interesting, I'm willing to create a PR for that |
Changing the monitor sheduler is a lot of work. |
🏷️ Feature Request Type
New Monitor, UI Feature
🔖 Feature description
To monitore cron, it's easier to send OK/NOK with curl (like healthcheck.io) or if cron don't execute after specific time it raise an alert.
I see push monitore and I think it can have a little improvement : set Heartbeat interval in second or cron execution format.
For exemple I want to monitore a cron who execute each monday at 3AM, I can define 604800 in interval, or define
0 3 * * 1
in interface to monitore the cron✔️ Solution
Add in push monitor a way to select interval or cron execution time format.
❓ Alternatives
Healtcheck.io can work (it work) but multiplying the tools can be a bit of a headache
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: