-
Notifications
You must be signed in to change notification settings - Fork 1.2k
DOCS-12589: Lambda on EC2 #32917
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
base: master
Are you sure you want to change the base?
DOCS-12589: Lambda on EC2 #32917
Conversation
Preview links (active after the
|
| description: Install and configure the Datadog Agent for AWS Lambda on Amazon EC2 | ||
| --- | ||
|
|
||
| Datadog Serverless Monitoring enables visibility into AWS Lambda functions running on Amazon EC2. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Datadog Serverless Monitoring enables visibility into AWS Lambda functions running on Amazon EC2. | |
| Monitoring AWS Lambda Managed Instances |
Managed Instances is the official name
| ## Setup | ||
|
|
||
|
|
||
| 1. [Create a task definition file](#create-a-task-definition-file) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you accidentally copied the ECS docs not the Lambda installation docs!
Can we replace this with the following sections:
- 'Installation' - should redirect our basic installation docs for Lambda (all the different runtimes) as the starter template.
- 'Available Metrics' (everything is the same as regular lambda, est. cost isn't sent, billed duration)
- 'Logs Trace Correlation' (needs ENV Var the logs trace injection env variable to be set)
- 'Preview Limitations' (e.g. inferred spans for java, .net, and go)
| title: Monitoring Lambda on EC2 | ||
| description: Install and configure the Datadog Agent for AWS Lambda on Amazon EC2 | ||
| --- | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add a 'preview' callout on this?
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes