Skip to content

Commit 4f61784

Browse files
authored
Update docs/en/ingest-management/elastic-agent/configuration/outputs/output-logstash.asciidoc
1 parent 5f33df8 commit 4f61784

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

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

+4-5
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,10 @@ 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 the structure of the documents sent from Elastic Agent to {ls} must not be modified by the pipeline.
36-
We recommend 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
38-
in use to work correctly.
39-
We cannot guarantee that the {es} ingest pipelines associated to the integrations of {agent} can work with missing or modified fields.
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.
4039

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

0 commit comments

Comments
 (0)