Add a note about saved object migrations to the kibana setup docs#23251
Add a note about saved object migrations to the kibana setup docs#23251chrisdavies wants to merge 2 commits intoelastic:masterfrom
Conversation
| @@ -0,0 +1,16 @@ | |||
| [[migrations]] | |||
| == Kibana index migrations | |||
There was a problem hiding this comment.
I think we should call this "saved object migrations" instead, to better distance itself from things like generic index management/reindex. Thoughts?
There was a problem hiding this comment.
Yep. I think that's a valid point.
There was a problem hiding this comment.
Hm. How about "saved object index migrations"? The reason being, "Only one server will perform saved object migrations." is an incorrect statement, but "Only one server will perform saved object index migrations." is correct.
|
Thanks for creating this so quickly. I want to give this some more thought before we press forward with a merge. It's all good information that I do want to document, but I want to do so in a way that makes it easiest for folks to consume without making them feel like every upgrade of Kibana is super risky. |
💚 Build Succeeded |
|
Regarding the "risky" sound of things, I think this paragraph in particular could use some work. I'll wait for your feedback before tweaking, though!
|
|
One other thing. It's hard to know what Kibana index you should point the |
💔 Build Failed |
|
@epixa sounds like this is not going into 6.5. Should we clean up version labels? |
|
@rayafratkina Docs changes can happen at any time and are not bound by feature freeze. Since this feature is going out in 6.5, it makes sense to backport it to 6.5 docs. |
|
Closing in favor of #25558 |
This PR adds a note about index migrations to the Kibana setup docs. The target for this doc is probably someone in the sys admin role. The goal is to give them a heads up about new log messages they may see when booting up Kibana, and to set some expectations about some edge cases.
I'm not sure exactly how detailed we should get here.