Skip to content

update log injection docs #31192

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
merged 4 commits into from
Aug 21, 2025
Merged

update log injection docs #31192

merged 4 commits into from
Aug 21, 2025

Conversation

mabdinur
Copy link
Contributor

Log Injection is now enabled by default in the latest release of Datadog APM SDKs (except Go and C++ with do not support DD_LOGS_INJECTION configuration). This PR updates docs to reflect this.

Merge instructions

Merge readiness:

  • Ready for merge

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

@mabdinur mabdinur requested review from a team as code owners August 20, 2025 15:09
@github-actions github-actions bot added the Guide Content impacting a guide label Aug 20, 2025
Copy link
Contributor

github-actions bot commented Aug 20, 2025

✅ Documentation Team Review

The documentation team has approved this pull request. Thank you for your contribution!

Copy link
Contributor

github-actions bot commented Aug 20, 2025

Preview links (active after the build_preview check completes)

Modified Files

@mabdinur mabdinur requested a review from duncanhewett August 20, 2025 17:01
Copy link
Contributor

@duncanhewett duncanhewett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - I added a couple of comments.

**Supported Input**: Boolean (`true`/`false`) <br>
**Caveats**: Not supported in C++ or Go. The default value in Ruby is `true`.<br>
**Caveats**: Not supported in C++ or Go.<br>
**Description**: Enables or disables the automatic injection of trace context (trace ID, span ID) into application logs. This allows for correlation between traces and logs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we should clarify in the description that automatic injection is only for JSON/structured logs?

Copy link
Contributor

@aliciascott aliciascott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @mabdinur just a small suggestion, let me know when this is ready for re-review!

Co-authored-by: Alicia Scott <[email protected]>
Co-authored-by: Duncan Hewett <[email protected]>
@mabdinur mabdinur requested a review from aliciascott August 21, 2025 14:34
Copy link
Contributor

@aliciascott aliciascott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the updates looks good!

@mabdinur mabdinur merged commit 3e958fc into master Aug 21, 2025
20 of 21 checks passed
@mabdinur mabdinur deleted the munir/update-log-injection branch August 21, 2025 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Guide Content impacting a guide
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants