|
By Pēteris Caune
Healthchecks.io ping endpoints accept HTTP HEAD, GET, and POST request methods. When using HTTP POST, clients can include an arbitrary payload in the request body. Healthchecks.io stores the first 100kB of the request body. If the request body is tiny, Healthchecks.io stores it in the PostgreSQL database. Otherwise, it stores it in S3-compatible object storage. We recently migrated from a managed to a self-hosted object storage.
|
By Pēteris Caune
I semi-recently bought a used Roborock S5 Max robot vacuum, and installed Valetudo on it. The installation process involves rooting the robot, and gaining SSH access to it. Which got me thinking, could I get the robot to ping Healthchecks.io at regular intervals? When the robot runs into a problem (closes a door after itself, gets stuck, chokes on a loose wire) and cannot return to the base, it eventually shuts down.
|
By Pēteris Caune
Starting from today, Healthchecks.io users on all plans (Hobbyist, Supporter, Business, Business Plus) can invite an unlimited number of users into their projects. Previously, the limits were: 3 team members for Hobbyist and Supporter, 10 team members for Business, and unlimited team members for Business Plus. From now on, it is unlimited for all.
|
By Pēteris Caune
Over the last few weeks, I indulged myself in doing a few “nice to have” website optimizations. They were.
|
By Pēteris Caune
Healthchecks.io can now classify HTTP pings from clients as start, success, or failure signals not only by URL suffixes (no suffix, /start, /fail, /{exit-status}) but also by looking for specific keywords or phrases in the HTTP request body. The content filtering feature was already available for email pings, and now it has been extended to HTTP pings as well.
|
By Pēteris Caune
URLs) receive spiky traffic:. The Healthchecks open-source project includes a fully functional, tested and type-annotated ping handler written in Python. On self-hosted Healthchecks instances, when you send an HTTP request to a ping URL, a Django view collects and validates information from the request, then uses Django ORM to update a Check object in the database and insert a Ping object in the database. This approach is good for tens to low hundreds of requests per second, depending on hardware.
|
By Pēteris Caune
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 Apprise integration, the Shell commands integration. A more niche feature that has come up a few times is the ability to serve Healthchecks on a subpath. Typically Healthchecks would run on a root level of a domain:.
|
By Pēteris Caune
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 POST request with an access token in a request header and the issue title, body, and labels in the request body. However, where do we get the access token from? The API call accepts three types of access tokens.
|
By Pēteris Caune
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 in Healthchecks supports.
|
By Pēteris Caune
Healthchecks.io launched in July 2015, which means this year we turn 9. Time flies! Previous status updates.
- April 2026 (1)
- March 2026 (1)
- February 2026 (1)
- January 2026 (1)
- December 2025 (1)
- July 2025 (1)
- March 2025 (2)
- October 2024 (1)
- July 2024 (1)
- November 2023 (1)
- July 2023 (1)
- May 2023 (2)
- January 2023 (2)
- November 2022 (1)
- September 2022 (1)
- May 2022 (1)
- April 2022 (1)
- February 2022 (1)
- November 2021 (1)
- October 2021 (1)
- September 2021 (2)
- July 2021 (1)
- January 2021 (1)
- November 2020 (2)
- May 2020 (1)
- January 2020 (2)
- August 2019 (1)
- April 2019 (1)
- February 2019 (1)
- October 2018 (1)
- August 2018 (1)
- June 2017 (1)
- December 2016 (1)
- May 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
Monitor cron jobs and get notified when they fail. Healthchecks.io monitors the heartbeat messages sent by your cron jobs, services and APIs. Get immediate alerts you when they don't arrive on schedule.
Make HTTP requests to the Ping URL at regular intervals. When the URL is not pinged on time, Healthchecks.io will send you an alert. You can monitor any service that can make HTTP requests or send emails.
What Can I Monitor With Healthchecks.io?
- Cron Jobs: Healthchecks.io monitoring is a great fit for cron jobs and cron-like systems (systemd timers, Jenkins build jobs, Windows Scheduled Tasks, wp-cron, uwsgi cron-like interface, Heroku Scheduler, ...). A failed cron job often has no immediate visible consequences, and can go unnoticed for a long time.
- Processes, Services, Servers: Healthchecks.io monitoring can be used for lightweight server monitoring: ensuring a particular system service, or the server as a whole is alive and healthy. Write a shell script that checks for a specific condition, and pings Healthchecks.io if successful. Run the shell script regularly.
Detect silent failures before your customers do.