A first concept of the opentracing support requested in #105.
All existing tests are currently running, but I didn't test the new functionality at all, and it likely doesn't work yet.
We introduce an abstraction layer around the opentracing tracer, as we don't want to add a hard dependency (and need only three methods).
Then the event log writer creates spans (which hopefully get their calling spans as parents), extracts the span context from them and stores it together with the rest of the event data into the database.
The event transmitter then puts it into the event metadata which is sent to Nakadi.
TODO:
[ ] write actual tests for this – both with no available tracer and a tracer as spring bean
A first concept of the opentracing support requested in #105.
All existing tests are currently running, but I didn't test the new functionality at all, and it likely doesn't work yet.
TODO: