Bump sentry-ruby from 5.23.0 to 5.24.0

[dependabot]

Bumps sentry-ruby from 5.23.0 to 5.24.0.

Changelog

Sourced from sentry-ruby's changelog.

5.24.0

Features

• Add new sidekiq config report_only_dead_jobs (#2581)

• Add max_nesting of 10 to breadcrumbs data serialization (#2583)

• Add sidekiq config propagate_traces to control trace header injection (#2588)

  If you use schedulers you can get one large trace with all your jobs which is undesirable. We recommend using the following to propagate traces only from the Rails server and not elsewhere.

  config.sidekiq.propagate_traces = false unless Rails.const_defined?('Server')

• Only expose active_storage keys on span data if send_default_pii is on (#2589)

• Add new Sentry.logger for Structured Logging feature (#2620).

  To enable structured logging you need to turn on the enable_logs configuration option:

  Sentry.init do |config|
    # ... your setup ...
    config.enable_logs = true
  end

  Once you configured structured logging, you get access to a new Sentry.logger object that can be used as a regular logger with additional structured data support:

  Sentry.logger.info("User logged in", user_id: 123)
  Sentry.logger.error("Failed to process payment",
  transaction_id: "tx_123",
  error_code: "PAYMENT_FAILED"
  )

  You can also use message templates with positional or hash parameters:

  Sentry.logger.info("User %{name} logged in", name: "Jane Doe")
  Sentry.logger.info("User %s logged in", ["Jane Doe"])

  Any other arbitrary attributes will be sent as part of the log event payload:

  # Here `user_id` and `action` will be sent as extra attributes that Sentry Logs UI displays
  Sentry.logger.info("User %{user} logged in", user: "Jane", user_id: 123, action: "create")

... (truncated)

Commits

• cad4b3f release: 5.24.0
• b9fc537 Add new Sentry.logger (#2620)
• 63b5162 Replace logger with sdk_logger (#2621)
• 60859d5 Stop running vernier specs under 3.2 due to a bug in Vernier (#2622)
• 27e3313 Introduce log event buffering (#2619)
• 942dc3a Refactor id generation to use Utils.uuid method (#2618)
• 6da79bd Introduce Sentry.capture_log (#2606)
• b4bd9ee Improve test setup (#2590)
• 8108ddb Remove user_segment from DSC (#2586)
• 9c6f387 Fix breadcrumb serialization error to be an object (#2584)
• 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 will merge this PR once CI passes on it, as requested by @openhpi-bot.

---

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)

[openhpi-bot]

@dependabot merge

[dependabot]

Looks like sentry-ruby is up-to-date now, so this is no longer needed.