search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.8k stars 8.19k forks source link

[Controls] Filter a subset of dashboard panels #29749

Open alexfrancoeur opened 5 years ago

alexfrancoeur commented 5 years ago

Some users would like to be able to filter a specific visualization inside the dashboard, instead of filtering the entire dashboard using input controls

elasticmachine commented 5 years ago

Pinging @elastic/kibana-app

bhansenmis commented 5 years ago

+1, I would suggest possibly expanding this to all dashboard filters, not just those applied with the input control.

I don't know how much sense this would make for actual implementation, but in my mind I see using some sort of tagging as a potential solution to link a filter to a visual.

Example:

lukasolson commented 5 years ago

Note that the courier:ignoreFilterIfFieldNotInIndex setting should at least limit filters to only apply to panels that are associated with an index pattern with a matching field.

Shifter2600 commented 3 years ago

The Controls Visualization is Locked to the default Index and those fields. Click the + Add filter and you will see that the Field drop down only shows Fields from the Default index pattern. Even when courier:ignoreFilterIfFieldNotInIndex is enabled. This prevents the ability to add filters that reduce the options avaialble that are using a different Index Pattern.

abhitrip07 commented 2 years ago

+1

paugalles commented 1 year ago

+1

ThomThomson commented 1 year ago

The plan for this is roughly related to https://github.com/elastic/kibana/issues/1547 and is also blocked by https://github.com/elastic/kibana/issues/88710.

The idea is that a Controls panel inside a panel group will filter all other panels in that group. Leaving this open for the time being.

woodda commented 3 months ago

Running into this now. Two simple visualizations on a dashboard, each drawing data from different indexes. also has 2 controls. I change the value Control 1 which and it correctly displays a data change in Visualization 1, but causes Visualization 2 to go blank. So I reset Control 1 to "Any" and the data reappears in Visualization 2. I then change Control 2, which correctly displays a data change in Visualization 2, but causes Visualization 1 to go blank. Same deal there.

My question is, how is this not a "day 1" feature? How have others been creating complex dashboards with numerous visualizations, created from different indexes, yet be completely hampered by not being able to use controls because they are tied to the "default" index of the dashboard?

I suspect others have been working around this issue by creating a bloated data view that has everything "and the kitchen sink" thrown in so the controls and visualizations all work from the same dataset. But that seems like a really bad way to go about things, and violates separation of concerns in the data world.

ThomThomson commented 3 months ago

@woodda have you tried enabling the courier:ignoreFilterIfFieldNotInIndex setting? We have this issue related to enabling that setting by default.

Additionally, are you using the new Controls or the legacy Input Controls panel? The new Controls can use any data view.

woodda commented 3 months ago

Using new controls, apparently, as I am able to set a specific data view for each filter control. However, that doesn't prevent that control from "blanking out" the content of one of the visualizations which uses the other index, due to that index not having the field from these global controls in its associated index.

No, I have not tried enabling the courier:ignoreFilterIfFieldNotInIndex setting. Thanks for mentioning it, as I was not aware of it. However from what I've read, that setting must be applied across an entire Space, rather than to just the dashboard I'm interested in. I'm not our company's ELK/Kabana administrator, and I would have concerns that enabling that option could potentially negatively impact hundreds of other resources in the Space created and used by other employees, with no way for me to know the implications of changing that as such a high level. However, if such a feature could be turned on for a specific dashboard, that would obviously be ideal. But I'm guessing that's not possible.

ThomThomson commented 3 months ago

However, if such a feature could be turned on for a specific dashboard, that would obviously be ideal. But I'm guessing that's not possible.

This is not possible today, although it was something we were considering adding. @teresaalvarezsoler FYI.