Distributed Tracing Design

Designing trace topology and semantics: selecting actionable span boundaries, stable operation names, kinds, status and attributes; modelling synchronous, asynchronous, messaging, batch, retry and long-running workflows with parentage and links; and making traces usable with metrics, logs and profiles during incidents. Use when traces are noisy, fragmented, mis-parented, high-cardinality, misleading about errors, or unable to model batches and asynchronous causality. Sampling, propagation mechanics and overhead belong to opentelemetry-performance; metric cardinality to metrics-and-cardinality.

robsonkades Updated 3 repo stars

File contents

robsonkades/agent-skills commit 5d3af9c3bd

Frequently asked questions

npx get-skill add robsonkades/distributed-tracing-design