Add docs for integrations-level outputs (#1218)

* Add docs for integrations-level outputs

* Add content

* touchup

* touchup

* touchup

* Update docs/en/ingest-management/integrations/integration-level-outputs.asciidoc

Co-authored-by: Karen Metts <[email protected]>

---------

Co-authored-by: Karen Metts <[email protected]>

Author: kilfoyle

docs/en/ingest-management/fleet/fleet-settings.asciidoc

@@ -67,6 +67,9 @@ are updated automatically.
 Add or edit output settings to specify where {agent}s send data. {agent}s
 use the default output if you don't select an output in the agent policy.
 
+TIP: If you have an `Enterprise` link:https://www.elastic.co/subscriptions[{stack} subscription],
+you can configure {agent} to
+<<integration-level-outputs,send data to different outputs for different integration policies>>.
 
 NOTE: The {ecloud} internal output is locked and cannot be edited. This
 output is used for internal routing to reduce external network charges when

docs/en/ingest-management/index.asciidoc

@@ -199,6 +199,8 @@ include::integrations/install-integration-assets.asciidoc[leveloffset=+2]
 
 include::integrations/view-integration-assets.asciidoc[leveloffset=+2]
 
+include::integrations/integration-level-outputs.asciidoc[leveloffset=+2]
+
 include::integrations/upgrade-integration.asciidoc[leveloffset=+2]
 
 include::integrations/managed-integrations-content.asciidoc[leveloffset=+2]

docs/en/ingest-management/integrations/integration-level-outputs.asciidoc

@@ -0,0 +1,46 @@
+[[integration-level-outputs]]
+= Set integration-level outputs
+
+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.
+
+[discrete]
+== Order of precedence
+
+For each {agent}, the agent policy configures sending data to the following outputs in decreasing order of priority:
+
+. The output set in the <<add-integration-to-policy,integration policy>>.
+. The output set in the integration's parent <<agent-policy,{agent} policy>>.
+This includes the case where an integration policy belongs to multiple {agent} policies.
+. The global, default data output set in the <<fleet-settings,{fleet} settings>>.
+
+[discrete]
+== Configure the output for an integration policy
+
+To configure an integration-level output for {agent} data:
+
+. In {kib}, go to **Integrations**.
+. On the **Installed integrations** tab, select the integration that you'd like to update.
+. Open the **Integration policies** tab.
+. From the **Actions** menu next to the integration, select *Edit integration*.
+. In the **integration settings** section, expand **Advanced options**.
+. Use the **Output** dropdown menu to select an output specific to this integration policy.
+. Click **Save and continue** to confirm your changes.
+
+[discrete]
+== View the output configured for an integration
+
+To view which {agent} output is set for an integration policy:
+
+. In {fleet}, open the **Agent policies** tab.
+. Select an {agent} policy.
+. On the **Integrations** tab, the **Output** column indicates the output used for each integration policy.
+If data is configured to be sent to either the global output defined in {fleet} settings or to the integration's parent {agent} policy, this is indicated in a tooltip.
+
+
+
+