Skip to content

Commit 62793d6

Browse files
authored
Notes for excluding Lambda platform logs (#523)
* Notes for excluding Lambda platform logs * Update README.md
1 parent ac4be12 commit 62793d6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

aws/logs_monitoring/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -356,7 +356,7 @@ Using an inefficient regular expression, such as `.*`, may slow down the Forward
356356

357357
Some examples of regular expressions that can be used for log filtering:
358358

359-
- Include (or exclude) Lambda platform logs: `"(START|REPORT|END)\s`
359+
- Include (or exclude) Lambda platform logs: `"(START|END) RequestId\s`. Note: The preceding `"` is needed to match the start of the log message, which is in a json blob (`{"message": "START RequestId...."}`). Datadog recommends keeping the `REPORT` logs, as they are used to populate the invocations list in the serverless function views.
360360
- Include CloudTrail error messages only: `errorMessage`
361361
- Include only logs containing an HTTP 4XX or 5XX error code: `\b[4|5][0-9][0-9]\b`
362362
- Include only CloudWatch logs where the `message` field contains a specific JSON key/value pair: `\\"awsRegion\\":\\"us-east-1\\"`

0 commit comments

Comments
 (0)