-
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
TSVB is retaining results even after indexpattern is removed from options #31951
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:TSVB
TSVB (Time Series Visual Builder)
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Comments
bhavyarm
added
bug
Fixes for quality problems that affect the customer experience
Feature:TSVB
TSVB (Time Series Visual Builder)
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
labels
Feb 25, 2019
Pinging @elastic/kibana-app |
These are the es logs:
|
Interesting issue. I think it'a a regression issue after #24832 and #30946 |
7 tasks
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:TSVB
TSVB (Time Series Visual Builder)
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Kibana version: 6.7.0 BC3
Elasticsearch version: 6.7.0 BC3
Server OS version: darwin_x86_64
Browser version: chrome latest
Browser OS version: OS X
Original install method (e.g. download page, yum, from source, etc.): from staging
Describe the bug: I was playing with TSVB and trying to get a top 10 hit on machine.ram on logstash dataset from loading sample data from Kibana tutorial.
https://www.elastic.co/guide/en/kibana/current/tutorial-load-dataset.html
I couldn't get the value for top hit on ram so I deleted the logstash indexpattern and voila - all of a sudden tsvb is displaying the graph, gauge chart and top n for ram that too for a timeperiod which doesn't make sense on the logstash dataset.
This is very confusing and also its letting the user save the chart like this:
The text was updated successfully, but these errors were encountered: