known issue for when an integration level output is set to default (#…

…1615) (#1621) * Add known issue for integration default output * Add known issue for default integration-level output * Update docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc Co-authored-by: Karen Metts <[email protected]> --------- Co-authored-by: Karen Metts <[email protected]> (cherry picked from commit ac7c195) Co-authored-by: David Kilfoyle <[email protected]>
elastic · Jan 10, 2025 · 05864cb · 05864cb
1 parent 4fcf6f2
commit 05864cb
Showing 1 changed file with 13 additions and 0 deletions.
diff --git a/docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc b/docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc
@@ -234,6 +234,19 @@ curl -XPOST -H 'Authorization: Bearer ${TOKEN}' -H 'x-elastic-product-origin:fle
 ----
 ====
 
+[discrete]
+[[known-issue-206131]]
+.Integration output fails when using default output
+[%collapsible]
+====
+*Details* +
+Beginning in version 8.16.0 you can specify an output per integration policy. However, setting the integration output to the default creates an invalid output name.
+
+*Impact* +
+As a workaround, you can create a clone of the default output and then set it as the output for an integration policy. Refer to issue link:https://github.com/elastic/kibana/issues/206131[#206131] for details and status.
+
+====
+
 [discrete]
 [[new-features-8.16.0]]
 === New features