[ML] AIOps Log Rate Analysis: Merge fetch queue for keyword and text field candidates. #183649
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.
So far we identified significant
text
field candidates beforekeyword
field candidates. There were 2 problems with this: 1) The loading behaviour fortext
fields was not considered in the progress bar. 2) Analysing atext
field can be quite slow we weren't taking advantage of the same queue we used to fetchkeyword
fields. If it was taking quite a while to analysis thetext
fields, it would appear the progress bar was "stuck". And we had to wait to finish those slow queries before we started fetching p-values forkeyword
fields.This PR improves the behaviour by adding
text
field fetching to the same queue that fetcheskeyword
fields. This means while a maybe slowertext
field is analysed, we can continue to fetchkeyword
based fields in parallel given the max concurrency.It's a bit tricky to test because with the local datasets the analysis might be so fast you won't notice a difference. So for testing you could do the following: In the file
significant_items_handler.ts
at the top add:And further down around line
110
add the following delay:This will randomly delay the next call for the text/keyword field so you should see the progress bar moving. The difference to before would be that the progress bar would not move while it analyses the text fields.
Checklist