Neel Shah
Neel Shah
We will just pick an obscure port here, exposing this as config doesn't hold much value. Will update issue when fixed/shipped.
Hi @silvermind, we added the whole rack env to `sampling_context` so you can use it in your `traces_sampler`. See an example below. Does that help? https://github.com/getsentry/sentry-ruby/blob/c237974b185e51296542237cbca7f9c1ba1a7eb6/sentry-rails/spec/sentry/rails/tracing_spec.rb#L209-L217
@st0012 can we close this issue now? feature seems to be stable.
@jordan-brough currently, AWS lambda on ruby is not a first-class feature like for python/node where we have separate packages/integrations/layers implemented. AWS extensions are also something we are looking into right...
> I would be pleasure if these queue overflow errors visualized on sentry.io's UI. @hogelog this is on the product road map, but I can't give you an ETA on...
@st0012 so there are some things to consider here. 1. `with_scope` belongs to the [Unified API](https://develop.sentry.dev/sdk/unified-api/) so we can't just change it outright, even though I personally don't like these...
Yes the issue is the same across SDKs, so we can drive the change process by doing it in ruby first. But we cannot change the old `with_scope`, so it...
hmm yea good point! As long as the old behavior is preserved/backward compatible, we should be good.
@jordan-brough PRs are always welcome!
yes, thought the same.