[DOCS] infrastructure monitoring section needs clearer instructions for installing and configuring required Beats

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation, infrastructure, observability-sre

Research direction

Start with the install-infrastructure-monitoring.html topic and compare its direct Beats instructions with the in-app Kibana instructions it references. Review the current installation and configuration flow and the noted Infrastructure/Logs separation and modules work; done means identifying what can be clarified now, testing those instructions, and distinguishing deferred changes.

Written by the indexing model from the issue text.

Description

Infrastructure monitoring

Topic https://www.elastic.co/guide/en/infrastructure/guide/current/install-infrastructure-monitoring.html

The instructions for installing and configuring Beats need clarifying, testing and checking. In particular, I think there is some overlap between the in-app instructions in Kibana (which is one of the options mentioned here), and the direct instructions here, which could cause confusion for some readers.

Any work carried out in this area should probably bear in mind the imminent separation of Infrastructure and Logs content, but also the changes likely to occur as a result of the integrations work, which may bring parts of this together again?

As part of working on this issue, I'd like to better understand the current installation and configuration, and the changes likely as a result of the modules work. Then it will be possible to decide what is sensible to fix now, to improve the current user experience, and what should wait until later.

@Titch990

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.