クラウドネイティブ時代の分散トレーシング / Distributed Tracing in a Cloud Native Age
Presentation slides for de:code 2019 DT81 Session title: クラウドネイティブ時代の分散トレーシング - Distributed Tracing in a Cloud Native Age
Session Video: https://youtu.be/0RFYvMfIJUo Date: May 29, 2019
service_red app process service_blue envoy process Service Blue Container service_blue app process service_green envoy process Service Green Container service_green app process 8080 8080 8080 Jaeger process Port 9411 Port 9411 Port 9411 Trace Data Port 8000 Port 80 Port 16686 Port 16686 Access to Jaeger UI Port 80 Port 9000 Trace Data Trace Data Port 80 Port 80 Port 9000 Trace Data Port 9411 Demo1 Architecture https://github.com/yokawasa/envoy-proxy-demos/tree/master/jaeger-tracing
Demo2 Architecture Python app Port 8002 Port 8000 Local forwarder Node app Port 8003 Port 8008 Azure Monitor Local Forward – Application Insights Local forwarder https://github.com/microsoft/ApplicationInsights-LocalForwarder Trace Data
service-to- service communication. It’s responsible for the reliable delivery of requests through the complex topology of services that comprise a modern, cloud native application. In practice, the service mesh is typically implemented as an array of lightweight network proxies that are deployed alongside application code, without the application needing to be aware. Buoyant’s CEO William Morgan https://blog.buoyant.io/2017/04/25/whats-a-service- mesh-and-why-do-i-need-one/