-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Single Metric Viewer sometimes shows anomalies from all partition field values #94820
Comments
Pinging @elastic/ml-ui (:ml) |
@benwtrent what is the sequence of actions you use when seeing this? I can't reproduce on my setup with that same job. Are you opening the Single Metric Viewer straight from the Jobs list, or from a specific anomaly in the Anomaly Explorer for example? |
SMV straight from the jobs list. Let me pull down latest kibana (I am about ~2days behind) and see if it reproduces |
Pulled latest master, attempted on the same job again and it immediately happened again. It initially filtered to the appropriate IP address, and then it changed to the incorrect display. I was able to reproduce it again with the console open. I think this has to do with two async callbacks being handled out of order. There is probably a search to gather cardinality and overall anomalies that kicks off on page load, then I select the IP. The data for the IP is loaded and THEN the cardinality + all anomalies load after. Can provide an HAR of the reproduction |
We have not been able to reproduce this. Closing issue, but if you see this again please re-open with the steps to reproduce. |
Kibana version:
master
Elasticsearch version:
master
Browser version:
Chrome 89.0.4389.82 MacOS
Describe the bug:
Instead of only showing the anomalies related to the selection, it shows ALL anomalies in the SMV overview.
Steps to reproduce:
over
fieldExpected behavior:
I expect only the anomalies related to the specifically selected
over
field.Screenshots (if relevant):
Image:
Any additional context:
It only occurs sometimes.
Also, If I hit the
Refresh
button, it displays correctlyThe text was updated successfully, but these errors were encountered: