Clarify compatibility in upgrading stack document

Open
#185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
38/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Read the upgrading Elastic Stack document linked in the issue, then compare its compatibility wording with the referenced support matrix. Clarify the statement so the documented upgrade flexibility and the monitoring compatibility concern are not conflated; done means the document accurately explains the relevant compatibility limits.

Written by the indexing model from the issue text.

Description

When doing upgrade testing from 5.6.14 to 6.6.0 using this doc:
https://www.elastic.co/guide/en/elastic-stack/6.6/upgrading-elastic-stack.html

When ES/Kibana are upgraded to 6.6.0 and Logstash is still on 5.6.14. I was confused by the below statement, when I went to check monitoring for Logstash and it did not appear.

Beats and Logstash 5.6 are compatible with Elasticsearch 6.6.0 to give you flexibility in scheduling the upgrade

@ycombinator pointed me to this matrix to verify monitoring 5.6 is not compatible with 6.6.0

https://www.elastic.co/support/matrix#matrix_compatibility

Maybe we can clarify a bit in the upgrading elastic stack document too about that.

Dominant language
Java
Stars
105
Forks
249
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/stack-docs

All issues in elastic/stack-docs

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.