Reproduction for sentry-ruby#2842

[sl0thentr0py]

Summary

• Reproduces issue where Sentry.metrics.count doesn't emit user attributes (user.id, user.email) even when Sentry.set_user has been called
• Minimal Rails 8 app that sets user info in ApplicationController and emits a metric in TestController
• Demonstrates that user info IS present in the Sentry scope but NOT included in metrics

Issue: getsentry/sentry-ruby#2842

Test plan

• Run bundle install in sentry-ruby/2842/
• Set SENTRY_DSN environment variable
• Run bundle exec rails server
• Visit http://localhost:3000/test
• Verify user info is logged to console
• Check Sentry dashboard to confirm metric lacks user attributes

🤖 Generated with Claude Code

[cursor]

Hardcoded Rails secret key base

Medium Severity

config.secret_key_base is hardcoded in config/application.rb, which risks leaking a valid secret into version control. If this app is ever run beyond a purely local repro (or copied as a template), sessions/cookies and other signed data can become forgeable.

 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Callback may crash and silently drop metrics

Medium Severity

The before_send_metric callback calls event.to_h on the metric object, but the MetricEvent type received by this callback is not a documented subclass of Sentry::Event (which defines to_h). Its documented interface only exposes name, attributes, span_id, trace_id, and timestamp. If to_h is not defined on this object, the callback raises NoMethodError, which sentry-ruby catches internally and silently drops the metric — making the reproduction appear as if no metric was sent at all, rather than demonstrating the actual user-attributes-missing issue.