Skip to content

Commit

Permalink
Add docs for integrations-level outputs
Browse files Browse the repository at this point in the history
  • Loading branch information
kilfoyle committed Aug 2, 2024
1 parent 7632880 commit 6f5020a
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 0 deletions.
12 changes: 12 additions & 0 deletions docs/en/ingest-management/fleet/fleet-integration-outputs.asciidoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
:type: output-elasticsearch-fleet-settings

[[fleet-integration-outputs]]
= Setting outputs per integration

If you have an `Enterprise` link:https://www.elastic.co/subscriptions[{stack} subscription], you can configure {agent} data to be sent to different outputs for different integration policies. Integration-level outputs are very useful for certain scenarios. For example:

* You can may want to send security logs monitored by an {agent} to one {ls} output, while informational logs are sent to a another {ls} output.
* If you operate multiple {beats} on a system and want to migrate these to {agent}, integration-level outputs enable you to maintain the distinct outputs that are currently used by each Beat.


Order of precedence...
2 changes: 2 additions & 0 deletions docs/en/ingest-management/index.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,8 @@ include::fleet/fleet-settings-output-kafka.asciidoc[leveloffset=+3]

include::fleet/fleet-settings-remote-elasticsearch.asciidoc[leveloffset=+3]

include::fleet/fleet-integration-outputs.asciidoc[leveloffset=+3]

include::fleet/fleet-settings-changing-outputs.asciidoc[leveloffset=+3]

include::fleet/fleet-manage-agents.asciidoc[leveloffset=+2]
Expand Down

0 comments on commit 6f5020a

Please sign in to comment.