Editable filters

[jimmyjones2]

Would be great if filters were editable in the Kibana 4 Discover page, like they were in Kibana 3. This allows you quickly add a filter for a field of interest, but change the value to one not in the current set, or something else you're interested in. I know it can be done with the query, but would be better for people scared/too lazy for that!

[rashidkpc]

While I agree this is a good feature, it likely won't happen for some time. There is an infrastructure that needs to be built around filters to properly facilitate the inclusion of custom filters. Long term we want to provide structured inputs for filters, shorter term we need the ability to insert JSON filters

[mkliu]

On the same line, i could click on a pie chart and filter down to a set of data, that feature is lost in Kibana 4?

[kadaan]

This should be available not just on Discover but also Visualize and Dashboard

[ecneladis]

+1

[zytek]

+1

[szibis]

+1

[rayl]

+1

[bladypirat]

+1

[tomkregenbild]

+1

[benningm]

At least a button to create a filter from the current query field would be useful.

[sebdotv]

+1, Kibana 4 should make it easier to work with filters because cached filters generally outperform queries [http://www.elastic.co/guide/en/elasticsearch/guide/current/_queries_and_filters.html]

[rugger74]

+1. This may prevent migration to the new kibana for my company.

[siavashgh]

+1

Editable filters in the former version was one of the best features. Specially because of the immediate response as @sebdotv mentioned.

[peterlau]

Here's my workaround to this. Not ideal but it might satisfy some. This will allow you to add arbitrary filters to your search, not just the limited term match filters you get by clicking on fields.

1. Under the Discover tool, customize your search to your liking, minus any custom filter(s) that you need but cannot add at this point. Save it.
2. Click on the 'Open folder' button. Inside the dropdown, click the 'manage searches' link at the top right hand corner.
3. Click the pen next to the search you created in step one.
4. In the last text box (kibanaSavedObjectMeta.searchSourceJSON), scroll to the bottom and find the 'filter' array, add your custom filter to the bottom. In my example below I'm seaching for a non-null 'exception_class' field using an asterisk. This cannot typically be done using the interface.
5. Save the search object, this takes you back to the 'manage searches' page. Click on the 'Eye' button next to your search to test it.
6. It's important that you've made all the filters that you need in step 1 because from this point onward you won't be able to add any new filters via the UI. It'll generate a JS error. You can however enable and disable any of the existing filters, including any custom filters that you just added. The query bar should work as normal.

 "filter": [
..... existing filters .....
    {
      "meta": {
        "disabled": false,
        "index": "[logstash-]YYYY.MM.DD",
        "key": "query",
        "negate": false,
        "value": "exception.exception_class:*"
      },
      "query": {
        "query_string": {
          "analyze_wildcard": true,
          "query": "exception.exception_class:*"
        }
      }
    }
]

[roman-parkhunovskyi]

+1. the feature which forces me to keep Kibana3 still alive

[hetzge]

+1

[roman-parkhunovskyi]

Doesn't work in Firefox 37. Related to https://github.com/elastic/kibana/issues/3610.

[thelalle]

+1

[kmartensson]

+1

[hyperletter]

+1

[koniin]

+1 , would really improve usability!

[SecEng]

+1

[oshmyrko]

+1

[nitdana]

+1. Yes.

[arturpriz]

+1, Guys, we need it.

[toleksyn]

+1

[pielgrzym]

+1

[clstokes]

+1

[fbaligand]

+1

[fbaligand]

Up to me, it is really a key feature. Like @rparkhunovsky, I can't totally go to Kibana 4 until this feature is not implemented.

[landonix]

+1

[peterlau]

+1 @rparkhunovsky @fbaligand Same here on running a dual K3/K4 setup and not being able to fully upgrade.. This issue is the biggest blocker for me, and the fact that you cannot give names to filters in a subaggregation. We need proper labels and not a bunch of cryptic filters to appear in the legend box.

[Prazzy]

+1

[Maran123]

+1 wont' be able to move from kibana 3 until this is fixed

[stephanmitchev]

+1

[MarkGavalda]

I'm shocked that such an essential feature from Kibana 3 is missing from Kibana 4... I had to do a couple of Google searches, well, to arrive here plus to confirm that it's not just me who cannot figure out how to simply edit a filter "bubble". Please add this...

[davidski]

+1 This is absolutely key functionality. Honestly, Kibana 4 feels very not ready for prime time. Interesting architecture and lots of potential, but so not ready to replace KB3.

[mckennab]

+1 definitely regression

[stephanmitchev]

+1 absolutely necessary

On Tue, Jun 30, 2015 at 1:54 PM, mckennab notifications@github.com wrote:

+1 definitely regression

— Reply to this email directly or view it on GitHub https://github.com/elastic/kibana/issues/1583#issuecomment-117282685.

[heksoli]

+1 no discussion over to be or not to be.

[LaurentChardin]

+1 ... agreed with @hirobertgit

[warpkanal]

+1 K4 is nice but without editable filters I'm better off with K3

[tiago-loureiro]

Any plans to add this in the near future? This was one of the most useful features in K3!

[jerrac]

@tiago-loureiro There's a "4.3.0" label on this issue. So I'd assume it's slated for when 4.3 is released. Since we're only on 4.1.1 now, that makes me a bit :cry:

At the devs: What kind of skills are needed to add this feature? Or does it require touching too many pieces of Kibana for it to be easy?

[elvarb]

+1

[andrewvc]

+1

[mkliu]

+1 million

[loren]

+1

[willejs]

+100000

[vaiwa]

+100001