WordPress error logging with Rollbar
Instantly know when WordPress errors occur and how to fix them
Get exception & crash reports in real-time.
Track & debug bugs in record time.
Real-time error reporting
WordPress 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. Works with JavaScript source maps.
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.
Using Rollbar I don’t have to spend time trying to reproduce errors on my own. It tells me what the steps are. Rollbar empowers your team to be able to sort through issues and turn things around quickly.
Quick setup with our lightweight & open source SDK
Rollbar SDK for Wordpress
The easiest way to install the plugin is from the WordPress Plugin directory. If you have an existing WordPress installation and you want to add Rollbar:
1.In your WordPress administration panel go to Plugins → Add New
Start monitoring errors now
14-day unlimited errors free trial. 5,000 errors/month free forever.
Rollbar.js provides a configuration option captureUncaught which allows you to control if uncaught exceptions should automatically reported to Rollbar.
Rollbar PHP SDK allows you the same, but in a slightly different way. Rollbar::init takes the 2nd, 3rd and 4th argument which control if exceptions, errors and fatal errors are going to be reported to Rollbar. The default behavior is to report everything to Rollbar automatically...