Your Honeybadger account comes with uptime monitoring. Our geographically distributed network of friendly robots will ping your site every few minutes. If a check fails, we'll let you know.
You can set up fairly sophisticated checks based on the HTTP status code, or the response body.
Just tell us which URL you want monitored. We'll ask you what you consider "success" - maybe you expect the HTTP response code to be 200, or maybe you expect the page to contain the words "all systems go". Here are your options:
- Success - notifies you that your site is down when your server responds with a non-20x status code. When in doubt, this is the one you probably want.
- Exact - prompts you to enter an HTTP status code. If you entered 302 it would ensure that the server responds with a 302 status code.
- Response body includes string - prompts you for a string (i.e. "Error") and notifies you when the response body matches.
- Response body excludes string - prompts you for a string and notifies you if the response body does not match.
You can also choose to send custom request headers or a custom request body, check the validity of the SSL certificate, and select which locations should be used for monitoring.
Hit "save" and you're done!
When your site goes down, we'll notify you with all the details about what went wrong:
By default, the notification is sent after half of the locations report a failing check. This means that if you are using five locations, there would need to be three failures in a row before you would receive an alert. You can override this default by specifying a value for the Outage Threshold field.
We'll also link you to a web page with details:
Public Status Page
If you'd like to share your uptime status with the world, you can enable the "Publish a public status page" option near the bottom of the page when editing your uptime check. Once enabled, you'll see a button on the detail view for your uptime check that links to the public status page.