Instantly know when Spring errors occur and how to fix them
Spring 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.
Rollbar automatically collects all the data you need to replicate and debug an error, presented in ways optimized for debugging speed.
Works with ProGuard obfuscations.
Get stack traces, request parameters, local variables, affected users and IP addresses, browsers and OSes, deployed code versions, and more.
RQL (Rollbar Query Language) allows you to perform data analysis and build custom reports on your error data, using a familiar SQL-like language.
You can use RQL to get answers to very specific questions, e.g. "How many users are getting 404 errors right now, grouped by referring URLs?"
RQL is also accessible via API.
Rollbar supports all popular languages and frameworks:
The fact that we’re ramping up continuous deployment for a lot of our services - is only doable because we have Rollbar integrated. Rollbar is so tightly coupled into the way we work, it seems part of our system as a whole.
How to configure rollbar-java to work with Spring MVC
Rollbar offers error monitoring integration for Spring MVC apps through the Java & Android SDK. This guide will show you how to add a global exception handler to catch all uncaught errors in your Spring app. It will also send helpful information from the request like the remote IP address.
If you require direct access to the underlying API objects include rollbar-api
as a dependency. For Android include rollbar-android
. For web projects include rollbar-web
.
14-day unlimited errors free trial. 5,000 errors/month free forever.
If you use ProGuard to obfuscate your code in production, reported stack traces will not be very useful in most cases.
ProGuard Deobfuscation
Rollbar provides a way for you to upload the mapping.txt file generated in the obfuscation process so that stack traces can be deobfuscated as they are reported...