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 - empty "Anomalies" table after job load #18343

Closed
elasticmachine opened this issue Jan 30, 2018 · 2 comments · Fixed by #18717
Closed

[ML] Anomaly Explorer - empty "Anomalies" table after job load #18343

elasticmachine opened this issue Jan 30, 2018 · 2 comments · Fixed by #18717
Assignees
Labels
bug Fixes for quality problems that affect the customer experience :ml

Comments

@elasticmachine
Copy link
Contributor

Original comment by @pheyos:

Version:

  • 6.2.0 BC3

Browser:

  • Firefox 58.0, Chromium 63.0

Steps to reproduce:

  • In Job Management click the button "Open in Anomaly Explorer" for a job
    • The Anomalies table should display all anomalies over all time, but sometimes the table is empty:
      no_matching_results_found
  • If the table is filled:
    • Change back to Job Management and click the button "Open in Anomaly Explorer" for another job and look at the listed anomalies
    • Repeat for different jobs or the same jobs
    • In my setting after a few tries the table is empty in at least one of the iterations

Additional information:

  • This does not happen every time the job is loaded. Switching between jobs seems to increase the likelihood of this issue to appear.
  • This also happens (sometimes) when switching jobs via the job drop-down in the Anomaly Explorer
@elasticmachine
Copy link
Contributor Author

Original comment by @walterra:

I'm removing the v6.2.4 label here, the issue is not a blocker and I wasn't able to reproduce the issue yet.

@elasticmachine elasticmachine added :ml bug Fixes for quality problems that affect the customer experience labels Apr 25, 2018
@walterra
Copy link
Contributor

walterra commented May 3, 2018

Fixed in #18717, backported until v6.3.0.

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 :ml
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants