fix(aws/securityhub_findings): event.kind as keyword #14251
Merged
+15
−16
Conversation
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
Change event.kind to keyword instead of constant_keyword. When a pipeline error occurs, event.kind was being set to 'pipeline_error' and this break ingestion because event.kind was already assigned a value of 'state'.
Remove unused attributes. Add 'external: ecs' to all ECS fields. [git-generate] go run github.com/andrewkroh/fydler@c7c7bae --fix packages/aws/data_stream/securityhub_findings/**/fields/*yml
[git-generate] elastic-package -C packages/aws build
andrewkroh
added a commit
to andrewkroh/integrations
that referenced
this pull request
Jun 18, 2025
[git-generate] elastic-package -C packages/aws changelog add --link elastic#14251 --next patch --type bugfix --description 'Modify the data type of `event.kind` from a constant_keyword to a keyword to handle pipeline errors that send `event.kind` to `pipeline_error`.'
andrewkroh
force-pushed
the
aws/fix/securityhub_findings
branch
from
f331747 to
948cccf
Compare
[git-generate] elastic-package -C packages/aws changelog add --link elastic#14251 --next patch --type bugfix --description 'Modify the data type of `event.kind` from a constant_keyword to a keyword to handle pipeline errors that send `event.kind` as `pipeline_error`.'
andrewkroh
force-pushed
the
aws/fix/securityhub_findings
branch
from
948cccf to
ba5aa86
Compare
andrewkroh
added
Integration:aws
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
kcreddy
approved these changes
Jun 18, 2025
|
From https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/field-data-types
Changing constant_keyword to keyword should not break anything, but the performance characteristics may differ. |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
? Is there something else that it also closes? |
efd6
approved these changes
Jun 18, 2025
|
Package aws - 3.8.1 containing this change is available at https://epr.elastic.co/package/aws/3.8.1/ |
shmsr
pushed a commit
to shmsr/integrations
that referenced
this pull request
Jun 30, 2025
Change event.kind to keyword instead of constant_keyword.
When a pipeline error occurs, event.kind was being set to
'pipeline_error' and this break ingestion because event.kind
was already assigned a value of 'state'.
The observed error was:
[constant_keyword] field [event.kind] only accepts values that are equal
to the value defined in the mappings [state], but got [pipeline_error]
Closes elastic#12970
andrewkroh
added
the
documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Proposed commit message
Change event.kind to keyword instead of constant_keyword.
When a pipeline error occurs, event.kind was being set to
'pipeline_error' and this break ingestion because event.kind
was already assigned a value of 'state'.
The observed error was:
Closes #12970
Checklist
changelog.ymlfile.Author's Notes
This bug was detected in our internal demo deployment of the integration.
Logs
This will fix errors like:
{ "type": "document_parsing_exception", "reason": "[1:7357] failed to parse field [event.kind] of type [constant_keyword] in document with id '2KqJqX41g3ygdMw5sXCzYx1Wb/Y='. Preview of field's value: 'pipeline_error'", "caused_by": { "type": "illegal_argument_exception", "reason": "[constant_keyword] field [event.kind] only accepts values that are equal to the value defined in the mappings [state], but got [pipeline_error]" } }