DO NOT MERGE: "Docs for AI Agents" QA files for OpenTelemetry #31962
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jhgilbert
commented
Oct 2, 2025
| title: Datadog and OpenTelemetry Compatibility | ||
| description: Datadog, the leading service for cloud-scale monitoring. | ||
| breadcrumbs: Docs > OpenTelemetry in Datadog > Datadog and OpenTelemetry Compatibility | ||
| sourceUrl: https://docs.datadoghq.com/opentelemetry/compatibility/index.html |
There was a problem hiding this comment.
I just noticed the camelcase, I'll fix it to source_url.
brett0000FF
reviewed
Oct 3, 2025
There was a problem hiding this comment.
@jhgilbert This is so cool! There were only a couple of minor things that I commented on. No showstoppers though. 🔥
| # Important note for users on the following Datadog sites: app.ddog-gov.com | ||
|
|
||
| {% alert level="warning" %} | ||
| This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site). (). |
There was a problem hiding this comment.
Looks like any of the gov callout warning have an extra (). at the end.
|
|
||
| If you receive a `403 Forbidden` error when sending logs to the Datadog OTLP logs intake endpoint, it indicates one potential issue: | ||
|
|
||
| - The endpoint URL is incorrect for your organization.**Solution**: Use the correct endpoint URL for your organization. Your site is , so you need to use the endpoint. |
There was a problem hiding this comment.
Similar issue with the dynamic site name (and endpoint) creating a broken sentence.
|
|
||
| Use the `dd-otel-metric-config` header to configure how metrics are translated and sent to Datadog. The JSON header contains the following fields: | ||
|
|
||
| {% dl %} |
There was a problem hiding this comment.
This doesn't seem correct for the description lists? I believe it should just render as normal description list formatting?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
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