Bump sentry from 0.38.1 to 0.41.0

[dependabot]

Bumps sentry from 0.38.1 to 0.41.0.

Release notes

Sourced from sentry's releases.

0.41.0

Breaking changes

• feat(tracing): support combined EventFilters and EventMappings (#847) by @​lcian
  • EventFilter has been changed to a bitflags struct.
  • It's now possible to map a tracing event to multiple items in Sentry by combining multiple event filters in the event_filter, e.g. tracing::Level::ERROR => EventFilter::Event | EventFilter::Log.
  • It's also possible to use EventMapping::Combined to map a tracing event to multiple items in Sentry.
  • ctx in the signatures of event_from_event, breadcrumb_from_event and log_from_event has been changed to take impl Into<Option<&'context Context<'context, S>>> to avoid cloning the Context when mapping to multiple items.

Features

• feat(core): emit debug log when calling capture_log but logs are disabled (#849) by @​lcian

Fixes

• fix(logs): stringify u64 attributes greater than i64::MAX (#846) by @​lcian

Dependencies

• chore(deps): bump anyhow and disable its backtrace feature (#632) by @​LunaBorowska

0.40.0

Logs

We've released two new integrations for Sentry structured logs, the tracing and log integration. Read below on how to start sending logs to Sentry.

Breaking changes

• refactor(logs): apply user attributes to log regardless of send_default_pii (#843) by @​lcian
  • User attributes should be applied to logs regardless of send_default_pii. Therefore, that parameter was removed from sentry_core::Scope::apply_to_log.

Features

• feat(tracing): add support for logs (#840) by @​lcian
  • To capture tracing events as Sentry structured logs, enable the logs feature of the sentry crate.
  • Then, initialize the SDK with enable_logs: true in your client options.
  • Finally, set up a custom event filter to map events to logs based on criteria such as severity. For example:

      let sentry_layer = sentry_tracing::layer().event_filter(|md| match *md.level() {
          tracing::Level::ERROR => EventFilter::Event,
          tracing::Level::TRACE => EventFilter::Ignore,
          _ => EventFilter::Log,
      });

• feat(log): add support for logs (#841) by @​lcian
  • To capture log records as Sentry structured logs, enable the logs feature of the sentry crate.
  • Then, initialize the SDK with enable_logs: true in your client options.
  • Finally, set up a custom event filter to map records to Sentry logs based on criteria such as severity. For example:

      let logger = sentry::integrations::log::SentryLogger::new().filter(|md| match md.level() {

... (truncated)

Changelog

Sourced from sentry's changelog.

0.41.0

Breaking changes

• feat(tracing): support combined EventFilters and EventMappings (#847) by @​lcian
  • EventFilter has been changed to a bitflags struct.
  • It's now possible to map a tracing event to multiple items in Sentry by combining multiple event filters in the event_filter, e.g. tracing::Level::ERROR => EventFilter::Event | EventFilter::Log.
  • It's also possible to use EventMapping::Combined to map a tracing event to multiple items in Sentry.
  • ctx in the signatures of event_from_event, breadcrumb_from_event and log_from_event has been changed to take impl Into<Option<&'context Context<'context, S>>> to avoid cloning the Context when mapping to multiple items.

Features

• feat(core): emit debug log when calling capture_log but logs are disabled (#849) by @​lcian

Fixes

• fix(logs): stringify u64 attributes greater than i64::MAX (#846) by @​lcian

Dependencies

• chore(deps): bump anyhow and disable its backtrace feature (#632) by @​LunaBorowska

0.40.0

Breaking changes

• refactor(logs): apply user attributes to log regardless of send_default_pii (#843) by @​lcian
  • User attributes should be applied to logs regardless of send_default_pii. Therefore, that parameter was removed from sentry_core::Scope::apply_to_log.

Features

• feat(tracing): add support for logs (#840) by @​lcian
  • To capture tracing events as Sentry structured logs, enable the logs feature of the sentry crate.
  • Then, initialize the SDK with enable_logs: true in your client options.
  • Finally, set up a custom event filter to map events to logs based on criteria such as severity. For example:

      let sentry_layer = sentry_tracing::layer().event_filter(|md| match *md.level() {
          tracing::Level::ERROR => EventFilter::Event,
          tracing::Level::TRACE => EventFilter::Ignore,
          _ => EventFilter::Log,
      });

• feat(log): add support for logs (#841) by @​lcian
  • To capture log records as Sentry structured logs, enable the logs feature of the sentry crate.
  • Then, initialize the SDK with enable_logs: true in your client options.
  • Finally, set up a custom event filter to map records to Sentry logs based on criteria such as severity. For example:

      let logger = sentry::integrations::log::SentryLogger::new().filter(|md| match md.level() {
          log::Level::Error => LogFilter::Event,
          log::Level::Trace => LogFilter::Ignore,

... (truncated)

Commits

• 673e8dd release: 0.41.0
• 1d89cb8 fix(tracing): fix doctest (#850)
• 7dbafef feat(core): emit debug log when calling capture_log but logs are disabled (#849)
• 3a18382 chore(deps): bump anyhow and disable its backtrace feature (#632)
• 20a5d48 feat(tracing): support combined EventFilters and EventMappings (#847)
• 333b14e fix(logs): stringify u64 attributes greater than i64::MAX (#846)
• 0957716 Merge branch 'release/0.40.0'
• 25be1a5 release: 0.40.0
• 4553e2e refactor(logs): cache default attributes and add OS attributes (#842)
• 34db51d feat(log): add support for logs (#841)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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]

Superseded by #166.