Skip to content

Fleetserver connectivity requirments when using an elasticsearch remote output #4244

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.

Sign up for GitHub

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

Open
mjmbischoff wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fleetserver connectivity requirments when using an elasticsearch remote output #4244

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion reference/fleet/remote-elasticsearch-output.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,4 +117,6 @@
When you use a remote {{es}} output, {{fleet-server}} performs a test to ensure connectivity to the remote cluster. The result of that connectivity test is used to report whether the remote output is healthy or unhealthy, and is displayed on the **{{fleet}}** → **Settings** → **Outputs** page, in the **Status** column.

In some cases, the remote {{es}} output used for {{agent}} data can be reached by the {{agent}}s but not by {{fleet-server}}. In those cases, you can ignore the resulting unhealthy state of the output and the associated `Unable to connect` error on the UI.
::::

In addition the fleetserver will also reach out to the remote cluster user the service token to generate APIKeys. This means for agents calling into the this fleetserver that should connect to the remote elasticsearch, have a hard requirement to allow the fleetserver to reach the remote elasticsearch cluster.

Check notice on line 121 in reference/fleet/remote-elasticsearch-output.md

View workflow job for this annotation

GitHub Actions / vale 

Elastic.FutureTense: 'will also' might be in future tense. Write in the present tense to describe the state of the product as it is now.

Check notice on line 121 in reference/fleet/remote-elasticsearch-output.md

View workflow job for this annotation

GitHub Actions / vale 

Elastic.Wordiness: Consider using 'also' instead of 'In addition'.
::::
Loading