There is also Zipkin, but it requires you to run additional infrastructure on EC2 and whilst it has wide range of support for instrumentation the path to adoption in the serverless environment (where you don’t have or need traditional web frameworks) is not clear to me.
Yubl’s road to Serverless — Part 3, Ops
Yan Cui

As a contributor I’m interested to hear your feedback on Zipkin.

Zipkin defines a set of HTTP headers for use in propagation and as correlation IDs so to me it seems a natural fit. You do not need to run the backend server to get the benefits of tracing, for instance one of the headers is parent ID so you can even get the causal relationships in your logs.

Here is the repo that describes the wire format: and you’ve probably already come across this but:

Show your support

Clapping shows how much you appreciated Brian Devins’s story.