-
Notifications
You must be signed in to change notification settings - Fork 12
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
Xray Trace does not show SQL on trace in grafana #142
Comments
@mesparks can you maybe show a screenshot of what you are seeing in the aws console that you do not see in grafana? I'm not sure what you mean by "sql on trace" |
Thanks for getting back to us @mesparks. Will discuss this with the team and report back to you. |
Hi @mesparks it looks to me like this SQL feature is a "subsegment". My understanding is that any segment and subsegment data we recieve from aws we forward on to the user. It seems likely to me that this information is not being returned in the public api so there is no way for grafana to render it. But if you are able to make a specific public api call for this data, do let us know and we can see if we are somehow accidentally filtering this information somehow, or if there's a way for us to ping directly for it. |
Adds action trigger to remove from AWS Plugins project board when issues are unlabeled Part of [#142]( grafana/oss-plugin-partnerships#142)
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: