Skip to content

chore: Polish the language to recommend Lambda Extension over forwarder #911

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aws/logs_monitoring/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The Datadog Forwarder is an AWS Lambda function that ships logs from AWS to Data
- Forward CloudWatch and S3 logs.
- Forward logs from SNS, and Kinesis events to Datadog.
- Kinesis data stream events support CloudWatch logs only.
- Forward metrics, traces, and logs from AWS Lambda functions to Datadog. Datadog recommends to use [Datadog Lambda Extension][1] to monitor Lambda functions.
- Forward metrics, traces, and logs from AWS Lambda functions to Datadog. However, instead of using a forwarder, Datadog recommends to use [Datadog Lambda Extension][1] to monitor Lambda functions.

For Serverless customers using the Forwarder to forward metrics, traces, and logs from AWS Lambda logs to Datadog, you should [migrate to the Datadog Lambda Extension][3] to collect telemetry directly from the Lambda execution environments. The Forwarder is still available for use in Serverless Monitoring, but will not be updated to support the latest features.

Expand Down
Loading