From 10b2883148fbc4eca2b76fba89af5c83a279052b Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Fri, 10 Jan 2025 15:18:38 -0500 Subject: [PATCH] known issue for when an integration level output is set to default (#1615) * 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 <35154725+karenzone@users.noreply.github.com> --------- Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com> (cherry picked from commit ac7c195dc6e6c1f963aecef7d2179976b17fb227) --- .../release-notes/release-notes-8.16.asciidoc | 13 +++++++++++++ 1 file changed, 13 insertions(+) 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 index eaa2647bb..7f53f2980 100644 --- a/docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc +++ b/docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc @@ -240,6 +240,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