# Scala Error Monitoring

> See important file details and monitor errors at scale with Scala error & performance monitoring. Request a demo or try Sentry for free today.

**URL:** https://sentry.io/for/scala/

---

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.

**Documentation:** [https://docs.sentry.io/platforms/java/](https://docs.sentry.io/platforms/java/)

## Install

Grab the [Sentry Java SDK](https://github.com/getsentry/sentry-java/):

```scala
libraryDependencies += "io.sentry" % "sentry" % "8.62.0"
```

Configure your SDK:

```scala
import io.sentry.{Sentry, SentryOptions}

object Application {
  def main(args: Array[String]): Unit = {
    Sentry.init((options: SentryOptions) => {
      options.setDsn("https://<key>@sentry.io/<project>")
      // Set tracesSampleRate to 1.0 to capture 100%
      // of transactions for tracing.
      // We recommend adjusting this value in production.
      options.setTracesSampleRate(1.0)
    })

    try
      runSomething
    catch {
      case e: Exception =>
        Sentry.captureException(e)
    }
  }
}
```

See the [Scala docs](https://docs.sentry.io/platforms/java/) for full setup options.

## Features

### 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 Scala errors 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.

## FAQ

**What is the difference between Sentry and traditional logging?**

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](/vs/logging/) and on our [blog](https://blog.sentry.io/lets-get-ready-to-monitor/).

**How do I connect issues to git commits?**

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](https://docs.sentry.io/platforms/java/guides/spring-boot/#using-git-commit-id-as-the-release).

**How much does Sentry cost?**

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](/pricing/).

---

*Source: [sentry.io/for/scala/](https://sentry.io/for/scala/)*