You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/platforms/java/migration/7.x-to-8.0.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Migrating Version 7.x to 8.0
3
-
sidebar_order: 996
3
+
sidebar_order: 995
4
4
description: "Learn about migrating from version 7.x to 8.0.0"
5
5
---
6
6
@@ -9,7 +9,7 @@ description: "Learn about migrating from version 7.x to 8.0.0"
9
9
### Breaking Changes
10
10
11
11
-`Contexts` no longer extends `ConcurrentHashMap`, instead we offer a selected set of methods.
12
-
-`sentry-android-okhttp` has been removed in favor of `sentry-okhttp`, removing android dependency from the module ([#3510](https://github.com/getsentry/sentry-java/pull/3510))
12
+
-`sentry-android-okhttp` has been removed in favor of `sentry-okhttp`, making the module independent from android ([#3510](https://github.com/getsentry/sentry-java/pull/3510))
13
13
- Throw IllegalArgumentException when calling Sentry.init on Android ([#3596](https://github.com/getsentry/sentry-java/pull/3596))
14
14
- Metrics have been removed from the SDK ([#3774](https://github.com/getsentry/sentry-java/pull/3774))
15
15
- Metrics will return but we don't know in what exact form yet
@@ -20,7 +20,7 @@ description: "Learn about migrating from version 7.x to 8.0.0"
20
20
- Replace `synchronized` methods and blocks with `ReentrantLock` (`AutoClosableReentrantLock`) ([#3715](https://github.com/getsentry/sentry-java/pull/3715))
21
21
- If you are subclassing any Sentry classes, please check if the parent class used `synchronized` before. Please make sure to use the same lock object as the parent class in that case.
22
22
-`traceOrigins` option (`io.sentry.traces.tracing-origins` in manifest) has been removed, please use `tracePropagationTargets` (`io.sentry.traces.trace-propagation-targets` in manifest`) instead ([#3780](https://github.com/getsentry/sentry-java/pull/3780))
23
-
-`profilingEnabled` option (`io.sentry.traces.profiling.enable` in manifest) has been removed, please use `profilesSampleRate` (`io.sentry.traces.profiling.sample-rate`instead) instead ([#3780](https://github.com/getsentry/sentry-java/pull/3780))
23
+
-`profilingEnabled` option (`io.sentry.traces.profiling.enable` in manifest) has been removed, please use `profilesSampleRate` (`io.sentry.traces.profiling.sample-rate`in manifest) instead ([#3780](https://github.com/getsentry/sentry-java/pull/3780))
24
24
-`shutdownTimeout` option has been removed, please use `shutdownTimeoutMillis` instead ([#3780](https://github.com/getsentry/sentry-java/pull/3780))
25
25
-`profilingTracesIntervalMillis` option for Android has been removed ([#3780](https://github.com/getsentry/sentry-java/pull/3780))
26
26
-`io.sentry.session-tracking.enable` manifest option has been removed ([#3780](https://github.com/getsentry/sentry-java/pull/3780))
@@ -49,7 +49,7 @@ description: "Learn about migrating from version 7.x to 8.0.0"
49
49
-`HubAdapter.getInstance()` has been replaced by `ScopesAdapter.getInstance()`
50
50
- The `.clone()` method on `IHub`/`IScopes` has been deprecated, please use `.pushScope()` or `.pushIsolationScope()` instead
51
51
- Some internal methods like `.getCurrentHub()` and `.setCurrentHub()` have also been replaced.
52
-
-`Sentry.popScope` has been replaced by calling `.close()` on the token returned by `Sentry.pushScope()` and `Sentry.pushIsolationScope()`. The token can also be used in a `try` block like this:
52
+
-`Sentry.popScope` has been replaced by calling `.close()` on the token returned by `Sentry.pushScope()` and `Sentry.pushIsolationScope()`. The token can also be used in a `try-with-resource` block like this:
@@ -75,7 +75,7 @@ You may also use `LifecycleHelper.close(token)`, e.g. in case you need to pass t
75
75
- Isolation scope can be used e.g. to attach data to all events that come up while handling an incoming request. It can also be used for other isolation purposes. It can be manipulated using `Sentry.configureScope(ScopeType.ISOLATION, (scope) -> { ... })`. The SDK automatically forks isolation scope in certain cases like incoming requests, CRON jobs, Spring `@Async` and more.
76
76
- Current scope is forked often and data added to it is only added to events that are created while this scope is active. Data is also passed on to newly forked child scopes but not to parents.
77
77
-`Sentry.popScope` has been deprecated, please call `.close()` on the token returned by `Sentry.pushScope` instead or use it in a way described in more detail in "Migration Guide".
78
-
- We have chosen a default scope that is used for `Sentry.configureScope()` as well as API like `Sentry.setTag()`
78
+
- We have chosen a default scope that is used for `Sentry.configureScope()` as well as for APIs like `Sentry.setTag()`
79
79
- For Android the type defaults to `CURRENT` scope
80
80
- For Backend and other JVM applicatons it defaults to `ISOLATION` scope
81
81
- Event processors on `Scope` can now be ordered by overriding the `getOrder` method on implementations of `EventProcessor`. NOTE: This order only applies to event processors on `Scope` but not `SentryOptions` at the moment. Feel free to request this if you need it.
@@ -101,7 +101,7 @@ If you've been using the previous version of `sentry-opentelemetry-agent`, simpl
101
101
102
102
#### New to the agent
103
103
104
-
If you've not been using OpenTelemetry before, you can add `sentry-opentelemetry-agent` to your setup by downloading the latest release and using it when starting up your application
104
+
If you've not been using the Sentry OpenTelemetry agent before, you can add `sentry-opentelemetry-agent` to your setup by downloading the latest release and using it when starting up your application
- Please use `sentry.properties` or environment variables to configure the SDK as the agent is now in charge of initializing the SDK and options coming from things like logging integrations or our Spring Boot integration will not take effect.
107
107
- You may find the [docs page](https://docs.sentry.io/platforms/java/tracing/instrumentation/opentelemetry/#using-sentry-opentelemetry-agent-with-auto-initialization) useful.
0 commit comments