While you can technically add filters to a URL today, it's not implemented in a simplistic fashion. Ideally, it would be great if we could expand on the type of work done for navigating to a dashboard by the title of a dashboard (https://github.com/elastic/kibana/pull/14760).
For instance, my dashboard URL is http://localhost:5610/app/kibana#/dashboard/edf84fe0-e1a0-11e7-b6d5-4dc382ef7f5b
If I wanted to say filter on windows and osx operating systems, it would be nice to be able to create URL's like the one below
http://localhost:5610/app/kibana#/dashboard/edf84fe0-e1a0-11e7-b6d5-4dc382ef7f5b?filter=machine.os:windows,osx
With support for multiple filters
http://localhost:5610/app/kibana#/dashboard/edf84fe0-e1a0-11e7-b6d5-4dc382ef7f5b?filter=machine.os:windows,osx&filter=geo.src:US
Any syntax would work, and we'd likely need to support operators like >,>=, =,<,<= and anything else I haven't thought of.
I imagine we'll need similar functionality to support custom panel actions in the future. Other applications such as ML could utilize this internally for their custom URL builder UI.
This is somewhat related to https://github.com/elastic/kibana/issues/13061
cc: @elastic/kibana-sharing @elastic/kibana-platform
馃憤 This would be very beneficial for the ML custom URL builder, where currently we are passing any entities from an anomaly into the query section of the URL due to the complexity of getting them into the (preferred) filters section, overwriting any query the user may have set on the dashboard.
Most helpful comment
馃憤 This would be very beneficial for the ML custom URL builder, where currently we are passing any entities from an anomaly into the query section of the URL due to the complexity of getting them into the (preferred) filters section, overwriting any query the user may have set on the dashboard.