Search visualization list by index

[AlonaNadler]

When going into saved visualization list currently there is no way to identify which index the saved visualization is using.
Customer is asking to add another field to the saved visualization list (and for saved searches) that shows which index was used to create the visualization and allow to search by index name and get all the visualizations which use this index

[deanpeters]

Would this request be similar or related to that of #16747 ?

In that request, I think they're asking for the search driving a visualization. Am I correct that this request differs in that the ask for for the index behind the visualization (and not necessarily the search)?

If so, it makes me wonder where I might find what metadata is captured for a specific visualization, and if there is not a way to surface it so we don't spin up one story for the index, another for the search, and perhaps others on authors, modified date, etc ...

... usually the type of stuff important to those working in highly regulated situations where they need to keep audit trails on what got changed by whom and when and to which version and so forth.

[AlonaNadler]

Hi @deanpeters both issues are around the object metadata, but they are different.
I agree we need more metadata for Kibana objects which can include index pattern, saved search, who created the object, when was it last modify etc..

[timroes]

Intent Discuss: We need to figure out if we actually want to have this, since we have a couple of visualizations that can use multiple index patterns (like Vega, TSVB, Timelion) and don't expose them (and it also would be rather hard to expose them, since they don't even need to use index patterns at all). Also we would like to have better templating functionality in the future where a visualization might not even have a single index pattern at all anymore unless used in a specific dashboard. Also using the pipeline later on, a visualization can have an arbitrary amount of index patterns, and we to get that information we would need to make the expression language more complex, so that every function registered need to inform us which of it parameters might be an index pattern... and even then: just because an index pattern is used inside the expression, doesn't mean, that it even is presented in the chart at all.

That's why I would rather suggest we're not building filtering by index pattern, but rather rely on Spaces, Saved Object tagging (#16484) and improving the search itself, to achieve better (and technical stable!) discoverability of saved visualizations.

[AlonaNadler]

We have this capability starting from 6.4 in the saved object page, it is possible to select an index pattern relationship and see all objects in relationship with this object

I think we can close this