-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Lens] Accept filter definition via URL query parameters #97249
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
@ghudgins I think this is actually a bug, it has been possible in the past to pass in filters from the URL into Lens. It is also possible for other apps to construct Lens URLs using the One of the things that is has never been possible to add via URL is the KQL/Lucene query as text- although it's possible to add via the LensComponent. |
As discussed offline, right now only pinned filters and the time range can be synced via URL. Adding query/regular filters to this (maybe even the full state) would be an interesting extension. |
Sorry, I confused myself. The only filters that are typically passed in the URL today are Pinned Filters, which are passed in using the global state The existing behavior is that if I pin a filter from Discover and then open Lens, I will see a URL like this. Only pinned filters are kept.
The proposed change here is to add |
This is possible now with the new Share capabilities of Lens. You can share a url containing filters and the context will be passed to the new window |
@stratoula Where is the share in lens? I'm not seeing it like I do when I'm using |
Describe the feature:
Allow chart filter information to be passed into Lens via URL query parameter
Today there is a local/session storage for this information but you cannot generate this from another application outside of Kibana
Describe a specific use case for the feature:
When designing a custom application
I would like to construct a link into Lens carrying the current query context from my application
So I can lean on Kibana's functionality for data exploration rather than building it myself
The text was updated successfully, but these errors were encountered: