8000 Post Reorg Tweaks by brett0000FF · Pull Request #28940 · DataDog/documentation · GitHub
[go: up one dir, main page]

Skip to content

Post Reorg Tweaks #28940

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 8 commits into from
Apr 30, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 15 additions & 7 deletions config/_default/menus/main.en.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -592,10 +592,18 @@ menu:
parent: essentials_heading
weight: 70000
- name: Getting Started
url: /getting_started/opentelemetry
url: /opentelemetry/getting_started/
identifier: otel_guides_getting_started
parent: opentelemetry_top_level
weight: 1
- name: Datadog Example Application
url: /getting_started/opentelemetry
parent: otel_guides_getting_started
weight: 101
- name: OpenTelemetry Demo Application
url: /opentelemetry/guide/otel_demo_to_datadog
parent: otel_guides_getting_started
weight: 102
- name: Feature Compatibility
url: opentelemetry/compatibility/
identifier: otel_compatibility
Expand All @@ -611,7 +619,7 @@ menu:
identifier: otel_sdks
parent: otel-instrumentation
weight: 301
- name: OTel APIs
- name: OTel APIs with Datadog SDKs
url: /opentelemetry/instrument/api_support
identifier: otel-api-dd-sdk
parent: otel-instrumentation
Expand Down Expand Up @@ -649,7 +657,7 @@ menu:
identifier: otel_instrumentation_libraries
parent: otel-instrumentation
weight: 303
- name: Environment Variables
- name: Configuration
url: opentelemetry/config/environment_variable_support/
identifier: otel_env_var
parent: otel-instrumentation
Expand Down Expand Up @@ -694,17 +702,17 @@ menu:
identifier: otel-setup-otlp-ingest
parent: otel_collect
weight: 402
- name: Direct OTLP Ingest
url: /opentelemetry/setup/intake_endpoint
- name: Agentless Deployment
url: /opentelemetry/setup/agentless/
identifier: otel-setup-intake-endpoint
parent: otel_collect
weight: 403
- name: Logs Endpoint
url: /opentelemetry/setup/intake_endpoint/otlp_logs
url: /opentelemetry/setup/agentless/logs
parent: otel-setup-intake-endpoint
weight: 301
- name: Metrics Endpoint
url: /opentelemetry/setup/intake_endpoint/otlp_metrics
url: /opentelemetry/setup/agentless/metrics
parent: otel-setup-intake-endpoint
weight: 302
- name: Semantic Mapping
Expand Down
2 changes: 1 addition & 1 deletion content/en/opentelemetry/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ If your applications and services are instrumented with OpenTelemetry libraries,

### Additional setup options

For other setup options, including direct OTLP intake, see [Send Data to Datadog][7].
For other setup options, including Agentless deployment, see [Send Data to Datadog][7].

## Further reading

Expand Down
18 changes: 18 additions & 0 deletions content/en/opentelemetry/getting_started.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: Getting Started with OpenTelemetry at Datadog
disable_toc: false
further_reading:
- link: "/opentelemetry/guide"
tag: "Documentation"
text: "OpenTelemetry Guides"
---

{{< whatsnext desc=" " >}}
{{< nextlink href="/getting_started/opentelemetry" >}}Getting Started with a Datadog Example Application{{< /nextlink >}}
{{< nextlink href="/opentelemetry/guide/otel_demo_to_datadog" >}}Getting Started with the OpenTelemetry Demo Application
{{< /nextlink >}}
{{< /whatsnext >}}

## Further reading

{{< partial name="whats-next/whats-next.html" >}}
2 changes: 1 addition & 1 deletion content/en/opentelemetry/setup/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ There are multiple ways to send OpenTelemetry data to Datadog. Choose the method
|---------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|
| <strong>OTel Collector</strong> | New or existing OTel users wanting a vendor-neutral setup | <ul><li>Complete vendor neutrality</li><li>Send traces, metrics, and logs to Datadog without installing the Datadog Agent or tracing libraries</li><li>Advanced processing capabilities (for example, [tail-based sampling][4])</li></ul> | [Send data using the OTel Collector][2] |
| <strong>Datadog Agent</strong> | Existing Datadog users or teams requiring Agent-based features | <ul><li>Access to full Datadog Agent capabilities</li><li>Enhanced monitoring capabilities including:<ul><li>Fleet Automation</li><li>Live Container Monitoring</li><li>Kubernetes Explorer</li><li>Live Processes</li><li>Cloud Network Monitoring</li><li>Universal Service Monitoring</li><li>{{< translate key="integration_count" >}}+ Datadog integrations</li></ul></li></ul> | [Send data using OTLP ingest in the Agent][1] |
| <strong>Direct OTLP Ingest</strong> | Situations requiring direct connection without additional infrastructure | <ul><li>Direct data transmission</li><li>No additional components needed</li></ul> | [Send data using the intake endpoint][3] |
| <strong>Agentless Deployment</strong> | Situations requiring direct connection without additional infrastructure | <ul><li>Direct data transmission</li><li>No additional components needed</li></ul> | [Send data using the OTLP endpoint][3] |

<div class="alert alert-info"><strong>Still not sure which setup is right for you?</strong><br> See the <a href="/opentelemetry/compatibility/">Feature Compatibility</a> table to understand which Datadog features are supported.</div>

Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
---
title: Datadog OTLP Intake Endpoint
aliases:
- /opentelemetry/setup/intake_endpoint/
further_reading:
- link: "/opentelemetry/setup"
tag: "Documentation"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: Datadog OTLP Logs Intake Endpoint
aliases:
- /opentelemetry/otlp_logs
- /opentelemetry/setup/intake_endpoint/otlp_logs
further_reading:
- link: "https://opentelemetry.io/docs/concepts/sdk-configuration/general-sdk-configuration/"
tag: "External Site"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: Datadog OTLP Metrics Intake Endpoint
aliases:
- "/opentelemetry/otlp_metrics"
- "/opentelemetry/setup/intake_endpoint/otlp_metrics"
further_reading:
- link: "https://opentelemetry.io/docs/concepts/sdk-configuration/general-sdk-configuration/"
tag: "External Site"
Expand Down
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this also supposed to be an item in the navigation? Asking since Logs and Metrics are listed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the review! No, not yet. This is still supposed to be hidden for now. Thanks for checking though. 😄

Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: Datadog OTLP Traces Intake Endpoint
aliases:
- /opentelemetry/otlp_endpoint
- /opentelemetry/setup/intake_endpoint/otlp_traces
private: true
further_reading:
- link: "https://opentelemetry.io/docs/concepts/sdk-configuration/general-sdk-configuration/"
Expand Down
Loading
0