Clarify Fleet Server connectivity requirement in the “Remote Elasticsearch output” doc#5108
Clarify Fleet Server connectivity requirement in the “Remote Elasticsearch output” doc#5108vishaangelova wants to merge 2 commits intomainfrom
Conversation
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🔍 Preview links for changed docs |
|
|
||
| ::::{note} | ||
| 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. | ||
| ## Remote output health status [remote-output-health-status] |
There was a problem hiding this comment.
@blakerouse could you please verify the statements in this section? Thanks!
- Clarified the Fleet Server to remote cluster connectivity requirement - Added step for configuring SSL CA - Updated stepper to use step titles
vishaangelova
force-pushed
the
4026-clarify-remote-es-output
branch
from
ecf55f6 to
8823f2e
Compare
| These limitations apply to remote {{es}} output: | ||
|
|
||
| * {{fleet-server}} must be able to reach the remote {{es}} cluster with a service token to create API keys for any {{agents}} that use the remote {{es}} output. | ||
| * {{fleet-server}} must be able to reach the remote {{es}} cluster with a service token to generate API keys for the {{agents}} that use the remote output for data ingestion. |
There was a problem hiding this comment.
@blakerouse could you please verify this statement? Thanks!
There was a problem hiding this comment.
Would it make sense to say At least one {{fleet-server}}... in order to make it aligned with the note we have at the end of the doc?
Anyway feel free to ignore it, it also feels good in the way it is. Just for your consideration.
There was a problem hiding this comment.
I’ve updated this with your suggestion in 221ead4
vishaangelova
force-pushed
the
4026-clarify-remote-es-output
branch
from
8ad09e1 to
221ead4
Compare
2 participants
Summary
This PR:
applies_tofor a feature configuration, and removes incorrect use ofserverlessin an in-lineapplies_to(remote ES output is not available in Serverless)Resolves #4026
Preview
reference/fleet/remote-elasticsearch-output.md
Generative AI disclosure
Tool(s) and model(s) used: Cursor 2.4.31 with claude-4.5-sonnet