[Logs forwarder] Parse enhanced metrics from Lambda telemetry JSON logs. #859
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.
What does this PR do?
This change makes forwarder parse enhanced metrics from Lambda telemetry logs which get emitted instead of regular REPORT ones when JSON format is enabled. For schema, see https://docs.aws.amazon.com/lambda/latest/dg/telemetry-schema-reference.html#platform-report
Motivation
I would like to see same basic enhanced metrics I see when Lambda uses plain text logging when I enable JSON logging option.
Testing Guidelines
tests/run_unit_tests.sh
LOG_FORMAT=JSON
envar set and confirmed enhanced telemetry is showing upAdditional Notes
cold_start
tag is set for REPORT logs but for some reason neither show up in our DD instanceTypes of changes
Check all that apply