# Kotlin Error Tracking

> Prevent crashes & debug Kotlin errors with Kotlin performance monitoring by Sentry. Learn how to get & use actionable insights to improve your apps here.

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

---

Debug Kotlin apps and prevent crashes across your entire stack with Sentry. Triage and resolve Kotlin exceptions with an end-to-end view of every issue. Enjoy a Kotlin application monitoring workflow that actually improves the debugging process.

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

## Install

Add the Sentry SDK to `build.gradle`:

```groovy
// Make sure mavenCentral is there.
repositories {
    mavenCentral()
}

// Add Sentry's SDK as a dependency.
dependencies {
    implementation 'io.sentry:sentry:<VERSION>'
}
```

Configuration should happen as early as possible in your application's lifecycle:

```kotlin
import io.sentry.Sentry

Sentry.init { options ->
  options.dsn = "https://<key>@sentry.io/<project>"
}
```

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

## Features

### Kotlin Error Monitoring With Complete Stack Traces

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

### Fill In The Blanks About Kotlin Errors

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

### Resolve Kotlin Errors With The Right Inputs

Improve Kotlin error monitoring workflow with a full view of releases so you can mark 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 Kotlin 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/kotlin/](https://sentry.io/for/kotlin/)*