Update OP OTel default port

[maycmlee]

What does this PR do? What is the motivation?

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/may/otel-default-port/observability_pipelines/sources/opentelemetry

[domalessi]

A few minor suggestions!

[domalessi]

Thanks for the changes! Looks great :)

[mikhacim]

can we add this right after this line at the top: "Configure your OTel exporters to point to HTTP or gRPC"

"The Worker exposes configurable listener ports for each protocol.

Note: The ports 4318 (HTTP) and 4317 (gRPC) shown below are examples only. You can configure the port values for either protocol in the Worker. Ensure your OTel exporters match whatever port you choose."

Is it possible to make the Note a callout like we do here: https://docs-staging.datadoghq.com/may/otel-default-port/observability_pipelines/#observability-pipelines-worker

[maycmlee]

Thanks, updated and added note callout.