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.

Sign up for GitHub

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

Jump to bottom

[ML] Anomaly Explorer: Error when clicking on multiple 'Overall' swimlane cells #24735

Closed
alvarezmelissa87 opened this issue Oct 29, 2018 · 2 comments · Fixed by #24742
Closed

[ML] Anomaly Explorer: Error when clicking on multiple 'Overall' swimlane cells #24735

alvarezmelissa87 opened this issue Oct 29, 2018 · 2 comments · Fixed by #24742
Labels
bug Fixes for quality problems that affect the customer experience Feature:Anomaly Detection ML anomaly detection :ml

Comments

@alvarezmelissa87
Copy link
Contributor

alvarezmelissa87 commented Oct 29, 2018 •
edited
Loading

Describe the bug:
Seeing call stack error + d3 error when multiple cells are clicked in a row in Anomaly explorer:
screen shot 2018-10-29 at 1 14 49 pm

Steps to reproduce:

  1. From Job Management tab: click Create new job
  2. Select gallery* index pattern (for gallery-2017.05, and so on)
  3. Select multi-metric job wizard
  4. Under Fields select bytes (mean)
  5. Under Split Data select method
  6. Give job a name, etc then click Create Job
  7. Go to View Results -> Anomaly Explorer
  8. Click on 3 of 4 cells from the Overall swim lane ( in 'Anomaly Timeline' ) (only happens on overview)
  9. See something went wrong message (call stack size exceeded) same error every time
    screen shot 2018-10-29 at 1 03 56 pm
@alvarezmelissa87 alvarezmelissa87 added bug Fixes for quality problems that affect the customer experience :ml Feature:ml-results legacy - do not use labels Oct 29, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui

@alvarezmelissa87
Copy link
Contributor Author

Uncaught RangeError: Maximum call stack size exceeded looks to be coming from chart_utils.js line 260 - possibly due to recursive calls of the addTicks function.

@walterra walterra mentioned this issue Oct 29, 2018
Merged
1 task
@sophiec20 sophiec20 added Feature:Anomaly Detection ML anomaly detection and removed Feature:ml-results legacy - do not use labels Jun 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience Feature:Anomaly Detection ML anomaly detection :ml
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ML] Fix a call stack size exception triggered by a negative tickInterval walterra/kibana
3 participants
@sophiec20 @alvarezmelissa87 @elasticmachine