[Docs] Add dashboard upgrade info #5027
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dedemorton
added
help wanted
tsg
reviewed
Aug 28, 2017
|
|
||
| However, if you have Beats 5.5 dashboards and plan to use them with Kibana 6.0, | ||
| you need to import them into 5.6 now by using the Kibana API, or they will no | ||
| longer work in Kibana 6.0. |
There was a problem hiding this comment.
I don't think this is true. Kibana automatically upgrades any dashboards that work in 5.6, so as long as the user follows the normal upgrade sequence, there shouldn't be any need for extra instructions.
|
@tsg So should I close this PR? |
|
yes, let's close this one in favor of #5068 |
dedemorton
removed
the
needs_backport
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@monicasarbu I'm pretty sure that some of these details are wrong (especially around what to do with the 5.5 dashboards to get them into 5.6). I assume this info is for end-users, so we wouldn't expect them to use devtools.
Anyhow, this is my understanding of the upgrade process based on our discussion, but I think there's some missing content here.