[DOCS-15275] Add OP Traces for Preview - #38665
Conversation
|
[Automated message] This PR has merge conflicts created by the docs repo reorg project. Because this PR is marked as a work in progress, no attempt was made to auto-resolve the conflicts. When your PR is finished, you can queue your PR for an auto-fix by removing the This is an automated comment, but if you have a question, you can mention me in this PR (external contributors) or reach out in #docs-repo-reorg-support on Slack (internal contributors). |
jhgilbert
added
astro-reorg-skip
This comment has been minimized.
This comment has been minimized.
|
|
||
| - Datadog APM | ||
| - OpenTelemetry Traces | ||
|
|
There was a problem hiding this comment.
No links currently. These pages will be created in separate child PRs. I will add links there.
evazorro
left a comment
evazorro
left a comment
There was a problem hiding this comment.
Flagged a few rendering things I noticed, but this largely looks good!
| {% /if %} | ||
|
|
||
| The Observability Pipelines Worker is software that runs in your environment to centrally aggregate and process your logs and metrics ({% glossary-tooltip term="preview" case="title" /%}), and then route them to different destinations. | ||
| The Observability Pipelines Worker is software that runs in your environment to centrally aggregate and process your logs, metrics, and traces ({{< tooltip text="in Preview" tooltip="Traces for Observability Pipelines is in Preview. Contact your account manager to request access." >}}) ({% glossary-tooltip term="preview" case="title" /%}), and then route them to different destinations. |
There was a problem hiding this comment.
I'm not sure what the right fix it, but in the preview build it looks like this isn't rendering correctly:
| {{< img src="observability_pipelines/setup/pipeline_ui.png" alt="The pipelines page with a source going to two processors groups and two destinations" style="width:100%;" >}} | ||
|
|
||
| Observability Pipelines lets you collect and process logs and metrics within your own infrastructure, and then route them to different destinations. A pipeline consists of three core components: | ||
| Observability Pipelines lets you collect and process logs, metrics, and traces ({{< tooltip text="in Preview" tooltip="Traces for Observability Pipelines is in Preview. Contact your account manager to request access." >}}) within your own infrastructure, and then route them to different destinations. A pipeline consists of three core components: |
There was a problem hiding this comment.
This one does work! So maybe it's something about the .mdoc file?
| <div class="alert alert-info">The processors outlined in this documentation are specific to on-premises logging environments. To parse, structure, and enrich cloud-based logs, see the <a href="https://docs.datadoghq.com/logs/log_configuration/logs_to_metrics">Log Management</a> documentation.</div> | ||
|
|
||
| Use Observability Pipelines' processors to parse, structure, and enrich your logs and metrics. When you create a pipeline in the UI, pre-selected processors are added to your processor group based on the selected template. You can add additional processors and delete any existing ones based on your processing needs. | ||
| Use Observability Pipelines' processors to parse, structure, and enrich your logs, metrics, and traces ({{< tooltip text="in Preview" tooltip="Traces for Observability Pipelines is in Preview. Contact your account manager to request access." >}}). When you create a pipeline in the UI, pre-selected processors are added to your processor group based on the selected template. You can add additional processors and delete any existing ones based on your processing needs. |
There was a problem hiding this comment.
I don't know if this is fixable, but the line is breaking right after the parenthesis
There was a problem hiding this comment.
This is weird. I'm seeing something similar with an extra space in the mdoc file. I'll need to ping webops about it.
There was a problem hiding this comment.
Webops card: https://datadoghq.atlassian.net/browse/WEB-9845
Co-authored-by: Eva Parish <eva.parish@datadoghq.com>
| {% /if %} | ||
|
|
||
| The Observability Pipelines Worker is software that runs in your environment to centrally aggregate and process your logs and metrics ({% glossary-tooltip term="preview" case="title" /%}), and then route them to different destinations. | ||
| The Observability Pipelines Worker is software that runs in your environment to centrally aggregate and process your logs, metrics, and traces ({% tooltip contents="Traces for Observability Pipelines is in Preview. Contact your account manager to request access." %}in Preview{% /tooltip %}), and then route them to different destinations. |
There was a problem hiding this comment.
This tooltip has a space before "in Preview" that I can't get rid of
|
Thanks @evazorro for the review! Applied your suggestions. I'll open a webops card about the spacing issues. |
evazorro
left a comment
evazorro
left a comment
There was a problem hiding this comment.
Sounds good re the webops ticket! Thanks, May!
3 participants
What does this PR do? What is the motivation?
Updates OP docs for Traces.
Merge readiness
Do not merge.
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.AI assistance
Additional notes