cronhub / product-roadmap Goto Github PK

I tried to create scheduler by http post request on create endpoint but I get a Html page as response.

Schedules like every hour, once a day, etc. This will be an addition to the existing cron schedules.

See screenshot:

Number of times jobs ran in the past month has some ticks at 2.5, 7.5, 12.5. This seems like a weird place to put ticks, as you can't run 1/2 of a job.

When a new monitor is pinged for the first time we send "Your monitor is up" alert. It's the same time when monitor recovers from the "down" state. We should have a different type of alert.

It would be great to have a timeline metric and an alert when tasks are going to overlap each other.

As cron tasks usually are using for processing some heavy job in a background, there is a common error when the task starting to work slower and slower and finally, it overlaps with another run of the task and they begin to work simultaneously.

Also, a timeline can help you to set a proper start time for a new task to prevent overloading a server.

I think the best visualisation is something like this https://luna1.co/6ad8cc.png. With hours on X-axis and different tasks along the Y-axis.

Upon receiving /fail ping Cronhub should alert the user.

Having an API will allow Cronhub users to pull the status of their monitors. The API is also a foundation for many things I want to accomplish like shared dashboard, heroku add-on, etc.

A command line interface that eases the process of integration of your cronjob with Cronhub monitors.

Currently, you have to manually integrate Cronhub monitors with your cron jobs and it's not ideal. I think it could be better.

When a monitor is down it will be useful to send occasional reminders.

We send the same "Your X monitor is up" alerts for these cases:

1. When a new monitor is activated
2. Monitor goes from "down" to "up" state

We should differentiate the type of alert for 2.

There will be a new monitor section to display the logs of the running job. This means that you can send data to an existing monitor.

Would be nice to set an account-wide or cronjob specific timezone setting for easier readability of the last ping date

In the weekly email we should include:

• The number of times a monitor ran in the last week
• The number of times an error/alert was triggered