From f80dbd416c7462d8a8002d0c08027f2d634a0420 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Mon, 28 Aug 2023 09:38:49 -0400 Subject: [PATCH] mark review Signed-off-by: Hannah Hunter --- .../tracing/otel-collector/open-telemetry-collector.md | 6 +++--- .../en/operations/observability/tracing/tracing-overview.md | 1 + 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector.md b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector.md index 10c57ef3e..c1d5e4fda 100644 --- a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector.md +++ b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector.md @@ -6,9 +6,9 @@ weight: 900 description: "How to use Dapr to push trace events through the OpenTelemetry Collector." --- -Dapr directly writes traces using the OpenTelemetry (OTEL) protocol as the **recommended** method. For observability tools that support OTEL protocol, you don't need to use the OpenTelemetry Collector. +Dapr directly writes traces using the OpenTelemetry (OTEL) protocol as the **recommended** method. Run the Open Telemetry Collector on your hosting platform to send OTEL events to the observability tool that supports OTEL protocol. -Dapr can also write traces using the Zipkin protocol. Previous to supporting the OTEL protocol, you could combine the Zipkin protocol with the [OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector) to send traces to observability tools such as AWS X-Ray, Google Cloud Operations Suite, and Azure App Insights. This approach remains for reference purposes only. +Dapr can also write traces using the Zipkin protocol. Previous to supporting the OTEL protocol, you use the Zipkin protocol with the [OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector) to send traces to observability tools such as AWS X-Ray, Google Cloud Operations Suite, and Azure Monitor. Both protocol approaches are valid, however OTEL is the recommended choice. ![Using OpenTelemetry Collect to integrate with many backend](/images/open-telemetry-collector.png) @@ -33,7 +33,7 @@ Dapr can also write traces using the Zipkin protocol. Previous to supporting the kubectl apply -f open-telemetry-collector-generic.yaml ``` -## Set up Dapr to send trace to OTEL Collector +## Set up Dapr to send traces to OTEL Collector Set up a Dapr configuration file to turn on tracing and deploy a tracing exporter component that uses the OpenTelemetry Collector. diff --git a/daprdocs/content/en/operations/observability/tracing/tracing-overview.md b/daprdocs/content/en/operations/observability/tracing/tracing-overview.md index 2375eea34..603e5d121 100644 --- a/daprdocs/content/en/operations/observability/tracing/tracing-overview.md +++ b/daprdocs/content/en/operations/observability/tracing/tracing-overview.md @@ -10,6 +10,7 @@ Dapr uses the Open Telemetry (OTEL) and Zipkin protocols for distributed traces. Most observability tools support OTEL, including: - [Google Cloud Operations](https://cloud.google.com/products/operations) +- [AWS X-ray](https://aws.amazon.com/xray/) - [New Relic](https://newrelic.com) - [Azure Monitor](https://azure.microsoft.com/services/monitor/) - [Datadog](https://www.datadoghq.com)