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] AIOps Log Rate Analysis: Fixes text field selection #186176

Merged
merged 2 commits into from
Jun 18, 2024

Conversation

walterra
Copy link
Contributor

@walterra walterra commented Jun 13, 2024

Summary

Part of #181111.

If we analyse all detected text fields, we might run into performance issues with the categorize_text aggregation. Until this is resolved, we will rely on a predefined safe list of supported text fields, for now set to message and error.message.

Checklist

Delete any items that are not applicable to this PR.

@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@walterra walterra added the Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis label Jun 13, 2024
Copy link
Contributor

@peteharverson peteharverson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
Only data set I found to to test this was gallery where the useragent field no longer appears in the results.

Unrelated to the changes here, but the styling for text fields could maybe do with a tweak - padding in between the icon and the text, and the horizontal alignment is off compared to keyword fields.

Screenshot 2024-06-17 at 11 37 18

Copy link
Contributor

@alvarezmelissa87 alvarezmelissa87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ⚡

@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #75 / Serverless observability API Burn rate rule Rule creation should set correct information in the alert document

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @walterra

@walterra walterra merged commit d3b8123 into elastic:main Jun 18, 2024
24 checks passed
@walterra walterra deleted the ml-aiops-fix-text-field-selection branch June 18, 2024 07:49
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jun 18, 2024
If we analyse all detected text fields, we might run into performance
issues with the `categorize_text` aggregation. Until this is resolved,
we will rely on a predefined white list of supported text fields, for
now set to `message` and `error.message`.

(cherry picked from commit d3b8123)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.14

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Jun 18, 2024
… (#186351)

# Backport

This will backport the following commits from `main` to `8.14`:
- [[ML] AIOps Log Rate Analysis: Fix text field selection
(#186176)](#186176)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Walter
Rafelsberger","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-06-18T07:49:50Z","message":"[ML]
AIOps Log Rate Analysis: Fix text field selection (#186176)\n\nIf we
analyse all detected text fields, we might run into
performance\r\nissues with the `categorize_text` aggregation. Until this
is resolved,\r\nwe will rely on a predefined white list of supported
text fields, for\r\nnow set to `message` and
`error.message`.","sha":"d3b81237ee3138e7a62ae34c19f65109b751f0b3","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:ML/AIOps","v8.15.0","v8.14.2"],"title":"[ML]
AIOps Log Rate Analysis: Fix text field
selection","number":186176,"url":"https://github.com/elastic/kibana/pull/186176","mergeCommit":{"message":"[ML]
AIOps Log Rate Analysis: Fix text field selection (#186176)\n\nIf we
analyse all detected text fields, we might run into
performance\r\nissues with the `categorize_text` aggregation. Until this
is resolved,\r\nwe will rely on a predefined white list of supported
text fields, for\r\nnow set to `message` and
`error.message`.","sha":"d3b81237ee3138e7a62ae34c19f65109b751f0b3"}},"sourceBranch":"main","suggestedTargetBranches":["8.14"],"targetPullRequestStates":[{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/186176","number":186176,"mergeCommit":{"message":"[ML]
AIOps Log Rate Analysis: Fix text field selection (#186176)\n\nIf we
analyse all detected text fields, we might run into
performance\r\nissues with the `categorize_text` aggregation. Until this
is resolved,\r\nwe will rely on a predefined white list of supported
text fields, for\r\nnow set to `message` and
`error.message`.","sha":"d3b81237ee3138e7a62ae34c19f65109b751f0b3"}},{"branch":"8.14","label":"v8.14.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Walter Rafelsberger <[email protected]>
@walterra walterra added the bug Fixes for quality problems that affect the customer experience label Jul 8, 2024
@szabosteve szabosteve changed the title [ML] AIOps Log Rate Analysis: Fix text field selection [ML] AIOps Log Rate Analysis: Fixes text field selection Jul 31, 2024
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 release_note:fix v8.14.2 v8.15.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants