Skip to content
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

Ability to change the index pattern on a visualization #17542

Open
stacey-gammon opened this issue Apr 4, 2018 · 19 comments

Comments

@stacey-gammon
Copy link
Contributor

@stacey-gammon stacey-gammon commented Apr 4, 2018

Similar to how discover does it. Rather than requiring a new visualization to be built, add a field when editing a visualization that lets you change the index pattern on it. We need to figure out how to handle errors when a visualization was built with fields from the original index that don't exist in the new one.

Splitting this particular part out of this issue: #3668 which includes both dashboards and visualizations. Changing the index pattern on a dashboard is a much different problem and is now covered by this issue: #16917

It will be helpful for us to split these issues out and see which are the most important to the community.

also related: #16831

@ReanimationXP

This comment has been minimized.

Copy link

@ReanimationXP ReanimationXP commented Apr 9, 2018

I believe the visualization index pattern can already be changed manually by changing its' index guid, but it's extremely non user-friendly considering the compounding issues of (a) those index pattern guids are conveniently not available in the object manager / browser, (b) there is no simple dropdown to change it from within the visualization itself, and perhaps most importantly (c) there is no way to bulk-change multiple visualizations.

@conmurray

This comment has been minimized.

Copy link

@conmurray conmurray commented May 29, 2018

I'll add my request here as well. Im a GOLD licence and Ill raise this with my support engineer but I wanted to pop it here aswell.

  • User created a visualization against an index called "logstash_test_metrics"
  • We then deleted "logstash_test_metrics" and the index pattern for it aswell.
  • We needed to modify the logstash conf file and so re ran the logstash conf file to re-add the logstash_test_metrics index
  • We then created the index pattern for this "logstash_test_metrics"
  • We'd go to the visualization to be told the underlying index is not there. Actually, it is but because the kibanaSavedObjectMeta.searchSourceJSON now references the index by an ID and not by the actual index name, everything is broken. I have to either recreate the visualization or I have to find the ID for the new index and copy it into the kibanaSavedObjectMeta.searchSourceJSON. This isnt really feasible when I've a LOT of visualizations that all reference the same index.
@conmurray

This comment has been minimized.

Copy link

@conmurray conmurray commented Jun 7, 2018

Why was this closed? Also the Switch Index on Visualization is also closed so what's the story here? I've referenced this in my Internal Elastic Support case as well.

@stacey-gammon

This comment has been minimized.

Copy link
Contributor Author

@stacey-gammon stacey-gammon commented Jun 7, 2018

This issue isn't closed @conmurray. Switch Index on Visualization was closed because it's a duplicate of this one. Am I overlooking something else?

Regarding your use case above, it almost seems like #16831 is a better fit for it. Just being able to change the index pattern on one visualization in the UI would still require you to open each visualization and change it. If we had an export API that included linked objects you would be able to open the file, do a bulk find/replace, then re-import the file.

@conmurray

This comment has been minimized.

Copy link

@conmurray conmurray commented Jun 7, 2018

Ah yes I see that. Thanks... @stacey-gammon
With respect to #16831 it doesnt seem to support my particular use case. The fact that you're using ID and not the actual index name is the problem here. Ill add this to the #16831

@PritomAhmed

This comment has been minimized.

Copy link

@PritomAhmed PritomAhmed commented Aug 16, 2018

+1

2 similar comments
@Razikus

This comment has been minimized.

Copy link

@Razikus Razikus commented Aug 24, 2018

+1

@xingfanxia

This comment has been minimized.

Copy link

@xingfanxia xingfanxia commented Sep 11, 2018

+1

@lambdamusic

This comment has been minimized.

Copy link

@lambdamusic lambdamusic commented Sep 20, 2018

+1
As a side note, I noticed the the index ID in the kibanaSavedObjectMeta does not match any of the indexes I have in elasticsearch. Looks like the ID is created by Kibana when an 'index pattern' gets generated.
Is that right? If so how what's the best way to resolve these mappings?

@yami12376

This comment has been minimized.

Copy link

@yami12376 yami12376 commented May 23, 2019

+1

@smerzlyakov

This comment has been minimized.

Copy link

@smerzlyakov smerzlyakov commented Jun 21, 2019

+1 really need this feature. Or even manually change index pattern.

@nerophon

This comment has been minimized.

Copy link

@nerophon nerophon commented Jun 28, 2019

+1

@canturkisci

This comment has been minimized.

Copy link

@canturkisci canturkisci commented Jul 18, 2019

+1 on this please! This is tedious to recover when we have repeat deploys and many dashboards stop working due to the mismatch in index patterns. Intuitively we should be able to point a visualization to an index pattern name, and say "try this instead".

@louieamone

This comment has been minimized.

Copy link

@louieamone louieamone commented Jul 22, 2019

+1. It would be really great to have a more intuitive and efficient way to do this!

@duffar12

This comment has been minimized.

Copy link

@duffar12 duffar12 commented Aug 29, 2019

+1

@aviadbi1

This comment has been minimized.

Copy link

@aviadbi1 aviadbi1 commented Sep 2, 2019

+1

3 similar comments
@r33bl

This comment has been minimized.

Copy link

@r33bl r33bl commented Sep 17, 2019

+1

@rajesh212

This comment has been minimized.

Copy link

@rajesh212 rajesh212 commented Oct 14, 2019

+1

@ranjitmw

This comment has been minimized.

Copy link

@ranjitmw ranjitmw commented Oct 14, 2019

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.