From 04f13cc06fc357edfd2bfa1c035d58d0189b31c1 Mon Sep 17 00:00:00 2001 From: Bastian Ike Date: Fri, 20 Dec 2019 14:53:23 +0100 Subject: [PATCH] add jaeger --- radar/2019-11-01/distributed-tracing.md | 4 ++-- radar/2019-11-01/jaeger.md | 11 +++++++++++ 2 files changed, 13 insertions(+), 2 deletions(-) create mode 100644 radar/2019-11-01/jaeger.md diff --git a/radar/2019-11-01/distributed-tracing.md b/radar/2019-11-01/distributed-tracing.md index 34b03fd..584fc1a 100644 --- a/radar/2019-11-01/distributed-tracing.md +++ b/radar/2019-11-01/distributed-tracing.md @@ -1,11 +1,11 @@ --- title: "Distributed Tracing" ring: trial -quadrant: methods-and-patterns +quadrant: platforms-and-aoe-services --- 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. 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). diff --git a/radar/2019-11-01/jaeger.md b/radar/2019-11-01/jaeger.md new file mode 100644 index 0000000..27fd107 --- /dev/null +++ b/radar/2019-11-01/jaeger.md @@ -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.