-
Notifications
You must be signed in to change notification settings - Fork 8.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
[Fleet][Logs UI] Ensure the <LogStream /> component reacts to query changes #103876
Conversation
Pinging @elastic/fleet (Team:Fleet) |
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
Pinging @elastic/fleet (Feature:Fleet) |
@elasticmachine merge upstream |
@afgomez I have a question regarding version labels. Since it's already been code freeze, do we still need |
@mgiota Yes, bug fixes can go in post-FF. |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @afgomez |
@mgiota What @jen-huang said :) |
LGTM! I tested it and verify that logs view refreshes when searching for a query. It also refreshes when clicking on the dataset dropdown. |
…hanges (elastic#103876) * Ensure the <LogStream /> component reacts to query changes * Remove unused import
…hanges (elastic#103876) * Ensure the <LogStream /> component reacts to query changes * Remove unused import
…hanges (elastic#103876) * Ensure the <LogStream /> component reacts to query changes * Remove unused import
Summary
On #102980 we detected a bug that triggered too many refreshes in the
<LogStream/>
component on cases where the query didn't change. It introduced a problem where changing the query didn't trigger a refresh at the right time.This PR fixes that. Resolves #103563.