-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Recommend using Datadog CLI to enable serverless monitoring #11376
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
281f376
to
962daee
Compare
cswatt
requested changes
Aug 10, 2021
@@ -17,6 +17,51 @@ After you have installed the [AWS integration][2] and the [Datadog Forwarder][3] | |||
## Configuration | |||
|
|||
{{< tabs >}} | |||
{{% tab "Datadog CLI" %}} | |||
|
|||
Use the Datadog CLI to set up instrumentation on your Lambda functions in your CI/CD pipelines or from your local command-line interface. The CLI command automatically adds the Datadog Lambda library and extension to your functions using Lambda Layers, and configures your functions to send metrics, traces, and logs to Datadog. |
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.
Suggested change
Use the Datadog CLI to set up instrumentation on your Lambda functions in your CI/CD pipelines or from your local command-line interface. The CLI command automatically adds the Datadog Lambda library and extension to your functions using Lambda Layers, and configures your functions to send metrics, traces, and logs to Datadog. | |
Use the Datadog CLI to set up instrumentation on your Lambda functions in your CI/CD pipelines or from your local command-line interface. The CLI command automatically adds the Datadog Lambda Library and extension to your functions using Lambda Layers. It also configures your functions to send metrics, traces, and logs to Datadog. |
cswatt
approved these changes
Aug 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
The precommit hooks making the PR appear more complex than it really is. The actual changes are:
DATADOG_API_KEY
env var when using the Datadog CLI with Lambda Extension.Motivation
Datadog CLI is out of beta, and it is the easiest way to set up Datadog serverless monitoring and it works regardless whether you are using a specific devtool.
Preview
Additional Notes
Reviewer checklist