-
-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to mute transaction spans in a block #1943
Labels
Comments
thx @booleanbetrayal I'll discuss this internally and get back to you. Ideally when we implement high level features such as these, we should do them across all languages. |
Thank you @sl0thentr0py . Feel free to reach out if you need any use-case specifics. |
we're going to eventually move to opentelemetry like api's anyway so for this is out of the picture for now, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the idea
Skylight has
Skylight.mute
support to selectively disable span construction in a block, during operations known to inflate payload sizes unnecessarily or for any reason a developer might not be interested in that information. I haven't found any sort of corresponding support in Sentry, which is causing us troubles with payload contraints. Likewise, because there is no ability to interact with the transaction likebefore_send
, we are at a loss for how to deal with this situation.Why do you think it's beneficial to most of the users
Users will likely have requirements where selective disabling of span recording could allow transactions to succeed / be more contextually relevant, where they were not before.
Possible implementation
Sentry.mute
method that behaves identically toSkylight.mute
.The text was updated successfully, but these errors were encountered: