Zipkin 1.1.4

This is a patch release that fixes a bug where CASSANDRA_ENSURE_SCHEMA didn't work when the keyspace was absent. See #1128 for details

Zipkin 1.1.0

Zipkin 1.1 most notably offers improvements in the UI and the Cassandra storage component.

Zipkin UI

Thanks to @virtuald, the Zipkin UI now includes a JSON button! This allows you to see the json behind a trace diagram, something quite useful in support. For example, when people report problems in Zipkin, we often ask for json and this feature makes that easier.

@virtuald also improved error handling dramatically. Before, Zipkin wouldn't show server errors, so you'd have to use the javascript console to troubleshoot problems. Now, errors will show in pink boxes.

Cassandra Storage

Thanks to @michaelsembwever, the Cassandra schema now includes default ttls. These obviate the explicit ttls we were programmatically adding when storing each span. Those using CASSANDRA_ENSURE_SCHEMA(default) will automatically update into this. Those manually controlling the schema should run cassandra-schema-cql3-upgrade-1.txt before Zipkin 2.0 is released (unplanned).

Throttled retries when storage is down

Zipkin can start when storage is unavailable. The health check will report as unavailable until it is. Before, any activation of storage would re-attempt to connect. This has been throttled to no more than once per second to avoid thrashing the network or process with retry attempts.

Zipkin 1.0

Many of you noticed we've been working on a new dependency-light codebase for Zipkin.

Over the last 10 months we've gone beyond feature parity with the previous server, and reduced moving parts until zipkin could be deployable as a single process. The new codebase also includes new features like Elasticsearch and better metrics.

Those already using zipkin should know zipkin-java is schema, api, and environment variable compatible with the old servers. We took great care to ensure it is a drop-in.

Those worried about being first to the fire will be interested in the fact that this code has been in development for 10 months and used in production already by companies like Bouyant, LINE.me and anyone using Spring Cloud Sleuth.