Laravel error tracking with Rollbar
Instantly know when Laravel errors occur and how to fix them
Get Laravel exception & crash reports in real-time.
Track & debug Laravel bugs in record time.
Real-time error reporting
Laravel errors are tracked by Rollbar instantly as they occur. Get notified of errors and how to fix them throughout the software development process.
Similar errors are automatically grouped using Rollbar's fingerprinting technology to reduce noise, and all errors include detailed data to help you assess impact and assign priority.
Error details & metadata
Rollbar automatically collects all the data you need to replicate and debug an error, presented in ways optimized for debugging speed.
Get stack traces, request parameters, local variables, affected users and IP addresses, browsers and OSes, deployed code versions, and more.
Local variables & arguments
Local variables and arguments can help you debug problems faster by showing you the state of the application when the error was created.
You can view their values directly from the stack trace, and know exactly how to reproduce an error locally because you can see what triggered it.
Works with your stack
Rollbar supports all popular languages and frameworks:
Rollbar allows us to go from alerting to impact analysis and resolution in a matter of minutes. Without it, we would be flying blind.
Quick setup with our lightweight & open source SDK
Rollbar SDK for Laravel 5.6 and up
This library adds a listener to Laravel's logging component. Laravel's session information will be sent into Rollbar, as well as some other helpful information such as environment, server, and session
Installation
Start monitoring errors now
14-day unlimited errors free trial. 5,000 errors/month free forever.
Setting up ROLLBAR_TOKEN in .env should be enough for basic configuration.
The level setting defines the minimum log level at which log messages are sent to Rollbar. If not specified, the default is debug. For development, you could set this either to debug to send all log messages or to none to send no messages at all. For production, you could set this to error so that all info and debug messages are ignored...