Kibana: Input Controls visualization should not ignore dashboard filter

[nasirus]

Hi,

it will be very useful if Controls don't ignore dashboard filter or make it as option like in visual builder.

Thx

[kobelb]

Hey @nasirus the "Controls" Visualization is currently explicitly designed to ignore all Dashboard/Globals filters, would you mind elaborating on your specific use-case where not doing-so would be useful?

The original intent was to ensure that all potential filter options are listed, similar to the way that when you add a filter using the "Add Filter" UI, the auto-completes aren't impacted by the existing filters.

/cc @nreese

[idkw]

I have the same requirement.

So when I have data that look like :

[
  {
    "foo": {
      "a": 1,
      "b": 2      
  },{
    "foo": {
      "a": 1,
      "b": 3      
  },{
    "foo": {
      "a": 2,
      "b": 4      
  }
]

The use case is to have the filters behave like facets selectors.
When I have two input controls on :

• foo.a
• foo.b

When I apply the filter a = 1 for the first control, I want the second control to only show the remaining options which are :

• b = 2
• b = 3

b = 4 should be hidden in the second control because its a value is not 1

This behavior is useful to show what is left in the filtered data to help the user narrow his search more.
Of course it would only be an opt-in feature on the control input.

[drkelley]

I also have this requirement. My use case is the following:

I have users that are only interested in specific Product categories. Under each Product there are numerous Types. I would like to build a Control on my dashboard that only lists the Types associated with the specific Product filters that I have in place. Without the ability to filter data in the Control drop down my users sees Types that are _NOT_ associated with the Products filtered specifically for the dashboard.

Hope that's somewhat clear...

Thx.

[nreese]

@drkelley 6.3 will add the ability to nest controls. This will allow your product categories selection to filter the Types selection list.

[idkw]

Nice feature, this will solve one part of the issue.
However it won't solve the other part, which is that when there is no ancestor on a control, it will still display all the possible values, ignoring any filter that might have been set on the dashboard.
In the ancestor selector, it might be a good idea to choose between :

• empty which is the current behavior, ignore all filters
• "dashboard", which takes all of the currently applied filter on the dashboard to narrow the search, useful for the root control which can't have a control ancestor
• control ancestor like in your PR which narrow the search with all the filter taken from its ancestors

The only difference here but which makes it very useful in my use case is that a single control would react to the changes made by other kind of filters (e.g: filters applied by clicking on a chart)

[Yamoksh]

Thanks for raising this issue. I have a similar use case in which I want to show the data only if the drop-down of controls visualization is selected. If not, it should not show any data.

When I don't select any field, but still It showing all the data.

[joaosp]

I also have a similar use case where I need to have the ability to filter the first option list
A simple filter field in the option list config would be sufficient

[bhansenmis]

I would also like to see this implemented. All I want is the ability to filter what results appear for a field in the dropdown.

[fxprunayre]

I would also like to see this implemented. All I want is the ability to filter what results appear for a field in the dropdown
A simple filter field in the option list config would be sufficient

One option would be to add an optional filter to the aggregations returning values to populate the list.

In this case the list could be:

• all values for a field from the index
• a limited set of values for a field depending on a filter

Suggestion of PR for that https://github.com/elastic/kibana/compare/6.7...fxprunayre:6.x-vis-control/add-filter . Would this be the way to go ?

[FrancoisDB]

It would indeed be really useful.

[Eniqmatic]

+1

[oscarlopezp]

+1

[schafer21mcm]

+1

[fxprunayre]

Following previous comment https://github.com/elastic/kibana/issues/16123#issuecomment-471993927 for 6.x branch, here is the change for the 7.x branch https://github.com/elastic/kibana/compare/7.x...fxprunayre:7.x-vis-control/add-filter if that is of interest ?

[TFreseni]

In the same boat as most here. Looking to have the ability to use drop downs that pull from the already applied filters rather than showing every possible value for that field. Makes life easier and more structured for those unfamiliar with the data. Link to forum post

[tomryanx]

Could not agree more with this comment from @TFreseni

Makes life easier and more structured for those unfamiliar with the data

[ViktorMS]

Would be a huge improvement to be able to let unexperienced users filter data using user-friendly controls.

For example, selecting a username from error logs for a particular day. If we only have the “index” filter, we get all usernames from the beginning of time. The results are so many, it times out.

[jmwrobel85]

Is this somewhere on the roadmap? I could be really useful for filtering. I like fxprunayre implementation.

[Sagesh]

Data showing in "Add Filter" are not filtered based dashboard filter.

[raphaeldelio]

In my case my application is separated by clients and I have a different User Tracking Dashboard for each client. I want to create a control to filter by Username. If the controls respected the filter it would show only those users of this specific client. Since it doesn't it will show users from all clients in every dashboard.

Will it be implemented? Perhaps a button Use Dashboard Filter as there is one Use Time Filter would be enough.

Thank you

[mykael22000]

This would be really helpful. I'm using the new drill down structures. In the first panel the user selects a country which brings them to a panel showing just data from that country. There is a drill down control to then let them select a town - problem is, it shows all towns in all contrie, which makes it less than useful. I did try adding a control to let the user select the country as well, but it's not getting initialized when the drill down panel is display - even though the filter for country shows on the filter bar and affects the panel.

At present the control will let me select a town that is not displayed on the page and will never be displayed on the page because it's excluded by the country filter - because the town isn't in the country. Selecting it just shows an empty graph. Technically correct, but not useful.

A second scenario is that I have a control to select a product - that is also showing all products, not just the ones sold in the country. On the drill down panel I want the user to be able to filter by town, product or both, so there's no clear hierarchy that can be used to 'order' the controls.