Add support for flattened fields with ignore_above in mappings#238890
Merged
teresaromero merged 2 commits intoelastic:mainfrom Oct 17, 2025
Merged
Add support for flattened fields with ignore_above in mappings#238890teresaromero merged 2 commits intoelastic:mainfrom
teresaromero merged 2 commits intoelastic:mainfrom
Conversation
botelastic
Bot
added
the
Team:Fleet
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
teresaromero
added
release_note:skip
Contributor
Author
|
@elasticmachine merge upstream |
jsoriano
approved these changes
Oct 16, 2025
Member
jsoriano
left a comment
jsoriano
left a comment
There was a problem hiding this comment.
LGTM, as this is a bugfix, I think it could be backported to 9.2.
teresaromero
added
release_note:fix
backport:version
Contributor
💛 Build succeeded, but was flaky
Failed CI Steps
Test Failures
Metrics [docs]
History
|
Contributor
|
Starting backport for target branches: 9.2 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Oct 17, 2025
…ic#238890) ## Summary Fix elastic#223245 Fields of type `flattened` where being mapped as default. This did not include `ignore_above` field. This PR fixes the mapping and includes `ignore_above` field if exists. If the field is not present, it does not use a default value. Testing done: - unit test case for `generateMappings` function - manual testing installing the reported integration and checking the field is now being mapped. using `crowdstrike` integration and adding `ignore_above` to the [flattened field](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689). once installed, add the integration to an agent policy and verify the mapping has included the given field ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Fixes `ignore_above` mapping for `flattened` fields Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit aa12bed)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Oct 17, 2025
…238890) (#239490) # Backport This will backport the following commits from `main` to `9.2`: - [Add support for flattened fields with ignore_above in mappings (#238890)](#238890) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tere","email":"teresa.romero@elastic.co"},"sourceCommit":{"committedDate":"2025-10-17T08:20:07Z","message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:version","v9.2.0","v9.3.0"],"title":"Add support for flattened fields with ignore_above in mappings","number":238890,"url":"https://github.com/elastic/kibana/pull/238890","mergeCommit":{"message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e"}},"sourceBranch":"main","suggestedTargetBranches":["9.2"],"targetPullRequestStates":[{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/238890","number":238890,"mergeCommit":{"message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e"}}]}] BACKPORT--> Co-authored-by: Tere <teresa.romero@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
nickpeihl
pushed a commit
to nickpeihl/kibana
that referenced
this pull request
Oct 23, 2025
…ic#238890) ## Summary Fix elastic#223245 Fields of type `flattened` where being mapped as default. This did not include `ignore_above` field. This PR fixes the mapping and includes `ignore_above` field if exists. If the field is not present, it does not use a default value. Testing done: - unit test case for `generateMappings` function - manual testing installing the reported integration and checking the field is now being mapped. using `crowdstrike` integration and adding `ignore_above` to the [flattened field](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689). once installed, add the integration to an agent policy and verify the mapping has included the given field ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Fixes `ignore_above` mapping for `flattened` fields Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Oct 27, 2025
…ic#238890) ## Summary Fix elastic#223245 Fields of type `flattened` where being mapped as default. This did not include `ignore_above` field. This PR fixes the mapping and includes `ignore_above` field if exists. If the field is not present, it does not use a default value. Testing done: - unit test case for `generateMappings` function - manual testing installing the reported integration and checking the field is now being mapped. using `crowdstrike` integration and adding `ignore_above` to the [flattened field](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689). once installed, add the integration to an agent policy and verify the mapping has included the given field ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Fixes `ignore_above` mapping for `flattened` fields Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Contributor
@teresaromero, can we also backport to all |
This was referenced Nov 19, 2025
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
This was referenced Nov 19, 2025
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
teresaromero
added a commit
to teresaromero/kibana
that referenced
this pull request
Nov 19, 2025
…ic#238890) Fix elastic#223245 Fields of type `flattened` where being mapped as default. This did not include `ignore_above` field. This PR fixes the mapping and includes `ignore_above` field if exists. If the field is not present, it does not use a default value. Testing done: - unit test case for `generateMappings` function - manual testing installing the reported integration and checking the field is now being mapped. using `crowdstrike` integration and adding `ignore_above` to the [flattened field](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689). once installed, add the integration to an agent policy and verify the mapping has included the given field Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. Fixes `ignore_above` mapping for `flattened` fields Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit aa12bed)
teresaromero
added a commit
to teresaromero/kibana
that referenced
this pull request
Nov 20, 2025
…ic#238890) Fix elastic#223245 Fields of type `flattened` where being mapped as default. This did not include `ignore_above` field. This PR fixes the mapping and includes `ignore_above` field if exists. If the field is not present, it does not use a default value. Testing done: - unit test case for `generateMappings` function - manual testing installing the reported integration and checking the field is now being mapped. using `crowdstrike` integration and adding `ignore_above` to the [flattened field](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689). once installed, add the integration to an agent policy and verify the mapping has included the given field Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. Fixes `ignore_above` mapping for `flattened` fields Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit aa12bed)
teresaromero
added a commit
to teresaromero/kibana
that referenced
this pull request
Nov 20, 2025
…ic#238890) Fix elastic#223245 Fields of type `flattened` where being mapped as default. This did not include `ignore_above` field. This PR fixes the mapping and includes `ignore_above` field if exists. If the field is not present, it does not use a default value. Testing done: - unit test case for `generateMappings` function - manual testing installing the reported integration and checking the field is now being mapped. using `crowdstrike` integration and adding `ignore_above` to the [flattened field](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689). once installed, add the integration to an agent policy and verify the mapping has included the given field Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. Fixes `ignore_above` mapping for `flattened` fields Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit aa12bed)
teresaromero
added a commit
that referenced
this pull request
Nov 20, 2025
…238890) (#243532) # Backport This will backport the following commits from `main` to `9.1`: - [Add support for flattened fields with ignore_above in mappings (#238890)](#238890) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tere","email":"teresa.romero@elastic.co"},"sourceCommit":{"committedDate":"2025-10-17T08:20:07Z","message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:version","v9.2.0","v9.3.0"],"title":"Add support for flattened fields with ignore_above in mappings","number":238890,"url":"https://github.com/elastic/kibana/pull/238890","mergeCommit":{"message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/239490","number":239490,"state":"MERGED","mergeCommit":{"sha":"08792efca38a2b6f8d4d9db92f9536dea9186071","message":"[9.2] Add support for flattened fields with ignore_above in mappings (#238890) (#239490)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [Add support for flattened fields with ignore_above in mappings\n(#238890)](https://github.com/elastic/kibana/pull/238890)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Tere <teresa.romero@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/238890","number":238890,"mergeCommit":{"message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e"}}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
teresaromero
added a commit
that referenced
this pull request
Nov 20, 2025
…#238890) (#243534) # Backport This will backport the following commits from `main` to `8.19`: - [Add support for flattened fields with ignore_above in mappings (#238890)](#238890) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tere","email":"teresa.romero@elastic.co"},"sourceCommit":{"committedDate":"2025-10-17T08:20:07Z","message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:version","v9.2.0","v9.3.0"],"title":"Add support for flattened fields with ignore_above in mappings","number":238890,"url":"https://github.com/elastic/kibana/pull/238890","mergeCommit":{"message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/239490","number":239490,"state":"MERGED","mergeCommit":{"sha":"08792efca38a2b6f8d4d9db92f9536dea9186071","message":"[9.2] Add support for flattened fields with ignore_above in mappings (#238890) (#239490)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.2`:\n- [Add support for flattened fields with ignore_above in mappings\n(#238890)](https://github.com/elastic/kibana/pull/238890)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Tere <teresa.romero@elastic.co>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>"}},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/238890","number":238890,"mergeCommit":{"message":"Add support for flattened fields with ignore_above in mappings (#238890)\n\n## Summary\n\nFix #223245 \n\nFields of type `flattened` where being mapped as default. This did not\ninclude `ignore_above` field.\nThis PR fixes the mapping and includes `ignore_above` field if exists.\nIf the field is not present, it does not use a default value.\n\nTesting done:\n\n- unit test case for `generateMappings` function\n- manual testing installing the reported integration and checking the\nfield is now being mapped.\nusing `crowdstrike` integration and adding `ignore_above` to the\n[flattened\nfield](https://github.com/elastic/integrations/blob/main/packages/crowdstrike/data_stream/falcon/fields/fields.yml#L689).\nonce installed, add the integration to an agent policy and verify the\nmapping has included the given field\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n## Release note\n\nFixes `ignore_above` mapping for `flattened` fields\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"aa12bed49740bab72bc3466e3d8ec66198c87d9e"}}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix #223245
Fields of type
flattenedwhere being mapped as default. This did not includeignore_abovefield.This PR fixes the mapping and includes
ignore_abovefield if exists. If the field is not present, it does not use a default value.Testing done:
generateMappingsfunctionusing
crowdstrikeintegration and addingignore_aboveto the flattened field. once installed, add the integration to an agent policy and verify the mapping has included the given fieldChecklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Release note
Fixes
ignore_abovemapping forflattenedfields