Heartbeat Monitoring for Laravel
TL;DR
Heartbeat overview
Heartbeat monitoring is a specialized but simple type of monitoring used to track the health of processes, applications, or systems by periodically sending "heartbeat" signals to a monitoring service. These signals act as a status indicator, showing that a process or application is functioning as expected. If the heartbeat fails to arrive within a predefined time frame, an alert is triggered to inform web admins of a potential issue.
Create a new Heartbeat check in Acumen Logs
Within the Acumen Logs dashboard, navigate to Heartbeat in the side navigation. Then select the create button and add an identifiable name that you can recognise later. Then press save, you will then be redirected to your Heartbeat dashboard where you will find your unique endpoint which you can then use as shown in the example below.
Let's install a Heartbeat in the Laravel scheduler
1. Open your Laravel project and navigate to the below file.
App\Console\Kernel.php
2. Then within the schedule method call the heartbeat endpoint provided to you within the Acumen Logs dashboard
/**
* Define the application's command schedule.
*
* @param \Illuminate\Console\Scheduling\Schedule $schedule
* @return void
*/
protected function schedule(Schedule $schedule)
{
// Task a
// Task b
Http::post('https://acumenlogs.com/heartbeat/xxxx-xxxx-xxx-xxx-xxxx/pulse');
}
/**
* Define the application's command schedule.
*
* @param \Illuminate\Console\Scheduling\Schedule $schedule
* @return void
*/
protected function schedule(Schedule $schedule)
{
// Task a
// Task b
Http::post('https://acumenlogs.com/heartbeat/xxxx-xxxx-xxx-xxx-xxxx/pulse');
}
3. Run your scheduler and you will see the pulse registered in your dashboard
Key Takeaways
- Laravel background tasks and long-running queue processes regularly encounter silent logic timeouts without disrupting public web traffic configurations.
- Utilizing built-in framework execution hooks allows you to establish reliable background monitoring paths with zero external server dependencies.
- Continuous verification of data pipeline schedules protects critical transactional routines like midnight billing cycles and automated cleanups from breaking unnoticed.
