At Honeybadger, it's our goal to monitor your app anywhere it can fail in production.
We started with exception tracking, which gives you fine-grained error reports when your application experiences an error.
Next, we added uptime monitoring to ensure that your HTTP endpoints and APIs are always available and responding properly.
Today we are flipping ecstatic to introduce a new feature to the Honeybadger toolchain: Check-Ins!
How it Works
Check-Ins are kind of like Uptime monitoring, but in reverse: instead of Honeybadger periodically pinging a URL which you provide, with Check-Ins, you ping Honeybadger—or as we say, you "check in".
If you ever stop checking in, Honeybadger will alert you using all of your existing alerts and integrations. Simple, yet powerful.
If you have periodic background jobs (like cron jobs) or micro-services which may not be publicly available via HTTP, Check-Ins is a great new way to monitor them; if they ever go away or stop doing their job, we'll let you know about it.
Getting started with Check-Ins is super easy. Everyone who is on one of our current plans has Check-Ins enabled by default. If you're on an old plan, you can upgrade to one of the new plans to get Check-Ins for around the same price as you're paying now.
To configure your first Check-In, head to your Honeybadger project and click on the new "Check-Ins" tab (right next to Uptime). When you create a Check-In, we'll give you a unique URL that you can request every time you check-in. Here's an example of a cron job which uses
curl to check-in if the job completes successfully:
@hourly /usr/bin/do_something && curl https://api.honeybadger.io/v1/check_in/xyzzy &> /dev/null
You can request your check-in URL via any method—GET, POST, PUT, PATCH, HEAD, and from any language that has an HTTP library (which is all of them, except maybe assembler).
To learn more about Check-Ins, check out the documentation. If you have any questions, email the Honeybadger founders — Josh, Ben, or Starr — at firstname.lastname@example.org.