Checks
Uptime monitoring isn't enough
A 200 OK response does not always mean everything is ok. The page may load fine but let's say your queue workers crashed, so emails are not going out. Sound familiar?
Today, any sufficiently complex Laravel project:
- Connects to a database
- Utilizes cache
- Sends email
- Talks to 3rd party APIs
- Runs scheduled tasks / cronjobs
On top of that, there are other concerns such as server health. What if your server's disk is 95% full? That's just a problem waiting to happen soon.
It must be clear now why you need to monitor every single component of your Laravel project, all the time. Got a critical scheduled task? Monitor it. Scared of running out of disk space? Monitor that as well. What if your database server crashes? You get the point...
How can I monitor my Laravel application?
To set up application monitoring, you need to install our Laravel package, which ships with useful default checks that make sense for any Laravel application.
For further information, explore our Laravel package.
Incidents
Whenever there's a failing check, we will raise an incident and you will be notified.
To customize how you will be notified, see notifcations.
Data Logging
Besides signaling warnings and failures, checks can be used to collect metrics from your application as well.
Business Metrics and Alarms
App:keep allows you to write custom checks. You can use this creatively and implement business metrics and alarms. Here are some ideas:
- Monitor the rate of failed payments.
- Ensure an external API or service is up.
- Monitor the number of sign-ups or orders.