The Joy of Building a Cron Monitoring Service| Healthchecks.io
Starting from January 1, 2023, our ping endpoints (hc-ping.com, hchk.io) will reject requests from the Russian Federation IP addresses. The web dashboard at https://healthchecks.io will remain accessible and functional. We've sent email notifications to the affected user accounts. The rejected p| Healthchecks.io
Due to the nature of cron jobs, our ping endpoints (https://hc-ping.com/... URLs) receive spiky traffic: On average we write ~500 ping requests/second to the database. At the start of every minute, we write around 4000 pings/second. At the start of every hour, we write over 10'000 pings/se| Healthchecks.io
On April 30, starting from 15:46 UTC, Healthchecks.io was unavailable for about 30 minutes. The outage was caused by, most likely, hardware instability on the database server. The PostgreSQL server crashed with a segfault, and a little later, the entire server stopped responding to pings. The system| Healthchecks.io
I am designing and developing Healthchecks with the primary goal of running the hosted service at https://healthchecks.io. But I am also happy to incorporate features that enable or simplify self-hosting use cases. Examples include the first-party Docker image, the remote authentication support, the| Healthchecks.io
Healthchecks can now notify you about a failing check by opening a new issue in your chosen GitHub repository. Here is an example of how the GitHub issue might look: The technical side of creating a new issue is straightforward: GitHub has an API call for creating an issue. You make an HTTP P| Healthchecks.io
Webhooks are a powerful way to notify external systems about checks changing state in Healthchecks.io. Webhook notifications are available to all user accounts, paid and free. Webhooks were the second notification method supported by Healthchecks (the first one was email). The webhook delivery code started as a simple requests.get(user_supplied_url) and evolved. Today, the webhook integration …How Healthchecks.io Sends Webhook Notifications Read More »| Healthchecks.io
On July 2, 2024 we received a notice from Twilio, our SMS provider, about a data leak involving IdentifyMobile, one of their downstream carriers. The downstream carrier had made an AWS S3 bucket public from May 10-15, 2024. The bucket contained message-related data sent between January 1, 2024, and| Healthchecks.io
Healthchecks.io launched in July 2015, which means this year we turn 9. Time flies! Previous status updates: In 2018, My One-person SaaS Side Project Celebrates its Third Birthday In 2021, Healthchecks Turns 6, Status Update Money Healthchecks.io currently has 652 paying customers,| Healthchecks.io
Healthchecks now supports OnCalendar schedules, used for scheduling tasks with systemd timers. Here's what's new: when creating a check, you can now switch between "Simple", "Cron" and "OnCalendar" schedules: You can also edit schedules (and switch schedule types) for existing checks:| Healthchecks.io
In this post I’m comparing cron monitoring features of four services: Cronitor, Healthchecks.io, Uptime Robot, Sentry. How I picked the services for comparison: I searched for “cron monitoring” on Google and picked the top results in their order of appearance. Disclaimer: I run Healthchecks.io| Healthchecks.io
Since a little more than two months ago, Healthchecks.io has been sending transactional email (~300'000 emails per month) through its own SMTP server. Here are my notes on setting it up. The Before Before going self-hosted, Healthchecks sent email using 3rd-party SMTP relays: AWS SES and later| Healthchecks.io