Skip to content

[skill-drift] sentry-ruby-sdk may need updates #39

Closed

Description

@github-actions

SDK Changes Detected

The following PRs were merged to getsentry/sentry-ruby in the last 7 days that may affect the sentry-ruby-sdk skill:

Potential Skill Gaps

  1. New Config Options: PR #2872 adds two new configuration options not present in the skill's tracing reference table:

    • config.strict_trace_continuation (Boolean, default false) — controls whether the SDK starts a new trace when incoming sentry-org_id baggage doesn't match the SDK's org ID. Prevents inadvertent trace continuation from third-party services.
    • config.org_id (String) — explicitly set the organization ID (useful for self-hosted/Relay setups where DSN-based parsing may not work). Takes precedence over DSN-extracted org ID.

    The skill's tracing config table in references/tracing.md currently lists: traces_sample_rate, traces_sampler, trace_propagation_targets, propagate_traces. Neither new option appears.

  2. Rails Queue Time Fix: PR #2877 fixes request queue time tracking in Rails middleware. The skill (references/tracing.md) mentions queue time capture being automatic in v6.4.0+ via Puma — this fix may change behavior or requirements worth documenting.

Skill Files to Review

  • skills/sentry-ruby-sdk/SKILL.md — init options table in Phase 3
  • skills/sentry-ruby-sdk/references/tracing.md — distributed tracing config table and propagation section

Priority

MEDIUM — new configuration options that affect distributed tracing behavior; relevant for microservice architectures using Ruby services.

Generated by SDK Skill Drift Detector · ◷

  • expires on Mar 21, 2026, 9:08 PM UTC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions