Kibana: Y Scale to fit the bounds of the data for each split chart

[stormpython]

Currently, creating multiple charts in a visualization means that all charts will share the same y-axis scale. We should add the option for the user to specify if they want the charts to share the same y-axis or fit the bounds of the data.

[ZeAleks]

Thank you Shelby,
This is exactly what I mean.

Alek

[rashidkpc]

Isn't there already a flag for shareYAxis? Should be pretty simple to wire this up to the chart options.

[stormpython]

@rashidkpc It won't currently work. The shareYAxis flag is a remnant of the older vis library. The problem that we have to solve here is to add the y axis on mulitple charts in the Column display.

[damienjoldersma]

+1

[damienjoldersma]

@stormpython Here are two choices for you to consider managing the y axis on Column display:

• Possibly the best (only?) choice to is to show separate y axis per graph, I think at first this might sound unattractive, but on second thought I think it might actually work, as your eye will overlook and you can still see the trends you want and if you need to then you can focus in on the y axis to see resolution.
• The other choice is to simply disable multiple y axis on column view, i.e. force them to use row mode if they want that functionality.

[hex0cter]

+1 for this feature.

[lancechentw]

:+1: for this. Having the same Y-Axis scale bound through all charts seems not useful in certain cases.

[ebuildy]

You mean a bug/case like this:

Is it already planed for a next release? or do you have suggestion in how to do that maybe? I will glad to help since I really need this feature.

Thanks you,

[bsquare2]

+1 for this feature.

[rolebi]

+1

[ApsOps]

It's been more than a year since this was opened. Any updates?
Not having this feature is surely a bummer :(

[donpinkus]

+1

[romfreiman]

+1

[brettbates]

+1

[ApsOps]

Hi @stormpython . Any update on this? :)

[rajeshnambiar]

+1

[boillodmanuel]

+1

[cechovsky]

+1

[EugeniuZ]

+1

[mrjameshamilton]

+1

[ChrisMagnuson]

+1

[pjcard]

+1

[zdenkas]

+1

[jorymorrison]

+1

[fnukis]

+1

[gregoryo2014]

+1

[blodan]

+1

[kwolfe19]

+1

[oloflarsson]

+1

[chambj]

+1

[alkuzad]

+1

[ApsOps]

Almost 2 years guys.. any update on this? 😕

[Anastasia-mx]

+1

[carlosvega]

+1

[GoodMirek]

+1

[bbarn3y]

+1

[alkuzad]

+42, guys stop that, we are subscribing this thread to check for progress, not for +1

[jimanvlad]

News?

[ppisljar]

it is a bit tricky to implement as currently all charts share same axes, specially with additions we added in 5.4 (multiple axes and the ability of horizontal charts).

as a workaround you could do 3 separate charts (instead of a split chart).

[pjcard]

"as a workaround you could do 3 separate charts (instead of a split chart)."
The problem with that is it means that the number of charts is no longer dynamic, i.e. if I'm using terms to split and a forth term is added then that won't be shown if I manually set up the charts.

[pjcard]

Would the concept of an optional scale multiplier help? I.e., all charts still share the same axes, but those axes are scaled according to the data they contain.

[stuba]

+1

[sambigelow]

@ppisljar Is there any way of doing this multiplier? Some feature like this would be quite nice. My charts are identical, except for the rate at which they grow and their y-axis scale is drastically different, but the number of charts is dynamic, as well as the keys splitting the charts

[ppisljar]

not at the moment. once we get to this i think the original suggestion to allow to have separate axes sounds good. however this is not on the roadmap yet so not sure when can we get to it.

[sambigelow]

Thank you for the response. I’d love to see the separate axes also.

[brandond]

This seems like an awfully critical feature to not even have made it to the roadmap yet.

[cawoodm]

Bump

[7kn]

Another +1 for this feature request.

[yeDor]

+1

[janreges]

+1

[SoloTSi97]

+1

[matthagenbuch]

+1

[ravulareddy]

is this fixed in 6 ?

[pjcard]

It's still open, so presumably not.

[pjcard]

@rashidkpc This request has been open for four years, is it possible for someone to look at it again?

[henrytran026]

Can someone please fix this?

[nihilistdbanana]

Hi, I would like to try solving this. Can someone help me out on how I should start? @spalger?

[ppisljar]

best to check with @markov00
this would best be implemented in the new charts implementation we are working on.

[luizfzs]

+1

[22mano1bil]

+1

[tleach]

+1

[alkuzad]

@tleach

[rout39574]

+1

[sickmint79]

hey it's 2020 and this is a totally useful feature i just googled and found people have been requesting since 2014. cool

[tavishall]

+1

[sastorsl]

+1

[vickyd885]

+1

[nihilistdbanana]

Hi, Has Anyone picked this up yet? If not, I'd like to pick it up. I might not be able to do this quickly, but I'd like to work on this.

[jorymorrison]

Pick it up, please. This has been four years.

On Sat, Apr 4, 2020, 3:18 AM nihilist-banana [e-mail]
wrote:

Hi, Has Anyone picked this up yet? If not, I'd like to pick it up. I might
not be able to do this quickly, but I'd like to work on this.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elastic/kibana/issues/2021#issuecomment-608988429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAONMSKMKKUDH26CRKIRXSDRK3NNFANCNFSM4AX7O3XA
.

[pjcard]

Six years actually. I doubt something like this would be assigned externally, though.

[nihilistdbanana]

I'll start looking at it anyways, see if I can do something without breaking everything.

[lposani]

Any news? Crazy that it has been around for so long

[ronaldocpontes]

+1

[jorymorrison]

This issue will never die.

On Mon, Nov 16, 2020 at 12:36 PM ronaldocpontes [e-mail]
wrote:

+1

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elastic/kibana/issues/2021#issuecomment-728214605,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAONMSMTUXL4T4FY5GHT25LSQFPLBANCNFSM4AX7O3XA
.