URL templating for Drilldowns using required field from the dashboard filters

Elastic Stack Kibana
1

Hi Team,

We are trying to create a drilldown using URL templating to link two dashboards. But while moving from one dashboard to other we need to carry one particular field(recon_key) which is added in the filters to be carried as a filter to the other dashboard but not all the filters which are added. Could you please suggest us how to select a particular field from the filters to be carried ignoring other filters. Note: The users might select the filters randomly so that we cannot use filters offset to carry the recon_key from the filter.

For example:
From the below URL there are 3 filters added 1. Primary_sourceSystemId:OMS_SAPMENA
2. Secondary_sourceSystemId:SHP_ASEAN
3. recon_key: 24121619XXXXX(Sample value but the url should take the value what ever it has)
Out of these filters we need to take only recon_key to go to the other dashbord. Please suggest.

https://xxxxxxxxxxxxxxxxxxxxxxxxxx/app/dashboards#/view/cf954448-5885-4424-b24a-0d43656c3e3c?_g=(time:(from:'now-7d/d',to:'now'),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:d1b4ec03-6510-4e47-b418-cd24774f19a7,key:Primary_sourceSystemId,negate:!f,params:(query:OMS_SAPMENA),type:phrase),query:(match_phrase:(Primary_sourceSystemId:OMS_SAPMENA))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:d1b4ec03-6510-4e47-b418-cd24774f19a7,key:Secondary_sourceSystemId,negate:!f,params:(query:SHP_ASEAN),type:phrase),query:(match_phrase:(Secondary_sourceSystemId:SHP_ASEAN))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:d1b4ec03-6510-4e47-b418-cd24774f19a7,key:recon_key,negate:!f,params:(query:VN/P2/24121619XXXXX),type:phrase),query:(match_phrase:(recon_key:24121619XXXXX)))))

2

Can someone please help me with this request.

3

Can someone please help me with this request.

4

@venkatkumar229 Unfortunately, your specific request is not currently possible. Drilldowns are designed to either take all filters or no filters, and we don't have an option to configure a specific subset. As a workaround, you could pin your recon_key filter (i.e. make it a global filter) and then it would follow you across all of Kibana?

If that workaround doesn't work for you, please feel free to make a feature request so that we can better prioritize this :slight_smile:

1 Like
5

Thank you @Hannah_Mudge , if i try to pin recon_key after selecting a particular value from the dashboard. All the other filters which i have selected will be flowing to the other dashboards and if i remove filters nothing will be flowing to other dashboard even if i pin them. I will try to raise a feature request as suggested.

6

Hi @Hannah_Mudge ,

I have raised a feature request for this use case in Git.