Skip to content

Connect Kotlin with its Sentry SDK

Your Kotlin app keeps its Sentry SDK. Xovris gives it your project’s DSN, and every error it sends becomes a Xovris issue with its stack and release.

io.sentry:sentry
Get your project’s DSN

Already installed? Your code stays as it is – the DSN is the one change.

Start it

Put this where your app starts:

// reads SENTRY_DSN from the environmentimport io.sentry.Sentry
Sentry.init { it.isEnableExternalConfiguration = true }

It reads SENTRY_DSN, so your project’s address never sits in your code.

Your project’s DSN

Xovris finds the SDK in your build.gradle.kts, creates your project’s address and writes it as SENTRY_DSN in your env file, after showing you the change. It then sends a test event and waits until it is stored. In the project, run:

Terminal window
npx xovris@latest init

See the first error

Send one from anywhere your app runs:

Sentry.captureException(RuntimeException("first error for Xovris"))

Capture one error with the SDK’s own call and it appears as a Xovris issue:

  • Errors and their stack traces, grouped into issues
  • Messages you capture
  • The release each event names

Its frameworks

The same DSN covers every framework this SDK’s own integrations reach:

Compose Multiplatform and Kotlin Multiplatform.

What Xovris has run

Read through the Sentry protocol every Sentry SDK speaks. Xovris has not yet driven this SDK itself, so its own bytes are not in the tests yet.

Every option the SDK has is in its own documentation: docs.sentry.io/platforms/kotlin/

Traces and metrics too

Xovris also sets Kotlin up with OpenTelemetry for traces, metrics and logs beside the SDK’s errors. Connect Java (Spring Boot) with OpenTelemetry

Ask Xovris

Open the full page

Your data is never used to train our AI. How your data is kept

A problem is called fixed only once it works again. How each fix is checked

XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.