[Ingest Manager] Enrollment Flyout text corrections to cite correct binary path and to use Administrator rights
Kibana version:
7.9 BC5 deployed to elastic cloud prod
Describe the bug:
the enrollment flyout doesn't cite to use Administrator access, due to this incorrect usage happened a lot during an internal dog-fooding test and we expect customer / user usage to follow suit. we should call this out in the flyout if possible, instead of leaving it to docs. secondly, the .rpm/.deb instructions are mis-leading indicating a binary path that doesn't exist
Steps to reproduce:
- install stack of 7.9, BC latest
- to to ingest manager and enable Fleet user
- click on the 'enroll new agent' flyout and see text.
- it was recently updated and is massively improved, but can be tweaked a bit more.
Expected behavior:
the instructions are sufficient to enroll Agent and it set up with elastic solutions pieces (Endpoint Security)
The 2 suggestions I suggest we make are:
- to remove the ./ from the .rpm/.deb section for Linux. This is because the service executable can be used, and after install, there is no local binary to call in that location so it doesn't work.
for example, instead of citing this:
./elastic-agent enroll https://8a4af220da674c2287033be796421b1b.europe-west1.gcp.cloud.es.io:443 V1VpTm4zTUI5WjU5ZUl5X2tlWkY6NjBrSUk4TkpUQ3VvVU5odGdQMUpudw==
it would cite:
elastic-agent enroll https://8a4af220da674c2287033be796421b1b.europe-west1.gcp.cloud.es.io:443 V1VpTm4zTUI5WjU5ZUl5X2tlWkY6NjBrSUk4TkpUQ3VvVU5odGdQMUpudw==
- add this text to the step 3 after the current text to cite Administator privilege is required.
for example, from this:
From the agent’s directory, run the appropriate commands to enroll and start an Elastic Agent. You can reuse these commands to setup agents on more than one machine.
to:
From the agent’s directory, run the appropriate commands to enroll and start an Elastic Agent. You can reuse these commands to setup agents on more than one machine. Be sure to run the enrollment steps as a user with Administrator privilege on the system.
Screenshots (if relevant):
[Ingest Manager] Enrollment Flyout text corrections to cite correct binary path and to use Administrator rights
Kibana version:
7.9 BC5 deployed to elastic cloud prod
Describe the bug:
the enrollment flyout doesn't cite to use Administrator access, due to this incorrect usage happened a lot during an internal dog-fooding test and we expect customer / user usage to follow suit. we should call this out in the flyout if possible, instead of leaving it to docs. secondly, the .rpm/.deb instructions are mis-leading indicating a binary path that doesn't exist
Steps to reproduce:
Expected behavior:
the instructions are sufficient to enroll Agent and it set up with elastic solutions pieces (Endpoint Security)
The 2 suggestions I suggest we make are:
for example, instead of citing this:
./elastic-agent enroll https://8a4af220da674c2287033be796421b1b.europe-west1.gcp.cloud.es.io:443 V1VpTm4zTUI5WjU5ZUl5X2tlWkY6NjBrSUk4TkpUQ3VvVU5odGdQMUpudw==
it would cite:
elastic-agent enroll https://8a4af220da674c2287033be796421b1b.europe-west1.gcp.cloud.es.io:443 V1VpTm4zTUI5WjU5ZUl5X2tlWkY6NjBrSUk4TkpUQ3VvVU5odGdQMUpudw==
for example, from this:
From the agent’s directory, run the appropriate commands to enroll and start an Elastic Agent. You can reuse these commands to setup agents on more than one machine.
to:
From the agent’s directory, run the appropriate commands to enroll and start an Elastic Agent. You can reuse these commands to setup agents on more than one machine. Be sure to run the enrollment steps as a user with Administrator privilege on the system.
Screenshots (if relevant):
