On Fri, Dec 30, 2016 at 06:37:47PM +0100, Domagoj Stolfa wrote: > Hello, > > I have been working on extending DTrace to allow for a natural way of tracing > in > a distributed environment. This would consist of being able to trace events on > different virtual machines, remote servers with access, cluster nodes and so > on. > I will summarize the changes I have made and have thought of making, outly all > the design tradeoffs, flaws and merits of each design tradeoff I have thought > of > making in hopes of getting feedback from others interested in distributed > tracing.
I think some concrete examples of what you'd like to be able to accomplish with this would help a lot. Is the goal here to be able to trace multiple independent systems at once and somehow aggregate their trace records? That's what "distributed tracing" suggests to me, but from reading your email it seems as though you're primarily interested in some form of remote tracing whereby one could execute something like # dtrace -n 'fbt$guest::kern_ioctl:entry' on a hypervisor and get records (in real time?) from a guest. Assuming I'm not completely off-base, this is a cool idea, but I think your objective needs to be more clearly defined before it's possible to evaluate the merits of different designs, especially when you're proposing adding new concepts to the core DTrace code. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "[email protected]"
