---
title: "Troubleshooting"
description: "Troubleshoot Java OpenTelemetry problems."
url: https://docs.sentry.io/platforms/java/guides/logback/opentelemetry/troubleshooting/
---

# Troubleshooting | Sentry for Logback

## [OpenTelemetry Dependency Version Mismatches](https://docs.sentry.io/platforms/java/guides/logback/opentelemetry/troubleshooting.md#opentelemetry-dependency-version-mismatches)

OpenTelemetry integrations use several artifacts that must stay on compatible versions. If another BOM or dependency-management plugin changes some OpenTelemetry versions but not others, your application can start with a mixed OpenTelemetry classpath.

This is common in Spring Boot applications because Spring Boot dependency management can manage OpenTelemetry core artifacts while your application, Sentry, or another library brings in OpenTelemetry instrumentation artifacts. Version mismatches often appear as startup or request-time classloading errors, such as `ClassNotFoundException`, `NoClassDefFoundError`, `NoSuchMethodError`, or `NoSuchFieldError`.

### [Fix Dependency Alignment](https://docs.sentry.io/platforms/java/guides/logback/opentelemetry/troubleshooting.md#fix-dependency-alignment)

If you use Sentry's OpenTelemetry agentless or OTLP integrations and another BOM manages OpenTelemetry versions, manually import Sentry's OpenTelemetry BOM. The BOM aligns Sentry's OpenTelemetry modules with the OpenTelemetry core, instrumentation, and incubator artifacts Sentry tests against.

Use the dependency alignment instructions for your integration:

* [Agentless dependency alignment](https://docs.sentry.io/platforms/java/guides/logback/opentelemetry/setup/agentless.md#opentelemetry-dependency-alignment)
* [OTLP dependency alignment](https://docs.sentry.io/platforms/java/guides/logback/opentelemetry/setup/otlp.md#opentelemetry-dependency-alignment)