Fixes breaking changes Thrift

Upcoming Thrift release has some significant changes to generated code. We follow the master branch, so this one will bring it up to date with latest breaking changes.

Tags values as strings

This brings the package more in-line with the upcoming Zipkin V2.

It treats all tag values (binary annotations) as string. This also fixes the issue of not being able to query items that have been annotated as non string values in the Zipkin UI.

Release 0.3.0

• Adds OpenTracing Observer interface
• Updates Thrift to code compatible with 0.11.0 (Go context aware code)

various improvements and fixes

This release contains a couple of bugfixes and updates to improve interop with Zipkin V1 and HTTP collector transport details

• examples have been updated to use Go stdlib context as we now support Go 1.8+
• ability to set your own http.Client for the HTTP Collector
• bugfixed 128 bit trace id propagation serialization
• HTTPRequestCallback allows one to adjust the HTTP request (ex. add authorization header) before the HTTP Collector sends it off to Zipkin.
• added parentSpanID propagation test
• ClientServerSameSpan option now defaults to true as this is Zipkin V1 idiomatic

Many thanks to @primalmotion and Nathan West for contributing to this release.

HTTP Collector fixes

HTTP Collector could block under stress and/or slow uplink.

Improved KV Log handling and transporter queue flush on shutdown

Improvements to our HTTP and Kafka transporters. We now properly flush queues on shutdown not needing to arbitrarily wait for it to happen at shutdown time, most notably when used in short lived CLI like applications.

Next to the JSON serialization of KV Log objects we can now serialize to LogFmt strings and even Zipkin strict materialization.

Zipkin Strict materialization will only release a Zipkin Annotation distilled from an array of OpenTracing Log fields if we have a Log field with an "event" key which in OpenTracing terminology is a "common field" to be used as: "A stable identifier for some notable moment in the lifetime of a Span". This maps properly with Zipkin's concept of an Annotation and is easily created using the LogEvent method on an OpenTracing span.

Improved span timestamp and duration logic

To adhere to best practices the tracer will not report timestamp and duration in clientServerSameSpan mode for server side spans that have an existing client side counterpart.

128-bit traceID support

This release adds support for 128-bit TraceIDs.

• Tracer can be switched to 128-bit or 64-bit trace generation
• Works transparently with 128-bit and 64-bit traces originating from other instrumenting libraries
• Example shows 128-bit tracing in action.

First Release

First Release of zipkin-go-opentracing with the following feature set:

• Support for OpenTracing API release 1.0.0
• HTTP & gRPC B3 Propagation
• Dual host (Zipkin V1 style) and single host spans (OpenTracing style)
• Sampling
• HTTP, Kafka & Scribe Collectors