Tap Tap, Debugging an App with your Service Mesh
summary
Linkerd is used to inspect live traffic with tap and to add route metadata with service profile so debugging requires no app changes. Tap yields JSON with headers and grpc status codes, revealing a donut vote path that returns grpc UNKNOWN and 0% success while other routes are 100%. MTLS between proxies is observed. A generated service profile from protobufs and tap for REST routes enables adding retries on a flaky authors HEAD call, improving effective success to 100% at the cost of higher latency.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:44Overview
- 2:35Check Mesh
- 2:58Troubleshoot
- 4:00Deployments
- 4:24Live Calls
- 6:08Voting Service
- 7:36Metadata
- 8:53Voting Donut
- 9:47Changing Output Format
- 11:00Service Profiles
- 12:34Web Service Profiles
- 15:41Web Service Profiles Analysis
related talks
29mDebugging an app with a service mesh
41mDebugging an Application with Service Mesh
29mObservability and Debugging Cloud-Native Apps using Linkerd & Conduit
27mService Mess to Service Mesh
20mKeynote: Service Meshes and Observability
19mSeeing the Invisible Observability with
05mLightning Talk: Locating and Debugging Failures with Linkerd...
07mGetting the most out of service mesh