-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[serverless] Configure logs/core agent to respect datadog.yaml #11269
Conversation
Can we add a test to make sure the issue does not re-occur? |
I'm going to add a datadog.yaml to an integration test, with log obfuscation enabled. I think that will be the best way to test it. |
@@ -9,7 +9,8 @@ async function myHandler(event, context) { | |||
await sleep(); | |||
console.error("XXX LOG 2 XXX"); | |||
await sleep(); | |||
|
|||
console.error("XXX LOG M12345M XXX"); |
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 would suggest replacing M12345M with something like IF THIS STRING APPEARS IN A SNAPSHOT, MASKING IS NOT WORKING
so that it's easier to see in a diff what the expected behavior is.
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.
Looks good, just one suggestion!
What does this PR do?
Fixes a bug in the Datadog Lambda Extension, that was causing datadog.yaml to be incorrectly loaded.
Motivation
It appears this code was refactored out by mistake:
11e6514#diff-80867e42400e0fcf41760721c1e7bf703a1064d0636bfe72007834f0f21f7475L219
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Reviewer's Checklist
Triage
milestone is set.major_change
label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.changelog/no-changelog
label has been applied.qa/skip-qa
label is not applied.team/..
label has been applied, indicating the team(s) that should QA this change.need-change/operator
andneed-change/helm
labels have been applied.