-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[Event Lifecycle Hooks] Serialized Events Cause DX Issues #13285
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
Comments
Hey, thanks for filing this. I've added it to our backlog. Users can also set attributes on |
I think our API should be powerful enough for all use-cases described here. We expose certain hooks on the Maybe I don't understand correctly but it would probably help to have a bit more concrete suggestions for what these hooks should look like and behave before we can implement this. |
We have the lifecycle hooks, we just need to document them (if we decide to do that). Still in the backlog as such. |
this should no longer be an issue, as metrics are now just span data, which should be possible to set in the existing hooks nicely. |
Problem Statement
Any time a developer wants to mutate their event data before it's sent to Sentry they need to use a beforeX hook.
These hooks provide serialized events to work with which is convenient for evaluating an event's key's values but inconvenient for mutating the event without access to any of the event methods.
Example:
I want to upcycle a spans duration into a custom metric:
This metric is not connected to the sampled span and this API will be going away.
I can't use span.setAttribute here because the span is already serialized.
Solution Brainstorm
Provide lifecycle hooks that can hook into events prior to serialization so that event methods can be used on them.
The text was updated successfully, but these errors were encountered: