add jaeger
This commit is contained in:
@@ -1,11 +1,11 @@
|
|||||||
---
|
---
|
||||||
title: "Distributed Tracing"
|
title: "Distributed Tracing"
|
||||||
ring: trial
|
ring: trial
|
||||||
quadrant: methods-and-patterns
|
quadrant: platforms-and-aoe-services
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
Distributed Tracing creates visibility over processes spanning multiple applications.
|
Distributed Tracing creates visibility over processes spanning multiple applications.
|
||||||
In a microservice world where a request or operation involves multiple applications it is helpful to have an overview of what system is involved, at what point.
|
In a microservice world where a request or operation involves multiple applications it is helpful to have an overview of what system is involved, at what point.
|
||||||
Also visibility of communicated data and errors helps to quickly identify issues in a microservice environment.
|
Also visibility of communicated data and errors helps to quickly identify issues in a microservice environment.
|
||||||
Our tool of choice is [Jaeger](https://www.jaegertracing.io/) with [B3 Propagation](https://github.com/openzipkin/b3-propagation).
|
Our tool of choice is [Jaeger](/platforms-and-aoe-services/jaeger.html) with [B3 Propagation](https://github.com/openzipkin/b3-propagation).
|
||||||
|
|||||||
11
radar/2019-11-01/jaeger.md
Normal file
11
radar/2019-11-01/jaeger.md
Normal file
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
title: "Jaeger"
|
||||||
|
ring: trial
|
||||||
|
quadrant: platforms-and-aoe-services
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
[Jaeger](https://www.jaegertracing.io/) is a tool for [Distributed Tracing](/platforms-and-aoe-services/distributed-tracing.html). Developed at Uber and inspired by Dapper and OpenZipkin it grew into an [Cloud Native Computing Foundation](https://www.cncf.io/) project.
|
||||||
|
|
||||||
|
Jaeger is a great tool for troubleshooting distributed systems, such as microservice architectures. Developers and Operation can quickly see communicaiton between services, and what data is communicated where.
|
||||||
|
Errors in services can be traced to the originating system. Global trace identifiers are communicated using B3 headers. Jaeger supports Zipkin, which allows easy migration von OpenZipkin & co.
|
||||||
Reference in New Issue
Block a user