You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using TraceQL, I noticed that when I write {resource.}, I receive suggestions for all possible attributes from both the resource and span scope. This can be overwhelming when I only want to see the attributes specific to either the resource or the span.
Describe the solution you'd like
I would like to propose that typing . returns all possible attributes, typing resource. only displays the resource attributes, and typing span. only displays the span attributes. This would enhance the usability and make it easier to navigate and select the desired attributes based on the scope we are working with.
The text was updated successfully, but these errors were encountered:
I'm normally terrible about closing issues b/c I want there to be discussion even if it's not something we agree with or have time to work on, but this one seems pretty covered.
Is your feature request related to a problem? Please describe.
When using TraceQL, I noticed that when I write
{resource.}
, I receive suggestions for all possible attributes from both the resource and span scope. This can be overwhelming when I only want to see the attributes specific to either the resource or the span.Describe the solution you'd like
I would like to propose that typing
.
returns all possible attributes, typingresource.
only displays the resource attributes, and typingspan.
only displays the span attributes. This would enhance the usability and make it easier to navigate and select the desired attributes based on the scope we are working with.The text was updated successfully, but these errors were encountered: