Declaring check-ins in PHP/Laravel config

You can now configure your check-ins without leaving your codebase. No more tabbing between Honeybadger and your code to declare and set up check-ins.

If your cron job fails in a forest, and nobody is around, does it make a sound?

Honeybadger's check-in monitoring for PHP/Laravel gives you peace of mind, knowing that if any job fails, whether it's your billing cron job, your nightly backup, or even that third-party service's new integration, it won't happen silently. Instead, we'll notify you instantly via the tools you already use (Slack, PagerDuty, etc.).

Sometimes—especially if you have many jobs to monitor—configuring a check-in for each job can be tedious. Before today, you'd perform manual steps and copy/paste each check-in ID into your Laravel codebase.

Today, we're making managing check-ins in Laravel apps much easier: you can now create and manage check-ins from a config file in your codebase! No more tabbing back and forth between Honeybadger and your code. Define your check-ins in your PHP/Laravel configuration and run our new synchronization command when you deploy—our plugin will handle the rest.

check-ins synchronization

Configuring check-ins within your version control system lets you take advantage of git features such as the commit history, so you know what changed and when.

We've also eliminated the need to copy/paste randomly generated identifiers—you can now use the check-in's name.

configuring check-ins

If you already use Honeybadger's check-in monitoring, this feature will speed up your workflow. If you aren't using our check-in monitoring, now it's easier than ever to get started.

Check out the docs to learn more!

What to do next:
  1. Try Honeybadger for FREE
    Honeybadger helps you find and fix errors before your users can even report them. Get set up in minutes and check monitoring off your to-do list.
    Start free trial
    Easy 5-minute setup — No credit card required
  2. Get the Honeybadger newsletter
    Each month we share news, best practices, and stories from the DevOps & monitoring community—exclusively for developers like you.