Scala error logging with Rollbar
Instantly know when Scala errors occur and how to fix them
Get exception & crash reports in real-time. Track & debug bugs in record time.
Real-time error reporting
Get notified of Scala errors instantly as they occur after deployment - and before users notice.
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 ProGuard obfuscations.
Get stack traces, request parameters, local variables, affected users and IP addresses, browsers and OSes, deployed code versions, and more.
Error analytics query tool
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.
Works with your stack
Rollbar supports all popular languages and frameworks.
Fits into your workflow
Integrations with tools you're already using.
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.
Quick setup with our lightweight & open source SDK
How to configure rollbar-java to work with your Scala app
For the most basic Java applications use this to install rollbar-java:compile('com.rollbar:rollbar-java:1.+').
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.
Start monitoring errors now
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...