-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
Tempo: Remove traceqlSearch feature toggle #72029
Conversation
(Open the links below in a new tab to go to the correct steps)
|
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.
- Should we say which version we are going to remove the old search functionality in?
- Mark fields
spanName
,serviceName
etc as deprecated? traceqlSearch
mentioned in tempo-search-traceql.md
@@ -110,6 +99,11 @@ class TempoQueryFieldComponent extends React.PureComponent<Props, State> { | |||
} | |||
} | |||
|
|||
// Show the deprecated search option if any of the deprecated search fields are set | |||
if (query.spanName || query.serviceName || query.search || query.maxDuration || query.minDuration) { |
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.
Could we also check if queryType
is nativeSearch
…earch_toggle # Conflicts: # docs/sources/setup-grafana/configure-grafana/feature-toggles/index.md
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 👍
What is this feature?
This PR removes the
traceqlSearch
feature toggle, setting the TraceQL Search editor as the editor of choice for the "Search" query type and deprecating the old "Native Search" editor.The goal is to deprecate the old native search, but not remove it completely from Grafana's code since there may still be users who use it for dashboards or through stored links. Instead, these users (and only these who were already using native search through a dashboard or stored link) will see a deprecation alert asking them to migrate to another query type.
The PR also includes a small refactor/reorg of some components of the Tempo data source.
Who is this feature for?
All users of the Tempo data source.
Which issue(s) does this PR fix?:
Fixes #65825
Special notes for your reviewer:
Please check that: