Features
- Improve versatility of exception resolver component for Spring with more flexible API for consumers. (#2577)
- Automatic performance instrumentation for WebFlux (#2597)
- You can enable it by adding
sentry.enable-tracing=true
to yourapplication.properties
- You can enable it by adding
- The Spring Boot integration can now be configured to add the
SentryAppender
to specific loggers instead of theROOT
logger (#2173)- You can specify the loggers using
"sentry.logging.loggers[0]=foo.bar
and"sentry.logging.loggers[1]=baz
in yourapplication.properties
- You can specify the loggers using
- Add capabilities to track Jetpack Compose composition/rendering time (#2507)
- Adapt span op and description for graphql to fit spec (#2607)
Fixes
- Fix timestamps of slow and frozen frames for profiles (#2584)
- Deprecate reportFullDisplayed in favor of reportFullyDisplayed (#2585)
- Add mechanism for logging integrations and update spring mechanism types (#2595)
- NOTE: If you're using these mechanism types (
HandlerExceptionResolver
,SentryWebExceptionHandler
) in your dashboards please update them to use the new types.
- NOTE: If you're using these mechanism types (
- Filter out session cookies sent by Spring and Spring Boot integrations (#2593)
- We filter out some common cookies like JSESSIONID
- We also read the value from
server.servlet.session.cookie.name
and filter it out
- No longer send event / transaction to Sentry if
beforeSend
/beforeSendTransaction
throws (#2591) - Add version to sentryClientName used in auth header (#2596)
- Keep integration names from being obfuscated (#2599)
- Change log level from INFO to WARN for error message indicating a failed Log4j2 Sentry.init (#2606)
- The log message was often not visible as our docs suggest a minimum log level of WARN
- Fix session tracking on Android (#2609)
- Incorrect number of session has been sent. In addition, some of the sessions were not properly ended, messing up Session Health Metrics.