dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clean distributed tracing (#170) 

* Renamed to distributed-tracing and a few wording updates

* Removed number
This commit is contained in:
Greg Ingram 2019-10-19 14:50:33 -04:00 committed by Aman Bhardwaj
parent bb9a80e7df
commit 3ebb53778a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
concepts/README.md
View File

@ -16,7 +16,7 @@ This directory contains various Dapr concepts. The goal of these documents is to
Dapr uses a modular design, in which functionalities are grouped and delivered by a number of *components*, such as [pub-sub](./publish-subscribe-messaging/Readme.md) and [secrets](./components/secrets.md). Many of the components are pluggable so that you can swap out the default implemenation with your custom implementations.
* [**Distributed Tracing**](./tracing-logging/tracing-logging.md)
* [**Distributed Tracing**](./distributed-tracing/README.md)
Distirbuted tracing collects and aggregates trace events by transactions. It allows you to trace the entire call chain across multiple services. Dapr integrates with [OpenTelemetry](https://opentelemetry.io/) for distributed tracing and metrics collection.

6
concepts/tracing-logging/tracing-logging.md → concepts/distributed-tracing/README.md
View File

@ -1,4 +1,4 @@
# Distributed tracing
# Distributed Tracing
Dapr uses OpenTelemetry (previously known as OpenCensus) for distributed traces and metrics collection. OpenTelemetry supports various backends including [Azure Monitor](https://azure.microsoft.com/en-us/services/monitor/), [Datadog](https://www.datadoghq.com), [Instana](https://www.instana.com), [Jaeger](https://www.jaegertracing.io/), [SignalFX](https://www.signalfx.com/), [Stackdriver](https://cloud.google.com/stackdriver), [Zipkin](https://zipkin.io) and others.
@ -6,7 +6,7 @@ Dapr uses OpenTelemetry (previously known as OpenCensus) for distributed traces
# Tracing Design
Dapr adds a HTTP/grPC middleware to the Dapr sidecar. The middleware intercepts all Dapr and application traffic and automatically injects correlation IDs to trace distributed transactions. This design has several benifits:
Dapr adds a HTTP/gRPC middleware to the Dapr sidecar. The middleware intercepts all Dapr and application traffic and automatically injects correlation IDs to trace distributed transactions. This design has several benefits:
* No need for code instrumentation. All traffic is automatically traced (with configurable tracing levels).
* Consistent tracing behavior across microservices. Tracing a configured and managed on Dapr sidecar so that it remains consistent across services made by different teams and potentially written in different programming languages.
@ -37,5 +37,5 @@ spec:
Please see the [References](#references) section for more details on how to configure tracing on local environment and Kubernetes environment.
# References
* [How-to: set up distributed tracing](../../howto/diagnose-with-tracing/readme.md)
* [How-To: Set Up Distributed Tracing](../../howto/diagnose-with-tracing/readme.md)