[DOCS] Infrastructure monitoring section needs consistent and standard instructions for installing Elastic stack

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start with the linked Infrastructure Monitoring installation topic and compare its Elastic/Kibana and Beats instructions with the corresponding APM and Uptime content. Review the setup experience work mentioned in the issue, including the free cloud trial option; done means a single clear, consistent instruction set suitable for reuse across Observability products.

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

This is currently inconsistent with similar content in APM and Uptime, but I think both variants have good and bad points: both seemed good in parts and confusing in others.

It would be good to tie this section into the work that @debadair is doing on providing a clear and consistent set-up experience, and also to ensure that new users are presented with a prominent option to get started easily using a free cloud trial.

I've separated the Elastic and Kibana installation out from the Beats installation (also in this topic), because this part is common to all the Observability products. I think it should be possible to produce a single common set of instructions, which can then eventually be reused by all Observability products.

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.