-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
feat(eap): Add a GetTraces endpoint #6671
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly nitpicks but looks good to me overall.
|
||
_ATTRIBUTES: dict[ | ||
TraceAttribute.Key.ValueType, | ||
tuple[str, AttributeKey.Type.ValueType], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: a named tuple/data class/typed dict would be a little cleaner here so you don't have to access it by index
❌ 2 Tests Failed:
View the top 2 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
This is a possible implementation of the new FindTraces endpoint.
getsentry/sentry-protos#71
Closes https://github.com/getsentry/eap-planning/issues/122.