Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add ECS known issue for ecs@mappings and fieldless searches #1330

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Add ECS known issue for ecs@mappings and fieldless searches #1330

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
19aa77a
Add known issues about fieldless searches
zmoog Sep 17, 2024
cffad2d
Fix section IDs and cleanup
zmoog Sep 17, 2024
9ebb272
Add the known issue to 8.13.3 and 8.13.4
zmoog Sep 17, 2024
0ffac84
Update docs/en/ingest-management/release-notes/release-notes-8.13.asc…
zmoog Sep 18, 2024
cc97bf4
Apply suggestion from reviewers
zmoog Sep 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
93 changes: 93 additions & 0 deletions docs/en/ingest-management/release-notes/release-notes-8.13.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,27 @@ Also see:

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

[discrete]
[[known-issues-8.13.4]]
=== Known issues

[[known-issue-174855-8.13.4]]
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
[%collapsible]
====
*Details*

Due to changes introduced to support the ecs@mappings component template (see link:https:/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer include ECS fields to 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).
zmoog marked this conversation as resolved.
Show resolved Hide resolved

If you run a query without specifying a field, the query will not return results for ECS fields.

*Impact* +

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.

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.
====

// end 8.13.4 relnotes

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

[discrete]
[[known-issues-8.13.3]]
=== Known issues

[[known-issue-174855-8.13.3]]
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
[%collapsible]
====
*Details*

Due to changes introduced to support the ecs@mappings component template (see link:https:/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer include ECS fields to 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).

If you run a query without specifying a field, the query will not return results for ECS fields.

*Impact* +

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.

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.
====

[discrete]
[[bug-fixes-8.13.3]]
=== Bug fixes
Expand Down Expand Up @@ -90,6 +132,23 @@ This issue has been link:https:/elastic/elastic-stack-installers/pul

====

[[known-issue-174855-8.13.2]]
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
[%collapsible]
====
*Details*

Due to changes introduced to support the ecs@mappings component template (see link:https:/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer include ECS fields to 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).

If you run a query without specifying a field, the query will not return results for ECS fields.

*Impact* +

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.

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.
====

[discrete]
[[bug-fixes-8.13.2]]
=== Bug fixes
Expand Down Expand Up @@ -127,6 +186,23 @@ This issue has been link:https:/elastic/elastic-stack-installers/pul

====

[[known-issue-174855-8.13.1]]
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
[%collapsible]
====
*Details*

Due to changes introduced to support the ecs@mappings component template (see link:https:/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer include ECS fields to 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).

If you run a query without specifying a field, the query will not return results for ECS fields.

*Impact* +

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.

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.
====

[discrete]
[[enhancements-8.13.1]]
=== Enhancements
Expand Down Expand Up @@ -233,6 +309,23 @@ This issue has been link:https:/elastic/elastic-stack-installers/pul

====

[[known-issue-174855-8.13.0]]
.ECS fields are not included to the `index.query.default_field` in {agent} integrations
[%collapsible]
====
*Details*

Due to changes introduced to support the ecs@mappings component template (see link:https:/elastic/kibana/pull/174855[elastic/kibana/pull/174855]), {fleet} no longer include ECS fields to 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).

If you run a query without specifying a field, the query will not return results for ECS fields.

*Impact* +

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.

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.
====

[discrete]
[[new-features-8.13.0]]
=== New features
Expand Down