sentry-ruby-sdk

Malicious tool definition detected

Tool: sentry-ruby-sdk/references/migration.md [2/2] Description: Sentry | |------|-------------|--------| | AppSignal | `APPSIGNAL_PUSH_API_KEY` | `SENTRY_DSN` | | Honeybadger | `HONEYBADGER_API_KEY` | `SENTRY_DSN` | | Bugsnag | `BUGSNAG_API_KEY` | `SENTRY_DSN` | | Rollbar | `ROLLBAR_ACCESS_TOKEN` | `SENTRY_DSN` | | Airbrake | `AIRBRAKE_PROJECT_ID` + `AIRBRAKE_PROJECT_KEY` | `SENTRY_DSN` | ### Rollout strategy Run both tools in parallel for one release cycle, then remove the old gem once Sentry

Risky tool definition detected

Enable `strict_trace_continuation` to reject traces from services outside your Sentry organization: ```ruby Sentry.init do |config| config.dsn = ENV["SENTRY_DSN"] # Reject traces where the incoming sentry-org_id baggage doesn't match this SDK's org. # The org ID is normally extracted from the DSN automatically.

### Setup ```ruby # Gemfile — add alongside existing opentelemetry gems: gem "sentry-opentelemetry" gem "opentelemetry-exporter-otlp" # required for OTLP export ``` ```ruby # config/initializers/sentry.rb Sentry.init do |config| config.dsn = ENV["SENTRY_DSN"] config.send_default_pii = true config.otlp.enabled = true config.enable_logs = true # keep Sentry native logging unless OTel logs SDK is also present # Do NOT set traces_sample_rate — tracing is handled by OTel # Errors, Logs, Crons, and Me

Prompt Injection

Context Poisoning

Guardrail Bypass

Malicious tool definition detected

## Upserting Monitor Configuration Pass `monitor_config` in the initial check-in to create or update the monitor definition programmatically (no manual setup in Sentry UI required): ```ruby monitor_config = Sentry::Cron::MonitorConfig.from_crontab( "5 * * * *", # runs at :05 every hour checkin_margin: 5, max_runtime: 15, timezone: "Europe/Berlin" ) check_in_id = Sentry.capture_check_in( "hourly-sync", :in_progress, monitor_config: monitor_config ) # ...

Malicious tool definition detected

## Best Practices - Start with `profiles_sample_rate = 1.0` in development to verify profiles appear in Sentry - Lower to `0.1`–`0.5` in production — profiling adds overhead per sampled transaction - Prefer Vernier on Ruby 3.2.1+ for lower overhead and GVL visibility - Profiling without tracing is not supported — ensure `traces_sample_rate > 0` ## Troubleshooting | Issue | Solution | |-------|----------| | No profiles in Sentry | Verify `traces_sample_rate > 0` — profiling requires tracing to be

Tool passed security scan

Tool passed security scan