-
Notifications
You must be signed in to change notification settings - Fork 1.2k
DOCS-10828: Making Extension logging behavior more obvious #29560
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
Conversation
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.
Tiny edits to make "extension" lowercase. I wasn't sure if "Forwarder" needed to be capitalized but left it that way. Approved so you can merge at will!
Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
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.
Approving again to test CI
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
What does this PR do? What is the motivation?
Many users report issues with duplicate logs due to not realizing the Extension enables log collection by default. Making this more explicit.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in 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.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes