Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.6] [ML] Explain Log Rate Spikes: Fix field candidate selection. (e…
…lastic#147614) (elastic#147792) # Backport This will backport the following commits from `main` to `8.6`: - [[ML] Explain Log Rate Spikes: Fix field candidate selection. (elastic#147614)](elastic#147614) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Walter Rafelsberger","email":"walter.rafelsberger@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T17:35:31Z","message":"[ML] Explain Log Rate Spikes: Fix field candidate selection. (elastic#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix",":ml","Feature:ML/AIOps","v8.6.0","v8.7.0"],"number":147614,"url":"elastic#147614 Explain Log Rate Spikes: Fix field candidate selection. (elastic#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"elastic#147614 Explain Log Rate Spikes: Fix field candidate selection. (elastic#147614)\n\nThe field candidate selection for Explain Log Rate Spikes was missing a\r\ncheck if the supported field type is also aggregatable. For example, a\r\n`keyword` type field could still be non-aggregatable if it was both not\r\nindexed and `doc_values` set to `false`. Additionally, if no groups were\r\ndetected, we showed a \"Try to continue analysis\" button in the UI even\r\nif the analysis was able to finish. In this PR the artificial logs dataset for functional tests was extended\r\nto include a field like that.","sha":"aecad27159764d8ea2d0aeddc94fd03954d480e5"}}]}] BACKPORT--> Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>
- Loading branch information