Zipkin 1.19 includes UI and server improvements and controls in-flight requests to Elasticsearch
Our first release of the new year includes code from a couple Zipkin newcomers: Jakub and Nomy
- @jakubhava beautified the UI when json is used as a tag (aka binary annotation) value (#1458)
- @naoman fixed span merge logic (#1443) and an edge case in very large tags (#1451)
We're also lucky that Chris and Jeanneret continue to fix issues for the rest of us
- @fedj solved a couple hard-to-diagnose errors
- @cburroughs continues to pare down the UI issue backlog
We also have a new feature for Elasticsearch users (those using http to connect)
Before, we limited in-flight http connections per Elasticsearch host to 5. This is now 64 and can be adjusted by the
ES_MAX_REQUESTS variable. (#1450)
Zipkin 1.18 includes a number of UI fixes and exposes arbitrary Kafka configuration
Thanks to @cburroughs, many Zipkin UI glitches are addressed, including the ability to escape out of dialog boxes and fix the default trace view to Expand All services. Chris also reduced its minified size from 2.2 MiB to 821KiB, which will improve load performance and also reduce bandwidth usage.
Also notable in 1.18 is Kafka configuration. You can now override any Kafka consumer property using
zipkin.collector.kafka.overrides as a CLI argument or system property.
For example, to override "overrides.auto.offset.reset", you can set a prefixed system property:
$ KAFKA_ZOOKEEPER=127.0.0.1:2181 java -Dzipkin.collector.kafka.overrides.auto.offset.reset=largest -jar zipkin.jar
Thanks to our volunteers for continued improvements, and to our users for improvement suggestions.