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] Anomaly explorer queries closed above #18575

Closed
tveasey opened this issue Apr 25, 2018 · 1 comment · Fixed by #18995
Closed

[ML] Anomaly explorer queries closed above #18575

tveasey opened this issue Apr 25, 2018 · 1 comment · Fixed by #18995
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Anomaly Detection ML anomaly detection :ml v6.4.0

Comments

@tveasey
Copy link
Contributor

tveasey commented Apr 25, 2018

The searches backing the anomaly explorer appear to be erroneously closed above. This means when a time range is selected it is possible that influences are retrieved which are not anomalous at all in the selected time range. For example, in the following, note that third tile down is blank indicating that this has no results in that time range:

screen shot 2018-04-25 at 18 12 33

The anomalous bucket for this IP starts at midnight on the day after and results are assigned the start time of the bucket.

Found on master running the job described in elastic/ml-cpp#57.

cc @peteharverson.

@tveasey tveasey added bug Fixes for quality problems that affect the customer experience v7.0.0 Feature:ml-results legacy - do not use labels Apr 25, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui

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:Anomaly Detection ML anomaly detection :ml v6.4.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants