Interactive filtering

[rashidkpc]

Currently interactive filtering is supported in Discover, this needs to be extended to Visualize and the Dashboard. Ideally it would function in a similar fashion, with the same click and drag events we have elsewhere, along with the filter bar

[farracha]

+1

[sunshine850429]

I also found "brushing" a chart in 3.0 useful when it updated the document table on the same page as well. I could not find any tasks around this, but it would be great if "brusing" or Filtering a visualization on a dashboard filtered the Discover tab or a similar visualization, for those who like t use the timeline to filter the data and dig deeper into the data via the vis.

[jayswan]

In addition to extending the filter bar to the other tabs, I'd like to see it be editable in a fashion similar to Kibana 3. In Kibana 3, one of my most common workflows is to create a series of filters with the "either" option selected, and then use the toggle checkbox to quickly view the results of different combinations of filters. The ability to manually edit the contents of the filter string is also essential to this workflow.

[marminthibaut]

👍

[mikebell90]

Maybe I am missing something, but filter interactivity simply isn't there, except in VERY limited fashion during dashboard view of a saved search? In Kibana 3 i can have a bunch of these babies sitting there, easily toggled on and off. The only way I found in kibana 4 to make them is to open the row and click on the mag glass. And then, since its not editable it's often worthless.

[jayswan]

@mikebell90 you can get the filter bar in Kibana 4 on Visualize and Dashboard by clicking on any element in an aggregated visualization, and then you can interact with each filter in much the same way as in Kibana 3, except that you can't edit them.

The lack of editable filters and the "either" option in filters in Kibana 4 is disorienting to me, since I use both "either" and filter editing constantly in Kibana 3. If someone has a suggested alternative workflow for Kibana 4, I'd love to see it. Everything in the Elasticsearch documentation trains us to use filters as much as possible for performance reasons, so I'm not sure what else to do.

[mikebell90]

Not only that, because you can't edit, you can't add the (for my druthers) very useful exists operator for a filter. For example we have an exception class field (java) - this is very useful for finding items with exceptions attached.

[tyrannosaurus-becks]

Not certain if this will be any help, but I'm just learning Kibana 4 today and one of my coworkers noted that Kibana 4 shifts dramatically away from using filters, to using the text search box instead.

An example query using the search box might be @fields.host:somehost* AND @message:"some string". The query string syntax is described here, and it may be Lucene under the hood, described here, which does appear to support an "exists" query.

Please do point it out if I'm wrong.

[jarlelin]

I second the need for both:

1. editable filters
2. OR - operator for filters

[avcherkasov]

+1 for make filter editable!

[marcuslacerda]

+1 editable filters

[abferm]

+999999999999999999999999 for editable filters

[muddman]

+1 editable filters

[roman-parkhunovskyi]

There's an open issue for editable filters - #1583