elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.7k stars 8.12k forks source link

Change index on visualization/dashboard #3668

Closed hvisage closed 6 years ago

hvisage commented 9 years ago

Update on April 4th 2018 We really appreciate all of your feedback on this mega issue so far, but we need your help as we break this down into more concrete items to work on. Even if you've already +1'd this specific issue, it would be extremely helpful if you could +1 and describe your use case in the more granular issues that are provided below. We won't ignore all the feedback folks have provided so far in this issue, but more focused feedback on the individual feature proposals would be invaluable.

Here are the three sub issues that I believe make up this mega issue:

Changing index patterns on a visualization: #17542 Dashboard level index patterns: #16917 Improved export/import to include referenced objects. Then you can do a search/replace on an index pattern id in a single file: #16831 Nested dashboards: https://github.com/elastic/kibana/issues/16919

Dashboard level index patterns seems to match this initial request best and there is a currently available workaround for it, which is mentioned in https://github.com/elastic/kibana/issues/16917.

If those three issues do not cover your particular case, please let us know!


Original Issue Request:

I'm in a situation where I have the exact same dashboard and it's visualizations, but want it to use different aliases/indexes.

The idea would be to segregate different user's data/views, but each have the same view/dashboard (just his/her index/alias differs), especially as I read Shield does authorization/access control via aliases/indexes and that is what I need/want to use for the user authorization/access control then.

matt-softlogic commented 8 years ago

+1

steveblackmon commented 8 years ago

+1

alcamie101 commented 8 years ago

👍

fdufourd commented 8 years ago

+1

forzagreen commented 8 years ago

+1

vtipparam commented 8 years ago

+1

oxygenecore commented 8 years ago

+1

driperdk commented 7 years ago

+1

sumerjabri commented 7 years ago

+1

schickling commented 7 years ago

+1

sorenbs commented 7 years ago

OMG. This would be so useful!!!

sirhc-k commented 7 years ago

+1 - Kibana really needs to support reusable "assets."

fbaligand commented 7 years ago

+1

killthrush commented 7 years ago

+1

latos commented 7 years ago

+1111!!!1one

NightWuYo commented 7 years ago

+1

timtofan commented 7 years ago

+1

GreggBzz commented 7 years ago

+1 this would be great!

krismercado commented 7 years ago

+1 for this.

sebastianmonzel commented 7 years ago

+1

halucinka commented 7 years ago

+1

mrunalgosar commented 7 years ago

+1

bskim45 commented 7 years ago

+1

tullydwyer commented 7 years ago

+1

rezkam commented 7 years ago

+1

vincentpfarr commented 7 years ago

+1 ! Could be very useful

xandreklein commented 7 years ago

+1

edgarshurtado commented 7 years ago

+1

jenmo917 commented 7 years ago

+1

rohits-dev commented 7 years ago

+1

maniankara commented 7 years ago

+1 I thought this was already possible :(

wosho commented 7 years ago

+1

This is def. a must have. Please make it happen.

Arieltk1 commented 7 years ago

+1

avindsilva commented 7 years ago

+1

M2UNO3 commented 7 years ago

+1

ghost commented 7 years ago

Will a requested feature exist after 2 years? Who knows! +1

neilc2016 commented 7 years ago

+1

dongshengmu commented 7 years ago

+1

xycloud commented 7 years ago

+1

taylorstine commented 7 years ago

+1

maniankara commented 7 years ago

+1

charliejllewellyn commented 7 years ago

+1

kenliao94 commented 7 years ago

+1

sorinescu commented 7 years ago

+1

nbelakovski commented 7 years ago

+1

GautamP7 commented 7 years ago

+1

fanwu72 commented 7 years ago

+100000000000

kmokrzycki commented 7 years ago

+1

89berner commented 7 years ago

+1

AndreAga commented 7 years ago

+1