-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
fix(visibility): Return meta
in span samples responses
#88733
fix(visibility): Return meta
in span samples responses
#88733
Conversation
meta
in span samples responses
6c7f8c5
to
348b1bb
Compare
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.
small comment, lgtm otherwise
transform_alias_to_input_format = ( | ||
request.GET.get("transformAliasToInputFormat") == "1" or use_rpc | ||
) |
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.
Are we not able to just force this on always instead of needing the param
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.
You tell me, honestly! I followed what the other endpoints do. For EAP, it's always on, for indexed spans, there's a parameter. I think that'll make it easier to coordinate switching over, but it's probably a small difference
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.
I'd prefer if we can move away from needing this parameter at all, if the frontend doesn't need it un-transformed lets just not use this? ie. does the frontend need the old format still?
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.
🤔 well, the meta isn't in use at all right now, so I guess I could just force it, yeah! I'll probably replacing all the frontend usages of this at the same time anyway. I'll get rid of it 👍🏻
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Right now, `/spans-samples` doesn't return any meta, only `"data"`. This PR runs the response through `handle_results_with_meta` and returns it, which includes the correct standard meta. Closes [DAIN-49: Return `meta` from span samples endpoint](https://linear.app/getsentry/issue/DAIN-49/return-meta-from-span-samples-endpoint) --------- Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
Right now,
/spans-samples
doesn't return any meta, only"data"
. This PR runs the response throughhandle_results_with_meta
and returns it, which includes the correct standard meta.Closes DAIN-49: Return
meta
from span samples endpoint