Skip to content
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

[ML] Explain Log Rate Spikes: Fix field candidates detection. #146992

Closed
2 tasks done
walterra opened this issue Dec 5, 2022 · 1 comment · Fixed by #147614
Closed
2 tasks done

[ML] Explain Log Rate Spikes: Fix field candidates detection. #146992

walterra opened this issue Dec 5, 2022 · 1 comment · Fixed by #147614
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis :ml v8.7.0

Comments

@walterra
Copy link
Contributor

walterra commented Dec 5, 2022

In some cases the field candidates include non-aggregatable fields.

image

  • The fields should not be included in the original list of field candidates.
  • In a case like this, if the user clicks Try to continue analysis, the progress bar will proceed above 100%. On completion it ends up as 100%. The button should only we available if the analysis fails to continue as a whole at some point. In this case just individual queries fail but the analysis is able to finish
@walterra walterra added bug Fixes for quality problems that affect the customer experience :ml Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis v8.7.0 labels Dec 5, 2022
@walterra walterra self-assigned this Dec 5, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis :ml v8.7.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants