How is one supposed to initialize spanFactory? about vitess HOT 4 CLOSED

The trace library we use ourselves is an internal tool, so that's why the default implementation is a no-op. I agree that it would be more useful if you could register plugins from outside the package. I'll work on that. Thanks for the suggestion!

from vitess.

@enisoc Thanks a lot! :) Is there any public implementation of this trace factory? I'll try to implement one but having a look at other implementations would make it better, at least I would know what I should take care of.

from vitess.

I don't think there's a public version of the particular trace library we use, but it should be possible to find one that can be plugged in. The main things you'd need are:

1. A plugin for this trace package, to wrap the trace creation/annotation methods provided by the trace library you use into the expected interface.
2. A plugin for golang.org/x/net/context to put/get trace spans in contexts, so spans can be passed around by only passing context (which we already do).
3. If you want to associate traces across RPCs instead of just within a given process, you'd also need a patch to bsonrpc to serialize the trace ID into the request.

from vitess.

I would suggest Twitter's zipkin (http://twitter.github.io/zipkin/). I've seen folks outside Twitter use it and the project itself seems mature.

from vitess.