fix(deps): update rust crate sentry to 0.48.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
sentry (source)	dependencies	minor	0.47.0 → 0.48.0

---

Release Notes

getsentry/sentry-rust (sentry)

v0.48.0

Compare Source

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#​1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#​1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#​1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#​1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#​1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#​1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#​1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#​1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;

let _guard = sentry::init((
    "(your DSN here)",
    ClientOptions {
        enable_metrics: true,
        // ... other options ...
        ..Default::default()
    },
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;

// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
    .unit(Unit::Millisecond) // units can also be set on gauges
    .attribute("http.status", 200) // attributes can be set on all metric types
    .capture();

Fixes

• Fixed several feature additivity SemVer violations, where enabling a feature flag could have introduced breaking changes. All known violations are fixed now, so simply enabling an additional feature flag in any Sentry SDK crate should no longer cause any public API breakages. Fixing these issues required us to break the public API in some places; those breakages are detailed above.

---

Configuration

📅 Schedule: (in timezone America/Indiana/Indianapolis)

• Branch creation
  • Between 08:00 AM and 11:59 PM, only on Friday and Saturday (* 8-23 * * 5,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Test Results

46 tests   46 ✅  2s ⏱️
 1 suites   0 💤
 1 files     0 ❌

Results for commit de5efec.

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.86%. Comparing base (4510f8f) to head (de5efec).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #140   +/-   ##
=======================================
  Coverage   87.86%   87.86%           
=======================================
  Files           8        8           
  Lines        2430     2430           
  Branches     2430     2430           
=======================================
  Hits         2135     2135           
  Misses        261      261           
  Partials       34       34           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ericswpark]

@kdkasad do we want to enable metrics for the webring?

[kdkasad]

@kdkasad do we want to enable metrics for the webring?

We aren't collecting any metrics right now, so we don't have any to report. I think that's what @Xendergo was working on in #75, so maybe he can export the metrics he collects to Sentry.

[Xendergo]

I haven't been working on that PR primarily because I don't know how to export the data into a format that can be accepted by opentelemetry/sentry/prometheus/whatever. If you want, I could make my statistics tracker export data to a facade and someone else could implement the other end of it?

[kdkasad]

Actually @ericswpark it looks like Sentry's Rust SDK doesn't support application metrics yet: https://docs.sentry.io/product/explore/metrics/getting-started/

[ericswpark]

Actually @ericswpark it looks like Sentry's Rust SDK doesn't support application metrics yet: https://docs.sentry.io/product/explore/metrics/getting-started/

@kdkasad

I think that link hasn't been updated. See the changelog for the new release and it does mention Metrics support.

But if we are adding metrics later then I think this PR can be merged since we won't be enabling it now.