Skip to content

Update integration-level-outputs.md #1477

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

Merged
merged 2 commits into from
May 27, 2025
Merged

Update integration-level-outputs.md #1477

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1f1f47e
Update integration-level-outputs.md
jamie-wilson88 May 23, 2025
a8017f9
Merge branch 'main' into jamie-wilson88-patch-1
colleenmcginnis May 27, 2025
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
2 changes: 1 addition & 1 deletion reference/fleet/integration-level-outputs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ If you have an `Enterprise` [{{stack}} subscription](https://www.elastic.co/subs

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.
* You may want to send security logs monitored by an {{agent}} to one {{ls}} output, while informational logs are sent to 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.


Expand Down
Loading