Skip to content

fix AWS Lambda message handling#19250

Draft
Kavindu-Dodan wants to merge 1 commit into
elastic:mainfrom
Kavindu-Dodan:fix/fix-lambda-message-handling
Draft

fix AWS Lambda message handling#19250
Kavindu-Dodan wants to merge 1 commit into
elastic:mainfrom
Kavindu-Dodan:fix/fix-lambda-message-handling

Conversation

@Kavindu-Dodan
Copy link
Copy Markdown
Contributor

@Kavindu-Dodan Kavindu-Dodan commented May 27, 2026

Proposed commit message

aws.lambda.message is defined as a flattened field. However, Lambda log's JSON pipeline ignore checks to validate this. This cause JSON pipeline to parse but indexing to fail.

If the payload contains a non-compliant content, then this fix preserve the original message at root level message field.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • [] I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
@Kavindu-Dodan Kavindu-Dodan force-pushed the fix/fix-lambda-message-handling branch from a32f83b to 0277758 Compare May 27, 2026 21:16
@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants