Kibana 4 is a complete rewrite from version 3 that we currently use. As part of this the format for dashboards is completely different and there are no migration scripts available. Devise a plan for how we can deal with this. See https://www.elastic.co/blog/recreating-kibana-3-dashboards-in-kibana-4
|Resolved||bd808||T137400 Logstash elasticsearch mapping does not allow err.code to be a string|
|Resolved||dcausse||T138608 Vagrant role provisions wrong elasticsearch version|
|Resolved||debt||T136001 [EPIC] Upgrade elasticsearch cluster supporting logging to 2.3|
|Resolved||EBernhardson||T139368 puppet failed on deployment-logstash2.deployment-prep|
|Resolved||EBernhardson||T138328 Upgrade kibana to 4.5.0+|
|Resolved||EBernhardson||T138333 Devise migration plan for kibana dashboards to version 4|
Even rebuilding the dashboards shouldn't be a horrible task. Most of the dashboards that are well advertised follow a common template. We might be able to figure out how to script a migration for our specific uses once we know what changes are needed. At some point in the distant past I played with Kibana4 by running it locally on my laptop with an ssh tunnel to get to the Elasticsearch cluster. I can make some time to try to set that up again and figure out what the dashboard config changes might look like.
After consideration, I don't think we are really going to have a migration plan. Will dump out the dashboards created on beta cluster and import them to prod, leaving the other dashboards to be recreated by the people that need them.