Improve Enabling Logs Info for OTLP Ingest

[brett0000FF]

What does this PR do? What is the motivation?

• Follow up to docs(opentelemetry): add additional configuration parameters for OpenTelemetry in Kubernetes #33268.
• Organize content better around enabling logs.

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

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/brett.blue/clarify-logs-otlp-ingest/opentelemetry/setup/otlp_ingest_in_the_agent

[brett0000FF]

@songy23 - We just merged a small update to make it more explicit that logs are disabled by default (via and external contributor). Since I was looking at the doc, I felt there was an opportunity to organize the page a bit better around this. I created a new section on enabling logs. Could you please take a look and let me know what you think? Thanks!

[songy23]

LGTM