Skip to content

Commit 67b04cf

Browse files
lucabelluccinikilfoyle
authored andcommitted
[DOCS] Warn LS pipeline should not modify fields coming from EA (#1667)
* [DOCS] Warn LS pipeline should not modify fields coming from EA Warn LS pipeline should not modify fields coming from EA Modifying data coming from EA can prevent the ingest pipelines on Elasticsearch side associated to the integrations in use in EA to work correctly. * Update docs/en/ingest-management/elastic-agent/configuration/outputs/output-logstash.asciidoc --------- Co-authored-by: David Kilfoyle <[email protected]> (cherry picked from commit e37bb56)
1 parent 3494f4e commit 67b04cf

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

docs/en/ingest-management/elastic-agent/configuration/outputs/output-logstash.asciidoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,11 @@ To receive the events in {ls}, you also need to create a {ls} configuration pipe
3232
The {ls} configuration pipeline listens for incoming {agent} connections,
3333
processes received events, and then sends the events to {es}.
3434

35+
Please be aware that the structure of the documents sent from {agent} to {ls} must not be modified by the pipeline.
36+
We recommend that the pipeline doesn’t edit or remove the fields and their contents.
37+
Editing the structure of the documents coming from {agent} can prevent the {es} ingest pipelines associated to the integrations in use to work correctly.
38+
We cannot guarantee that the {es} ingest pipelines associated to the integrations using {agent} can work with missing or modified fields.
39+
3540
The following {ls} pipeline definition example configures a pipeline that listens on port `5044` for
3641
incoming {agent} connections and routes received events to {es}.
3742

0 commit comments

Comments
 (0)