amazon_security_lake: fix handling of JSON encoded flattened fields #14323
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
efd6
added
bugfix
efd6
force-pushed
the
s6140-amazon_security_lake-flattened
branch
from
a7a0602 to
274099b
Compare
The ocsf.api.{request,response}.data fields may be strings holding JSON
encoded data, but the fields is mapped as flattened, resulting in
failure to index documents. Conditionally JSON decode the string and if
this fails, put the value in a well known location in an object so that
the flattened mapping does not fail.
efd6
force-pushed
the
s6140-amazon_security_lake-flattened
branch
from
274099b to
1105833
Compare
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @efd6 |
|
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
ShourieG
reviewed
Jun 27, 2025
...curity_lake/data_stream/event/_dev/test/pipeline/test-application-activity.log-expected.json
Show resolved
Hide resolved
|
Package amazon_security_lake - 2.5.2 containing this change is available at https://epr.elastic.co/package/amazon_security_lake/2.5.2/ |
shmsr
pushed a commit
to shmsr/integrations
that referenced
this pull request
Jun 30, 2025
…lastic#14323) The ocsf.api.{request,response}.data fields may be strings holding JSON encoded data, but the fields is mapped as flattened, resulting in failure to index documents. Conditionally JSON decode the string and if this fails, put the value in a well known location in an object so that the flattened mapping does not fail.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots