My use case is for understanding a closed source application which has a number of separate pieces. Since I don't have the source code, these don't look like viable options.
Dapper will follow the call path of an RPC and report the details of it.
http://static.googleusercontent.com/media/research.google.co...
However, lightweight cross-component dynamic instrumentation that correctly captures causality is still an open research problem. This is actually something I have done some work on recently in my system Pivot Tracing[1] which won a best paper award at the conference it was presented at (SOSP). Pivot Tracing combines dynamic instrumentation with causal tracing in order to address precisely the problem you describe. The code for the system is open source and available on GitHub[2].
For example, a request hits the web server, the web server tickles an application server, the application server makes a number of database queries, and the results propagate back the way they came.
I'd love to see something that could follow this request through all of the layers and across all of the machines, without the luxury of having the source code for most of the components.
I don't see why this wouldn't be possible, but I certainly see why it wouldn't be EASY!