Issue using multiple {{gquery}} variables in Graph app Drill-down URL

I am using the Graph application in a way that the end result is I have selected a single node which is essentially an email address. In this example we're going to say that email address is I have set up a drill-down so that I can go from Graph to a Kibana dashboard which is filtered using the email address selected in Graph. I can hard code the drill-down url and it works as expected. The URL looks as such:

(two notes. i have omitted the leading part of the url as its not relevant. I have made this url decoded as its easier to read, but the url used in Graph is encoded.)


When using that, I am taken to the appropriate dashboard with the filter appropriately applied. The obvious problem here is that the email address is hard coded, so any time I select a user other than, it won't work as expected. What I attempted to do was use the {{gquery}} variable to dynamically place the email address of the selected node from Graph into the URL. The updated URL looks as such, which is essentially the same as above just replacing with {{gquery}}:


This did not work as expected. In two of the three places, the literal "{{gquery}}" is plugged into the filter, and not the value of the email address coming from Graph. What I discovered is that it appears as though {{gquery}} can only be used once in the URL. After that, it is interpreted literally as "{{gquery}}". Is this intended functionality or is this possibly a bug? Since the Kibana url requires the actual email address plugged into 3 places, but gquery can only be used once, it makes it impossible to dynamically set the value in all 3 spots in the url.

For anybody looking for a workaround, you can set two of the email address parameters to a space (or %20). Note, that NULL did not work. The one spot where gquery has to be used is in the part of the url that sets the Query DSL of the filter. The negative of this is that while it works, the filter on the dashboard doesn't visually show what value is being filtered on. Here is the encoded url for this workaround:


This sounds like a bug. Please file an issue at

Thank you. I have filed an issue at

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.