appdash VS strace

Code Tracing Tools: Performs tracing during the execution of a computer program (Code). These tools help in tracing every line of code, the variables declared, the conditional statements used, the iterative functions, and finally deliver the expected output of the code. These are of great help in code analysis and diagnosing purposes. Some examples of Code Tracing tools are, OpenTracing, OpenZipkin, and Appdash.

There's a pretty decent set of autogenerated lists present in strace source, see e.g. https://github.com/strace/strace/blob/master/src/linux/64/io...

I guess the only way to find out is to make use of the fact that strace is OSS. https://github.com/strace/strace As I mentioned this is outside my skill level, but looking at the top level files I can see many references to output buffering so you may well be SOL.

No no noooo. Nope. Not even close. There's mountains of work down here. It's just less sexy, and less visible. There are a surprising number of ubiquitous sysutils that have very few relative github stars or whatever. Look at https://github.com/strace/strace for example. Laughably few stars compared to the flavor of the month javascript framework -- but does that mean that I can't find it on all of our *nix machines? Nope, it's on basically all of them.

Maybe taking a look at the strace source repository can help you along.

Program(Process) Tracing (ptrace) Tools: Establishes tracing operation during the execution of the application. Contains the traces of the index of instructions executed and the data referenced during execution. These are greatly used by developers for debugging purposes. Some examples of ptrace tools are, Strace, Ltrace, Opensnoop, and Valgrind Lackey.