Skip to content

Commit 72f6ed7

Browse files
known issue for when an integration level output is set to default (#1615) (#1620)
* 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]>
1 parent cda9dce commit 72f6ed7

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

docs/en/ingest-management/release-notes/release-notes-8.16.asciidoc

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -240,6 +240,19 @@ curl -XPOST -H 'Authorization: Bearer ${TOKEN}' -H 'x-elastic-product-origin:fle
240240
----
241241
====
242242

243+
[discrete]
244+
[[known-issue-206131]]
245+
.Integration output fails when using default output
246+
[%collapsible]
247+
====
248+
*Details* +
249+
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.
250+
251+
*Impact* +
252+
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.
253+
254+
====
255+
243256
[discrete]
244257
[[new-features-8.16.0]]
245258
=== New features

0 commit comments

Comments
 (0)