Fix standalone agent access for agent-driven monitoring (#17386)

* Fix standalone agent access for agent-driven monitoring

Change incorrect dedicated instructions, and base them on those from running Elastic Agent
in standalone mode.


---------

Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com>
This commit is contained in:
Rob Bavey 2025-04-01 14:50:14 -04:00 committed by GitHub
parent 7913f91340
commit 5a052b33f9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 15 additions and 4 deletions

View file

@ -39,10 +39,16 @@ monitoring.cluster_uuid: PRODUCTION_ES_CLUSTER_UUID
::::
::::{dropdown} Create a monitoring user (standalone agent only)
::::{dropdown} Grant agent access to Elasticsearch (standalone agent only)
:name: create-user-db
Create a user on the production cluster that has the `remote_monitoring_collector` [built-in role](elasticsearch://reference/elasticsearch/roles.md).
Minimal permissions required to send Logstash monitoring data to Elasticsearch:
* `monitor` cluster privilege
* `auto_configure` and `create_doc` index privileges on `logs-*` and `metrics-*` indices.
See [Grant standalone Elastic Agents access to Elasticsearch](docs-content://reference/fleet/grant-access-to-elasticsearch.md)
::::

View file

@ -47,10 +47,15 @@ monitoring.cluster_uuid: PRODUCTION_ES_CLUSTER_UUID
::::
::::{dropdown} Create a monitoring user (standalone agent only)
::::{dropdown} Grant agent access to Elasticsearch (standalone agent only)
:name: create-user-ea
Create a user on the production cluster that has the `remote_monitoring_collector` [built-in role](elasticsearch://reference/elasticsearch/roles.md).
Minimal permissions required to send Logstash monitoring data to Elasticsearch:
* `monitor` cluster privilege
* `auto_configure` and `create_doc` index privileges on `logs-*` and `metrics-*` indices.
See [Grant standalone Elastic Agents access to Elasticsearch](docs-content://reference/fleet/grant-access-to-elasticsearch.md)
::::