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

[8.6] [ML] Explain Log Rate Spikes: Fix field candidate selection. (#147614) #147792

Merged
merged 1 commit into from
Dec 19, 2022

Commits on Dec 19, 2022

  1. [ML] Explain Log Rate Spikes: Fix field candidate selection. (elastic…

    …#147614)
    
    The field candidate selection for Explain Log Rate Spikes was missing a
    check if the supported field type is also aggregatable. For example, a
    `keyword` type field could still be non-aggregatable if it was both not
    indexed and `doc_values` set to `false`. Additionally, if no groups were
    detected, we showed a "Try to continue analysis" button in the UI even
    if the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended
    to include a field like that.
    
    (cherry picked from commit aecad27)
    walterra committed Dec 19, 2022
    Configuration menu
    Copy the full SHA
    8ef6773 View commit details
    Browse the repository at this point in the history