Scala Error Monitoring

Debug Scala apps and prevent crashes across your entire stack with Sentry. Resolve issues with a Scala monitoring workflow that actually improves the debugging process.

Getting Started is Simple

Grab the Sentry Java SDK:

Click to Copy
libraryDependencies += "io.sentry" % "sentry" % "7.19.0"

Configure your SDK:

Click to Copy
import io.sentry.Sentry object Application { def main(args: Array[String]): Unit = { Sentry.init("https://<key>@sentry.io/<project>") try runSomething catch { case e: Exception => Sentry.captureException(e) } } }

Check our documentation for the latest instructions.

See all platforms

More than 100K Organizations Trust Sentry with Their Application Monitoring

$<!-- -->Github<!-- --> logo
$<!-- -->Atlassian<!-- --> logo
$<!-- -->Disney<!-- --> logo
$<!-- -->Cloudflare<!-- --> logo
$<!-- -->Microsoft<!-- --> logo
$<!-- -->Lush<!-- --> logo

Scala Error Monitoring with Complete Stack Traces

See details like filename and line number so you never have to guess. Filter and group Scala exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production.

Fill In The Blanks About Scala Errors

Expose the important events that led to each Scala exception: network requests, debug logs, database queries, past errors.

Resolve Scala Errors With Max Efficiency, Not Max Effort

Improve workflow with a full view of releases so you can mark Scalaerrors as resolved and prioritize live issues. Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release. Add commit data to automatically suggest an owner of each Scala error and instantly send deploy emails.

”Sentry's high-quality tooling helps Disney+ maintain high-quality service to its tens of millions of global subscribers.”

Andrew Hay
Director of Engineering at Disney Streaming Services

See The Full Picture Of Any Scala Exception

Triage quickly based on specific parameters like HTTP request, workflow stage, and hostname.

Set custom tags to recreate the error environment relevant to your app, business concerns, and users.

Find answers to the key questions: In which app release did the Scala bug occur? What version of the JVM was the application running?

Is your data secure? You better believe it.

Just look at all the high-quality security features all accounts get, regardless of plan.

  • Two-Factor Auth
  • Single Sign-On support
  • Organization audit log
  • SOC 2 Type II and ISO 27001 certified
  • HIPAA attestation
Learn more about security
  • PII data scrubbing
  • SSL encryption
  • Data Processing Addendum (includes latest EU SCCs)
  • Privacy Shield certified
Learn more about privacy

FAQs

Traditional logging provides you with a trail of events. Some of those events are errors, but many times they’re simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail here and on our blog.

When Spring Boot is configured to generate Git information every event triggered by Sentry will have a release field set to the current Git commit ID that will enable Monitor Release Health Sentry feature. More details here.

You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.

Supporting Resources

Sentry for Spring Boot and Logback

Improve your 99% latency with 1% effort.
Try Sentry’s Java monitoring today.

© 2024 • Sentry is a registered Trademark of Functional Software, Inc.