Configurable filter/range legend values

[cdahlqvist]

When I create a Filters and/or Ranges aggregations, the description shown in the visualisation automatically seems to default to the filter text or range. As this can potentially be a complex string containing field names, it would be very useful if it was possible to specify a display text for each filter and/or range.

[noamgal]

also can be useful to add some groovy script to just run on displayed values.
In contrast to scripted fields it will be used just for display and as a result will be possible to have a filter from the displayed values

[thopewell]

On a related note, when combining visualisations in the dashboard, the scale of the X axis seems to be dependent on the size of the legend. For instance, if I build a dashboard made up of 2 full width time based historgrams, the X axis times don't fully align unless the legends have the same width. This makes it harder to identify related events across different visualisations.

[tdesaules]

Hi !
So there no option to rename legend at this time right ?

[timroes]

I think this is a feature that shouldn't be missing in Kibana 4. As @cdahlqvist mentioned, we have a lot of dashboards where the filter is something like "type:123456" which is totally not understandable for the people actually working with the dashboards, where a label is indispensable. In the current state of Kibana 4 Beta this seems the only show stopper right now, that would prevent switching. Thanks for your great work on the new version so far.

[spalger]

Partial duplicate of #1816

[timroes]

I think there are several points to discuss for this issue.

First: Is this needed for all aggregations or only for some?

In my opinion this would be enough for range and filter aggregation in the beginning. In this aggregations you anyway define some custom "queries" in an input box and I think it makes sense to name these queries with custom labels, that should be shown.

It would also be nice to someday in the future change labels in e.g. terms aggregation. But since you don't exactly know what values will be returned by the terms aggregation, I don't think its useful at the moment. If you would like to label these custom, because you know what field values you want to change to what label, just replace it by a filter aggregation, and specify labels there (once implemented ofc).

Second: How should it look a like?

I think there are several options how this could be implemented in the editor. I have made some sample screenshot:

In this case, I added a gear icon beside each delete icon. Clicking on that icon will expand the Label box (which could also contain a color circle, to select a color (as it was possible with queries in Kibana 3, and kind of what asked in #1362).

You can click the gear button again to collapse that Label box again. The gear icon itself was just a first impression, one could of course find a better representing icon.

Some other options I thought about:

Using that kind of button, but instead of expanding something, use a tooltip to display the input box (and a color selector). Tooltips are always nasty on mobile, so I didn't mocked this.

Some other behavior I think that could work well: Just remove the gear icon completely again and just reveal the second line, when you enter the query textbox. As long as you stay in that input field or enter the label field it will stay expanded. As soon as you focus another query input field, the previous open label box will collapse again, and the label box of the now focused input will expand.
This could make the default collapsed state a bit less cluttered, due to the missing icon, but of course label boxes would automatically expand now every time you focus a field (even though you might not want to change a label).

The same ideas would also work well with the range filter.

Edit: Another option would of course be to show the label field always for every field, but I think that would clutter the UI way too much.

[KlavsKlavsen]

totally missing this.. I split up site traffic in hits/not hits, logged-in/anonymous users and dynamic/static content. a total of 6 filters with VERY long names..:
NOT cookie: SESS* AND NOT handling: hit AND NOT ( url.raw: .woff OR url.raw: *.js OR url.raw: .png OR url.raw: .gif OR url.raw: .ttf OR url.raw: *.css OR url.raw: .jpg OR url.raw: .jpeg OR url.raw: .ico OR url.raw: .swf OR url.raw: .eot OR url.raw: .txt OR url.raw: .pdf)

does not really work in kibana 4 without legend value option :(

[Marche86]

Yes, please, it's a really important functionality.

[heikkis]

Wanted!

[zaakiy]

@timroes: love your work!

+1 label boxes would automatically expand now every time you focus a field
-1 tooltip..agree not good on mobile

[beiske]

+1 From me. Got a dashboard for monitoring AWS cost and use filters in order to split up some categories that need multiple fields to be distinguished.

[julienadriano]

+1 as well!

• Julien

On Mar 15, 2015, at 4:28 PM, Konrad Beiske notifications@github.com wrote:

+1 From me. Got a dashboard for monitoring AWS cost and use filters in order to split up some categories that need multiple fields to be distinguished.

—
Reply to this email directly or view it on GitHub.

[dtabuenc]

It would also be nice to be able to select the color of the bar based on the filter, like in kibana 3

[DaveWilcock]

Same. Applying complex queries as the filters, means that I just get those (very) truncated queries as the legend, which is really not very usable at all. Application of a per-query legend would be ideal.

[pedro-andrade]

+1 for legend and color !

[pmurgatroyd]

+1 here too, its very difficult when you are presented with a wrapping legend that is a file hash!

[mateialexandru]

+1 for legend

[kevintelford]

+1 for display text for complex filters

[tbragin]

I noticed recent +1s on this... this functionality is available in Kibana 4.2+ and this issue is now closed.

@TheBig159 your question seems like potentially a new enhancement request, if so I'd suggest opening a new issue for it

[thj-dk]

@tbragin; from my understanding it's only possible for filters, right? Or am I missing something? Any documentation describing these labels?

[tbragin]

@thj-dk yes, filters aggregation only -- see screenshot. Docs are here.

If you have another request, I'd file a separate issue. Since this one is closed, your comments might get buried here, I'm afraid.

[jravichetan]

+1 editable/configurable legend

[megakid]

+1

[shuva10v]

+1

[uros678]

Anybody knows what the status is on this topic? Is it going to be implemented?

[giorgio94c]

+1

[ssable94]

+1

[jordanano]

+1

[ataormina-rmn]

+1

[fathijemli]

+1

[chaoranxie]

+1

[Xeteskian]

+1

[dfliess]

+1

[razaba]

+1

[iamshahjahan]

+1

[stollentroll83]

+1

[wdtmatt]

Not sure why this is closed. Only part of the issue has been addressed. Custom labels for ranges is still a need today!

[GuillaumeMartial]

+1

[RuralHunter]

This is a very basic feature for any chart application. I don't understand why this is closed without any explanation.

[nechama]

+1

[JohnTheBeloved]

+1

[vvvvoid]

+1

[ellismendez]

+1
Dashboards should always have an option to rename legends...in the age of IoT, Big Data and Analytics, one should not alter the original raw data headers just to make it readable in a dashboard. This is a dashboard UX/UI 101 requirement. Look at Splunk, Qlikview, Pentaho, etc... they all do it.

[georgezoto]

+1

[niulin]

+1

[vserluco]

+1