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 your application.properties
The Spring Boot integration can now be configured to add the SentryAppender to specific loggers instead of the ROOT logger (#2173)
You can specify the loggers using "sentry.logging.loggers[0]=foo.bar and "sentry.logging.loggers[1]=baz in your application.properties
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.
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
This change is backwards compatible. The default is null meaning existing behaviour remains unchanged (setting either tracesSampleRate or tracesSampler enables performance).
If set to true, performance is enabled, even if no tracesSampleRate or tracesSampler have been configured.
If set to false performance is disabled, regardless of tracesSampleRate and tracesSampler options.
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 your application.properties
The Spring Boot integration can now be configured to add the SentryAppender to specific loggers instead of the ROOT logger (#2173)
You can specify the loggers using "sentry.logging.loggers[0]=foo.bar and "sentry.logging.loggers[1]=baz in your application.properties
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.
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
This change is backwards compatible. The default is null meaning existing behaviour remains unchanged (setting either tracesSampleRate or tracesSampler enables performance).
If set to true, performance is enabled, even if no tracesSampleRate or tracesSampler have been configured.
If set to false performance is disabled, regardless of tracesSampleRate and tracesSampler options.
Detect dependencies by listing MANIFEST.MF files at runtime (#2538)
Report integrations in use, report packages in use more consistently (#2179)
Implement ThreadLocalAccessor for propagating Sentry hub with reactor / WebFlux (#2570)
Requires io.micrometer:context-propagation:1.0.2+ as well as Spring Boot 3.0.3+
Enable the feature by setting sentry.reactive.thread-local-accessor-enabled=true
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps io.sentry:sentry from 6.9.1 to 6.16.0.
Release notes
Sourced from io.sentry:sentry's releases.
... (truncated)
Changelog
Sourced from io.sentry:sentry's changelog.
... (truncated)
Commits
00ff407release: 6.16.0ed93ed6Fix session tracking (#2609)d0c4495chore(deps): update Native SDK to v0.6.0 (#2545)910071fAdapt span op and description for graphql (#2607)5bebc56Change log level from INFO to WARN for error message indicating a failed Log4...550d8ecAdd capabilities to track jetpack compose composition/rendering time (#2507)e0df34fFix readme.md workflow shields badge for build status (#2603)af5051fAdd mechanism for logging integrations and update spring mechanism types (#2595)46f5dfdAutomatic performance instrumentation for WebFlux (#2597)674b462Filter out session cookies sent by Spring and Spring Boot integrations (#2593)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)