Distributed tracing
5 articles in The Mesh Series by Arshad Badar Khan cover Distributed tracing.
Filter with other topics-
If you can’t prove it, it didn’t happen — audit logging in the mesh
Your service mesh is already logging every request. Method, path, status code — for free.
-
The LGTM stack for compliance evidence
Loki, Grafana, Tempo, Mimir. Four letters everyone treats as one observability blob. To a regulator they answer four different questions — and putting the wrong one in the wrong store is how evidence quietly disappears.
LGTM stackCompliance evidenceDistributed tracingMulti-cluster & residencyOpenTelemetry
-
Tracing identity through a request
You turned on distributed tracing. Grafana draws the pretty waterfall. You feel covered.
Distributed tracingLGTM stackCompliance evidenceIstioOpenTelemetry
-
Turning telemetry into signed evidence
You have the logs. That is not the same as having evidence.
Compliance evidenceSupply-chain signingLGTM stackDrift & postureMulti-cluster & residency
-
What the mesh actually costs — two curves on two axes, and the one the CFO sees
The platform lead has one slide. It says the sidecar costs about 100 millicores and 128 mebibytes per pod, multiply by your pod count, and ambient makes most of that go away. Finance nods. The slide is correct. It is also the…
Ambient meshService meshFinOps & costCompliance evidenceMulti-cluster & residency