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.

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

[8.17] [DOCS] Warn LS pipeline should not modify fields coming from EA (backport #1667) #1696

Merged
merged 1 commit into from
Feb 21, 2025
Merged

[8.17] [DOCS] Warn LS pipeline should not modify fields coming from EA (backport #1667) #1696

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
5 changes: 5 additions & 0 deletions .../ingest-management/elastic-agent/configuration/outputs/output-logstash.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,11 @@ To receive the events in {ls}, you also need to create a {ls} configuration pipe
The {ls} configuration pipeline listens for incoming {agent} connections,
processes received events, and then sends the events to {es}.

Please be aware that the structure of the documents sent from {agent} to {ls} must not be modified by the pipeline.
We recommend that the pipeline doesn’t edit or remove the fields and their contents.
Editing the structure of the documents coming from {agent} can prevent the {es} ingest pipelines associated to the integrations in use to work correctly.
We cannot guarantee that the {es} ingest pipelines associated to the integrations using {agent} can work with missing or modified fields.

The following {ls} pipeline definition example configures a pipeline that listens on port `5044` for
incoming {agent} connections and routes received events to {es}.

Expand Down