Turn a missed cron into a GitHub or Linear ticket
Email is a bad place for “the backup never ran.” You get the Down ping, maybe a Slack message, then it scrolls off. The job that failed is sitting next to a GitHub repo or a Linear team. That is where someone actually closes work. Gonewatch now opens a ticket when a monitor misses its window — GitHub Issues or Linear — instead of only sending chat. Chat vs ticket Slack, Discord, and Telegram are…
Gonewatch provides a solution to the issue of missed cron jobs by automating the creation of GitHub Issues or Linear tickets when a monitor fails to run as scheduled. Instead of relying solely on email notifications, Gonewatch integrates with these platforms to facilitate proper work tracking and resolution.
When a job succeeds, Gonewatch posts a heartbeat and sends a JSON payload to the dashboard, ensuring the job's status is always up to date. However, if a monitor misses its window, Gonewatch recognizes the failure and marks the monitor as Down. This triggers the creation of a new issue or a ticket in GitHub Issues or Linear, depending on the user's preference.
The issue or ticket contains essential information such as the job's schedule, the last heartbeat, and a link to the monitor responsible for the task. This provides a clear reference for the team to investigate and resolve the problem. JSON payloads remain on the dashboard, allowing for continuous monitoring without cluttering the ticket with unnecessary details.
Gonewatch smartly manages the workflow by reopening the issue or ticket if the job is still Down, ensuring that the issue remains open until the problem is resolved. Once the job succeeds, Gonewatch comments on the ticket, marking it as Up or Done, depending on the chosen platform. This helps keep track of the job's status and prevents confusion when multiple attempts are made.
Furthermore, Gonewatch avoids spamming tickets for each hour of a failed job. The system opens a new issue or ticket only when a missed heartbeat occurs, ensuring that the team focuses on resolving the actual issues rather than being inundated with trivial reminders.
To set up Gonewatch, users can connect their GitHub or Linear account within the Gonewatch settings. They then install the Gonewatch app on the desired repository or team. Once connected, Gonewatch listens for monitor heartbeats and automatically creates the corresponding GitHub Issues or Linear tickets when a job fails to run.
Similar to Slack, Discord, and Telegram, Gonewatch maintains a consistent heartbeat mechanism, ensuring that the job's success or failure is always acknowledged. The process is straightforward: the job sends a POST request upon successful completion, and Gonewatch marks the monitor as Up. Conversely, if a monitor fails to send the heartbeat within the expected timeframe, Gonewatch automatically marks it as Down and creates the appropriate issue or ticket.
Gonewatch offers a free plan that still provides email notifications for missed jobs, while more advanced features, such as GitHub Issues and Linear tickets, are available in the Basic and Pro tiers. By automating the creation of work-tracking tickets, Gonewatch empowers teams to efficiently address missed cron jobs, ensuring that no critical tasks are overlooked.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
