Repository navigation
[Preview only, do not merge] OpenTelemetry docs refactor: all changes together - #41110
Draft
brett0000FF wants to merge 58 commits into
Draft
brett0000FF wants to merge 58 commits into
brett0000FF wants to merge 58 commits into
Conversation
…to the Kubernetes quickstart
…the DDOT cluster tag
…tor without the Agent
…collector/kubernetes/
…Collector Kubernetes page
Group the Send Data nav into the DDOT Collector, the upstream OpenTelemetry Collector, direct OTLP ingest, and the Datadog Agent. Rewrite the Send Data hub as a comparison, refocus the DDOT Collector overview on the Collector without the Agent, and make the Agent overview cover OTLP Ingest in the Agent and OTel in the Agent. Retitle the Agent install pages to OTel in the Agent, and remove a nav entry for a page that no longer exists.
Replace the landing page's option list with the DDOT and upstream OpenTelemetry setups, a pointer to direct OTLP ingest, and links to Getting Started and the Send Data hub.
Say who builds each Collector, list supported platforms, and point inbound links that meant the Agent's Collector at OTel in the Agent. Name the DDOT SDK and Full-Host Profiler on the landing page, and move the Remote Configuration callout to the Datadog Agent overview.
…o the DDOT Collector The Compatibility page said not to run the Agent and a separate Collector on the same host. Add an exception for the DDOT Collector, which documents adding the Agent on the same nodes.
Use a plain name for the OpenTelemetry Collector that runs inside the Datadog Agent, so it isn't confused with OTLP Ingest in the Agent.
github-actions
Bot
added
Architecture
…ing cautions on the DDOT Collector Kubernetes page
Contributor
Add Kubernetes steps with OpenTelemetry Operator injection, host steps, verification, known limits, and troubleshooting. Rename the SDK nav entries, point the instrumentation overview at the new page, and list otlp as an accepted OTEL_TRACES_EXPORTER value.
The service and env search finds logs the SDK sends over OTLP. Container logs read by the Collector carry those tags only if the Collector adds them, so point to a namespace search for those.
… DDOT Collector Kubernetes page Move them out of the optional steps in both installation methods, make the Metrics and Logs checks conditional on the optional pieces, and point the instrumentation step at the OpenTelemetry SDK page.
…, and link the old DDOT Collector name
…e Send Data diagram
…nk both paths from the chooser Set DD_AGENT_ENABLED=false in the DDOT block, with a separate step to install the Agent. Fill the DDOT path summary, ask for a dedicated test cluster up front, and say to delete the Agent's secret before rerunning the installer. Add DDOT, Upstream, and host or Docker routes to the Getting Started chooser.
# Conflicts: # hugo/content/en/opentelemetry/setup/ddot_collector/kubernetes.md
# Conflicts: # hugo/content/en/opentelemetry/instrument/dd_sdks/_index.md
# Conflicts: # hugo/content/en/opentelemetry/instrument/dd_sdks/_index.md # hugo/content/en/opentelemetry/setup/ddot_collector/kubernetes.md
Say what a DDOT SDK is and which signals it sends, scope the no-code-change claim, and point existing Datadog SDK users to OpenTelemetry API Support. Move the Datadog SDK pages under their own nav entry, add Java and .NET checks to troubleshooting, and fix the Java DD_TRACE_OTEL_ENABLED note.
…name claims Replace the leftover sample-app section with one Instrument your application section that links the DDOT SDK page and uses OTLP over HTTP. Split the Verify logs row, say the DD_HOSTNAME crash applies before 7.85.0, make the Helm presets step optional, shorten the billing alerts, and add Next steps.
…ode-cluster hostname rule The standalone Collector needs DD_HOSTNAME before 7.85.0, not only with 7.83.1. Datadog names a host <node>-<cluster> only when no cloud-provider attributes apply, so say that and link the hostname mapping order.
… setup pages Expand Datadog OpenTelemetry (DDOT) on the landing page, give each setup a choice criterion, and link each golden path to its quickstart tab. Trim the hub so the table does the comparing. Remove the DaemonSet alert that said the Datadog SDK needs the Agent, say the custom builds make Agent images, scope the flare and tagging claims, add a DDOT column placeholder to Compatibility, and drop the nav entry that pointed at a section anchor.
… to Guides Getting Started is now the quickstart itself, with a short list for readers who aren't on Kubernetes. The OpenTelemetry Demo moves to Guides, the duplicate Datadog Exporter example page redirects to the original tutorial, and the site-wide Getting Started entry opens the quickstart. Also fix the DDOT troubleshooting search, the Agent default wording, and the production links.
…arning Match the in-app install command with the host profiler variables, and describe the optional host profiler and its requirements. Say that the uninstall also removes the Datadog Operator's custom resource definitions when the Agent is installed, note how hostnames work on managed clusters, and mention the installer's values file argument.
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
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?
Preview only. Do not merge. This branch combines the open OpenTelemetry docs PRs, so reviewers can see all of the changes together in one preview:
Review and merge the individual PRs. This PR is updated by merging their latest changes, and is closed when they merge.
Merge readiness
AI assistance
Branch assembled with Claude Code.
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.Additional notes