opentracing-go

The Go standard library has most of what you need for basic API servers. However as has been stated here, some things are not worth spending time crafting yourself. Also for modern Docker/Kubernetes ops environments you need some additional infrastructure for table stakes. Here's my standard Nulladmin.com stack: Routing - https://github.com/go-chi/chi Command flags - https://github.com/spf13/pflag Config - https://github.com/spf13/viper Logging - https://github.com/Sirupsen/logrus Metrics - https://github.com/prometheus/client_golang/prometheus SQL helper - https://github.com/jmoiron/sqlx OpenTracing - https://github.com/opentracing/opentracing-go

I think what you're looking for is Zipkin [0]. We use it in our microservers at Nulladmin.com via the opentracing Go library [1] and the zipkin-go-opentracing library [2] [0] https://github.com/openzipkin/zipkin [1] https://github.com/opentracing/opentracing-go [2] https://github.com/openzipkin/zipkin-go-opentracing

Before Jaeger was out I started using this, although I'm considering switching over to using Jaeger: https://github.com/opentracing/opentracing-go It should be pretty clear how to use it once you read through the examples. Jaeger requires using Cassandra as a datastore (for now), which isn't easily supported at my company, so I went with Zipkin and used MySQL as a datastore.

Mm it's a little sparse right now - had to dig into the opentracing spec, dig in to the implementations and make it piecemeal. OpenTracing is for everyone - both tracing implementors (eg. Jaeger engineers) and for you implementing tracing in your system. As an implementor in your system you mainly care about the "vocabulary" and "standards" opentracing defines. So, if you've got two functions (A which calls B) opentracing defines: - Syntaxes to say that the span for "B" is a "childOf" "A". This gives you the graph I had above. - Syntaxes to attach errors and other information to spans in a standard way (this lets any opentracing-compatible UI display/search errors etc): https://github.com/opentracing/specification/blob/master/sem... OpenTracing also allows you to define functions that follow each other: https://github.com/opentracing/