[ML] AIOps: Adds cardinality check to Log Rate Analysis #181129
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
walterra
force-pushed
the
ml-aiops-cardinality-check
branch
from
f5fa13d to
8d1730a
Compare
walterra
added
release_note:enhancement
:ml
Feature:ML/AIOps
|
Pinging @elastic/ml-ui (:ml) |
peteharverson
approved these changes
May 17, 2024
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: cc @walterra |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Part of #181111.
This filters field/value items from the results if the field has a cardinality of just 1 since it wouldn't be useful as a result.
Before (you can easily spot fields with cardinality of 1 because the mini histogram in the table is just one color which means the value is present in all logs):
After:
Checklist