Fix lambda_logs data_stream pipeline and tests #42
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
ltflb-bgdi
approved these changes
May 12, 2025
packages/ppbgdi/data_stream/lambda_logs/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
packages/ppbgdi/data_stream/lambda_logs/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
ckaenzig
force-pushed
the
feat-PB-1277-lambda-logs
branch
from
2d15a7e to
2536c71
Compare
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.
The lambda log entry comes in an unparsed JSON "message" field.
The pipeline changes are inspired by aws.apigateway_logs , parsing the json into "aws.lambda" and keeping the original content in the event.original field.
The tests are also changed to use raw log files that happen to contain json data, but not yet parsed.