feat(receiver): aws-like report log for invocations #2011
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.
Description
AWS Lambda users can see the following report in AWS Cloudwatch after the invocation has finished:
This pull request adds the ability to display these report and send them along with the regular Lambda application logs. This feature is hidden behind a flag (
log_report), which is turned off by default.Contrary to what someone could expect based on the documentation, these metrics are all floats, attempt to parse them as integers would fail.
Testing
Added unit test coverage, and tested in a production environment.
Attaching a Grafana log query for evidence (we're using Otel -> Alloy -> Loki -> Grafana pipeline)
Collector config extract: