-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[DOCS-6867] Restructure OTel Collector Datadog Exporter docs #21002
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My biggest concern is that I'm unclear on how the Datadog Exporter is related to the OpenTelemetry Collector. Is the exporter a component of the collector? And most critically—how does this play out wrt configuration? Do they share the same configuration? Is there a distinction between "configure the Exporter" and "configure the Collector"?
Other key points:
- The setup codeblocks on the component pages need some context ("add this to your config file") / explicit direction as to what exactly to do with the codeblocks provided
- On the Hostname and Tagging page, I can't really make sense of the Kubernetes DaemonSet->Gateway setup
- I'm dubious about the page titles... I made some suggestions but I am really not sure about them
And then some regular spag stuff.
@@ -0,0 +1,141 @@ | |||
--- | |||
title: Datadog Exporter Docker Stats Receiver Configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title: Datadog Exporter Docker Stats Receiver Configuration | |
title: Datadog Exporter Collector Log Collection |
@@ -0,0 +1,189 @@ | |||
--- | |||
title: Datadog Exporter OTLP Receiver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title: Datadog Exporter OTLP Receiver | |
title: Datadog Exporter Collector OTLP Receiver |
@@ -0,0 +1,59 @@ | |||
--- | |||
title: Datadog Exporter Trace Metrics |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title: Datadog Exporter Trace Metrics | |
title: Datadog Exporter Collector Trace Metrics |
|
||
[1]: https://hub.docker.com/r/otel/opentelemetry-collector-contrib/tags | ||
{{% /tab %}} | ||
{{% tab "Docker (other containers)" %}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where does configuration go? i see an otel_collector_config.yaml
and a config.yaml
in step 2, is that related? if so, which one/both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you referring to -v $(pwd)/otel_collector_config.yaml:/etc/otelcol-contrib/config.yaml
? If so, this is to mount volumes, so the otel_collector_config.yaml
on the machine will be available in the container at this path: /etc/otelcol-contrib/config.yaml
.
{{% /tab %}} | ||
{{% tab "Kubernetes (Gateway)" %}} | ||
|
||
To deploy the OpenTelemetry Collector and Datadog Exporter in a Kubernetes Gateway deployment, use this [full example of configuring the OpenTelemetry Collector using the Datadog Exporter as a DaemonSet][1], including the application configuration example. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this meant to link to the same examples as for Kubernetes DaemonSet? if so, then DaemonSet and Gateway have exactly the same instructions. is that intentional?
Co-authored-by: cecilia saixue watt <[email protected]>
There's a diagram here https://docs.datadoghq.com/opentelemetry/ that shows how they're related-- does that help? I think you're correct that we need to be more specific about where the configs go. I'll add that. |
|
||
[1]: https://hub.docker.com/r/otel/opentelemetry-collector-contrib/tags | ||
{{% /tab %}} | ||
{{% tab "Docker (other containers)" %}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you referring to -v $(pwd)/otel_collector_config.yaml:/etc/otelcol-contrib/config.yaml
? If so, this is to mount volumes, so the otel_collector_config.yaml
on the machine will be available in the container at this path: /etc/otelcol-contrib/config.yaml
.
content/en/opentelemetry/collector_exporter/collector_health_metrics.md
Outdated
Show resolved
Hide resolved
content/en/opentelemetry/collector_exporter/collector_batch_memory.md
Outdated
Show resolved
Hide resolved
For the additional context comments: any config file mentioned in the docs refers to the OpenTelemetry Collector configuration, except where it says |
* first 2 pages * otlp * host metrics * add docker metrics * add logs and health * add health, trace, and batch * tech review feedback * fix nav * Apply suggestions from code review Co-authored-by: cecilia saixue watt <[email protected]> * simplify page titles * review feedback * missed one * another * add back missing steps for DS and GW * fix links * fix more links * review feedback --------- Co-authored-by: cecilia saixue watt <[email protected]>
What does this PR do? What is the motivation?
DOCS-6867
Merge instructions
Additional notes