Add aws.requestId to Log Message if the lambda_request_id is found #34
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.
This copies the value that is set in
aws.lambda_request_id
toaws.requestId
on the log message dictionary that is ultimately submitted to the New Relic Logs API.The reason for this is to support a use case leveraging Insights dashboards that combine data from
AwsLambdaInvocation
andLog
NRQL queries along with the Filter New Relic One dashboards by facets. The idea being to:The way the filtering feature is built is it seems to leverage the exact field name from the source chart that is being used as a filter. In the case of
AwsLambdaInvocation
, this is namedaws.requestId
. With current behavior, this will effectively filter out all logs, since this field is not populated in theLog
entity.