Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Document remote monitoring cluster version requirement for upgrades?

Open
#35 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the monitoring production guide at the linked version-dependency section, then locate the stack upgrade documentation referenced in the issue. Document or cross-link the requirement that exports cannot move from a 6.x cluster to a 5.x monitoring cluster, and confirm the upgrade guidance makes this visible to users.

Written by the indexing model from the issue text.

Description

We have a note here on version dependency, i.e. they can't do an export from a 6.x cluster to a 5.x monitoring cluster during upgrades: https://www.elastic.co/guide/en/x-pack/current/monitoring-production.html#monitoring-production

The problem is that this note is in the "setup" section of the monitoring guide and users are unlikely going to revisit this page as part of the upgrade. It will be helpful if we can call this out (or cross link) as part of the stack upgrade documentation.

Dominant language
Java
Stars
105
Forks
249
PR merge metrics
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.