Kibana: Scale to Y-Axis Data Bounds option should be checked when the data scaled to its bounds

Created on 4 Mar 2015 · 7Comments · Source: elastic/kibana

Hello,

I'm trying to create a vertical bar chart with an X-axis as Date Histogram and a Terms sub-aggregation splitting charts.
One chart got values between 0 to 250k, others between 0 - 100. All splitted histograms got the same y-axis and no bar is visible except for one.

I activated the 'Scale Y-Axis to Data Bounds' hoping it will solve my problem, but it seems not functional.

I'm using Kibana 4.

Thanks for your job.

Vislib Visualizations bug discuss

Source

daks

Most helpful comment

I thought this option means that each graph will adapt its y-axis to its own set of data, which in my case would mean that graph 1 would have a 0-250k axis, the second 0-30 and the third one 0-70.

If it's not the case, I don't understand what is this option for.

daks on 5 Mar 2015

👍2

All 7 comments

@daks what is the min and max y value of each dataset (i.e. chart)? Could you also include a screenshot of your example?

The Scale to Y-Axis Data Bounds option when visualizing multiple charts does not scale each chart to its data bounds. That functionality needs to be implemented, and for that reason I am adding the bug tag as the option is misleading. But to really know if the function is buggy, I'd need to know the extent of all your datasets.

stormpython on 4 Mar 2015

This first image shows the rendering for the 3 top terms, and this one for the bottom 2 terms.

So I got 3 datasets, the first one with data ranging from 0 to 250k, and the 2 others with data from 0 to 70 max.

daks on 4 Mar 2015

@daks ok, so in your case the y-axis did scale to the data bounds, as 0 is the min and 250 and 70 were the max.

However, the implementation of Scale Y-axis to Data Bounds is off.

It should automatically be ticked when the data is scaled to the bounds of the data. Keep in mind that this is a global representation of the data, and not at a chart level. This also needs to be changed. At the moment each chart is not scaled individually. That is, every chart shares the same Y axis. We are working on implementing separate scales for charts. There is already an issue for this, see #2021. Finally another issue is that charts without data or with data that are all zeros should render a no results found message.

I am breaking these out into issues and re-titling this issue.

stormpython on 4 Mar 2015

I thought this option means that each graph will adapt its y-axis to its own set of data, which in my case would mean that graph 1 would have a 0-250k axis, the second 0-30 and the third one 0-70.

If it's not the case, I don't understand what is this option for.

daks on 5 Mar 2015

👍2

I wonder what to do about this option -- I agree it's misleading given that it doesn't scale to Y-bounds of individual charts when charts are split, which is this enhancement https://github.com/elastic/kibana/issues/2021. It is also has known issues, such as: https://github.com/elastic/kibana/issues/7236#issuecomment-253613752

tbragin on 13 Oct 2016

Hi,

Iam trying to create a chart where in the x-axis is the build version (Ex: 1.0,1.1) which is fetched from the index. Now i want the Y axis to have the timestamp (ie the time and the date the build was trigerred)

Is this possible to do as i see only count that be used for Y Axis

amruthapbhat on 5 Jun 2017

Looking at this, this looks to be resolved.

We do have the issue of splitting charts no having individual y-axis extents, that is tracked here https://github.com/elastic/kibana/issues/2021.

@amruthapbhat You can do that by using horizontal bar charts. Check out the latest v5 version from Kibana. If you have follow up questions, the discuss.elastic.co/c/kibana forum is a good place to continue the discussion.