Customizable axis labels

[AlexIoannides]

It would be really useful if chart axis labels could be edited - e.g. instead of 'count of documents' as a y-axis label, I'd really like the ability to relabel it as 'number of observations', etc.

[thorrsson]

+1 but extended to include the labels for each item as well

for instance if the split chart shows 6 groups of data, the label for each group is currently similar to: "Top N $fieldname: $Value" In charts that have a number of items, or on smaller screens you end up seeing "Top 4..." for each item. (Attached and example that shows the original request and and my extension)

[matthewgaulin]

+1 or even just dont show the "Top N $fieldname:" part and just show the value of the field.

[opswhisperer]

+1

[theNewFlesh]

Customizable legend names and customizable names and orientations for SplitChart rows would be awesome too.

[chadrik]

+1

[Blevene]

This is immensely frustrating for the reasons that Thorsson has described. Additionally, instead of top/bottom, I'd like to be able to define the order in which its split (for example I'm trying to do bytes(total) ~ Time | Node).

[theNewFlesh]

Also customizable axis ticks (as opposed to labels) would be very helpful. Configuring their display with a formatting string would be a very workable solution from my perspective. This link gives one such specification for formatting string syntax: https://docs.python.org/2/library/datetime.html#strftime-and-strptime-behavior

[chadrik]

@theNewFlesh, it might be good to the tick suggestion into a separate ticket, since it is more limited in scope and would likely be solved in a different way than axes labels.

[jyana]

+1

[chadrik]

+1

[joelclimbsthings]

+1

[carlosvega]

Yes please, make it able to customize labels, axis and stuff !

[ignaciovazquez]

+1

[pnarwa]

+1 Just wondering when this feature will be available? Customizing axis labels will be a useful feature to have. Thanks.

[rcrezende]

+1

[vikrim1]

+1

[marvin659]

+1. I want to add unit to describe the unit of the numbers in x-axis

[phanisrinivas]

+1 . This would be a very helpful feature if provided. Because for some of the filed names where we don't have much control in terms of representing in meaningful labels.

[acheriat]

+1 (marvin659)

[acheriat]

What I mean is so commonplace but forgive me share my frustration ... Indeed, While there are many advantages of Kibana, it is unfortunate to have to look for an alternative due to lack a basic features (but very important for a end user) such as:

• Renaming of legends, axis labels,
• Addition of a measurement unit to a quantity, ...etc.

[madrover]

+1

[aclayola]

+1

[KamilKeski]

Major regression from 3 and is high on the list for me regarding not migrating to 4.

[alexnederlof]

+1

[pickworth]

+1

@rashidkpc @panda01 Should this enhancement be merged with https://github.com/elastic/kibana/issues/1896 from the 4.3 enhancment/roadmap? I beleive they are extremely similar requirements, as a field alias would give you the same outcome;

i.e. Ability to have field aliases per visualization/search object would be great, and more flexible, instead of per index.

You can combine this with the Ability to Hide "Top n ...", "Average ..", "Sum ..", "Count .." (via checkbox) that is force prepended to the axis titles. I have found this to be a bit annoying and misleading (in terms of presenting labels for data) under certain visualisation conditions.

[bounddog]

+1

[balamacab]

+1

[blairjuice]

+1

[tonykcn]

+1

[ofir-petrushka]

So not even hiding this for the next 2 versions? should we just downgrade to kibana 3? :(

[tarunsapra]

Kind of surprising that this important request hasn't made it to 4.2 instead moved to 4.4

[novozhenets]

+1

[GrahamHannington]

I thought I was missing something, but reading this issue, perhaps I'm not. "@timestamp per ..." is a fugly axis label. I guess I could specify some other field with a more readable name - without an at-sign prefix - as the timestamp, rather than @timestamp itself, but that seems like a kludge, or at least, an annoyance. Or perhaps people these days are so used to seeing words prefixed by non-alphabetic characters that "@timestamp" looks commonplace? #I'mnotthereyet.

Can someone point me to documentation (or a schema) for visState properties?

[rkhapre]

+1

[jakauppila]

+1

[pmoust]

Would love to have this in soon.

[cschotke]

+1

[JohnnyQQQQ]

+1

[laukamp]

+1

[sebz1504]

+1

[pickworth]

@cherah30 your point regarding addition of a measurement unit is valid. This would be a really good feature. I have not needed millimeters, but percentage symbols is something that I would love to have, and have needed a several times while using kibana.

For obvious reasons, converting the field to a string is not practical but seems to be the only way. The field should remain numeric, and an option to append a unit of mesurement which would appear in the chart / on hover

[ghost]

+1 How about letting us set a chart title too? Edit: One nice thing about Kibana 3 is that less technical users can understand the charts better because we can title them. They don't need to know what the field names mean.

[tpeyrard]

+1

[pickworth]

2284 @cherah30

[bparruck]

+1

[felka]

+1

[ghost]

I'd also like to request this hits a version of Kibana that's compatible with ES 1.7. We are still stuck on Kibana 3 because we can't put titles on our charts in Kibana 4.

Moving to ES >= 2.x just to be able to get chart titles in Kibana would be a difficult thing to do due to how many applications we have that use ES 1.x at the moment.

[Soszu]

+1

[ghost]

+1

[hegold]

+1