Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Better / improved instructions for APM Integration monitoring for on-premise #4726

Open
lucabelluccini opened this issue Nov 22, 2024 · 2 comments · May be fixed by #4749
Open

[DOCS] Better / improved instructions for APM Integration monitoring for on-premise #4726

lucabelluccini opened this issue Nov 22, 2024 · 2 comments · May be fixed by #4749
Assignees
Labels

Comments

@lucabelluccini
Copy link
Contributor

The page https://www.elastic.co/guide/en/observability/current/apm-monitor-apm-self-install.html#apm-configure-ea-monitoring-data

  1. We mention one can edit elastic-agent.yml and enroll Elastic Agent. This option is valid only if one has not yet enrolled Elastic Agent.
    If ones does so when they have already an enrolled agent, they might likely lose the state of Elastic Agent.

=> We need a banner/warning

  1. Since 8.15.0 onwards, Fleet UI is able to change the HTTP monitoring port of EA running a specific policy (https://www.elastic.co/guide/en/fleet/8.15/agent-policy.html#agent-policy-http-monitoring)

Image

=> I think this can be added to the documentation as it's way better for already enrolled agents (TO BE TESTED FIRST)

  1. The documentation mentions Metricbeat Beat X-Pack Module, including username and password, but there's no need here

Image

=> I would remove it and add a banner mentioning the endpoint is not protected.

@lucabelluccini lucabelluccini added the bug Something isn't working label Nov 22, 2024
@lucabelluccini
Copy link
Contributor Author

Hello @colleenmcginnis - IDK if this should be in the observability-docs or here.
You might need engineering review/input on one point above.

@colleenmcginnis
Copy link
Contributor

Thanks @lucabelluccini! (I'll add it to the observability docs board. We'll triage it there and decide whether or not to move it to observability-docs.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants