Skip to content

Commit dda5bbf

Browse files
mergify[bot]zmoogkilfoyle
authored
Add ECS known issue for ecs@mappings and fieldless searches (#1330) (#1439)
* Add known issues about fieldless searches * Fix section IDs and cleanup * Add the known issue to 8.13.3 and 8.13.4 All 8.13.x releases are affected. * Update docs/en/ingest-management/release-notes/release-notes-8.13.asciidoc Co-authored-by: David Kilfoyle <[email protected]> * Apply suggestion from reviewers --------- Co-authored-by: David Kilfoyle <[email protected]> (cherry picked from commit f3e0dd1) Co-authored-by: Maurizio Branca <[email protected]> Co-authored-by: David Kilfoyle <[email protected]>
1 parent 277e29d commit dda5bbf

File tree

1 file changed

+93
-0
lines changed

1 file changed

+93
-0
lines changed

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

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,27 @@ Also see:
3232

3333
There are no bug fixes for {fleet} or {agent} in this release.
3434

35+
[discrete]
36+
[[known-issues-8.13.4]]
37+
=== Known issues
38+
39+
[[known-issue-174855-8.13.4]]
40+
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
41+
[%collapsible]
42+
====
43+
*Details*
44+
45+
Due to changes introduced to support the ecs@mappings component template (see link:https://github.com/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer includes ECS fields in the integrations' `index.query.default_field`. Not including ECS fields in the `index.query.default_field` setting may affect integrations that rely on fieldless queries (when no field is specified for a query).
46+
47+
If you run a query without specifying a field, the query will not return results for ECS fields.
48+
49+
*Impact* +
50+
51+
In version 8.14.0 and later, {fleet} sets `index.query.default_field` to `*`, so agentless queries will work as expected. We recommend users of {fleet} upgrade to 8.14 when that release becomes available.
52+
53+
If you are running 8.13.x and unable to upgrade to 8.14.0, you can follow the workarounds described in the link:https://support.elastic.co/knowledge/bbdbeb57.
54+
====
55+
3556
// end 8.13.4 relnotes
3657

3758
// begin 8.13.3 relnotes
@@ -48,6 +69,27 @@ Review important information about {fleet-server} and {agent} for the 8.13.3 rel
4869
{agent}::
4970
* Update Go version to 1.21.9. {agent-pull}4508[#4508]
5071

72+
[discrete]
73+
[[known-issues-8.13.3]]
74+
=== Known issues
75+
76+
[[known-issue-174855-8.13.3]]
77+
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
78+
[%collapsible]
79+
====
80+
*Details*
81+
82+
Due to changes introduced to support the ecs@mappings component template (see link:https://github.com/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer includes ECS fields in the integrations' `index.query.default_field`. Not including ECS fields in the `index.query.default_field` setting may affect integrations that rely on fieldless queries (when no field is specified for a query).
83+
84+
If you run a query without specifying a field, the query will not return results for ECS fields.
85+
86+
*Impact* +
87+
88+
In version 8.14.0 and later, {fleet} sets `index.query.default_field` to `*`, so agentless queries will work as expected. We recommend users of {fleet} upgrade to 8.14 when that release becomes available.
89+
90+
If you are running 8.13.x and unable to upgrade to 8.14.0, you can follow the workarounds described in the link:https://support.elastic.co/knowledge/bbdbeb57.
91+
====
92+
5193
[discrete]
5294
[[bug-fixes-8.13.3]]
5395
=== Bug fixes
@@ -90,6 +132,23 @@ This issue has been link:https://github.com/elastic/elastic-stack-installers/pul
90132
91133
====
92134

135+
[[known-issue-174855-8.13.2]]
136+
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
137+
[%collapsible]
138+
====
139+
*Details*
140+
141+
Due to changes introduced to support the ecs@mappings component template (see link:https://github.com/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer includes ECS fields in the integrations' `index.query.default_field`. Not including ECS fields in the `index.query.default_field` setting may affect integrations that rely on fieldless queries (when no field is specified for a query).
142+
143+
If you run a query without specifying a field, the query will not return results for ECS fields.
144+
145+
*Impact* +
146+
147+
In version 8.14.0 and later, {fleet} sets `index.query.default_field` to `*`, so agentless queries will work as expected. We recommend users of {fleet} upgrade to 8.14 when that release becomes available.
148+
149+
If you are running 8.13.x and unable to upgrade to 8.14.0, you can follow the workarounds described in the link:https://support.elastic.co/knowledge/bbdbeb57.
150+
====
151+
93152
[discrete]
94153
[[bug-fixes-8.13.2]]
95154
=== Bug fixes
@@ -127,6 +186,23 @@ This issue has been link:https://github.com/elastic/elastic-stack-installers/pul
127186
128187
====
129188

189+
[[known-issue-174855-8.13.1]]
190+
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
191+
[%collapsible]
192+
====
193+
*Details*
194+
195+
Due to changes introduced to support the ecs@mappings component template (see link:https://github.com/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer includes ECS fields in the integrations' `index.query.default_field`. Not including ECS fields in the `index.query.default_field` setting may affect integrations that rely on fieldless queries (when no field is specified for a query).
196+
197+
If you run a query without specifying a field, the query will not return results for ECS fields.
198+
199+
*Impact* +
200+
201+
In version 8.14.0 and later, {fleet} sets `index.query.default_field` to `*`, so agentless queries will work as expected. We recommend users of {fleet} upgrade to 8.14 when that release becomes available.
202+
203+
If you are running 8.13.x and unable to upgrade to 8.14.0, you can follow the workarounds described in the link:https://support.elastic.co/knowledge/bbdbeb57.
204+
====
205+
130206
[discrete]
131207
[[enhancements-8.13.1]]
132208
=== Enhancements
@@ -233,6 +309,23 @@ This issue has been link:https://github.com/elastic/elastic-stack-installers/pul
233309
234310
====
235311

312+
[[known-issue-174855-8.13.0]]
313+
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
314+
[%collapsible]
315+
====
316+
*Details*
317+
318+
Due to changes introduced to support the ecs@mappings component template (see link:https://github.com/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer includes ECS fields in the integrations' `index.query.default_field`. Not including ECS fields in the `index.query.default_field` setting may affect integrations that rely on fieldless queries (when no field is specified for a query).
319+
320+
If you run a query without specifying a field, the query will not return results for ECS fields.
321+
322+
*Impact* +
323+
324+
In version 8.14.0 and later, {fleet} sets `index.query.default_field` to `*`, so agentless queries will work as expected. We recommend users of {fleet} upgrade to 8.14 when that release becomes available.
325+
326+
If you are running 8.13.x and unable to upgrade to 8.14.0, you can follow the workarounds described in the link:https://support.elastic.co/knowledge/bbdbeb57.
327+
====
328+
236329
[discrete]
237330
[[new-features-8.13.0]]
238331
=== New features

0 commit comments

Comments
 (0)