Skip to content

Zipkin 1.11
Compare
Choose a tag to compare
@codefromthecrypt codefromthecrypt released this 12 Sep 12:37
· 2112 commits to master since this release
1.11.0
3d1d74c

Zipkin 1.11 allows you to see instrumented clients in the dependency view. It also fixes a search collision problem.

Before, the dependency view (ex http://your_host:9411/dependency) presented a server-centric diagram. This worked well enough as traces usually start at the first server. Especially with new projects like zipkin-js, client-originated traces are becoming more common. For example, the trace could start in your web browser instead of on a server. Zipkin's dependency linker is now trained to look for client send annotations in the root span, and if present, add them to the far-left of the dependency graph. Thanks to @rogeralsing for reporting.

screen shot 2016-09-12 at 6 11 38 pm

We also fixed a search bug where a query like http.method=GET matched against any service in a trace as opposed to the service specified in the UI. This affected all storage types except cassandra and is now fixed.

Note: While seemingly simple, this smoked out a latent problem in our Elasticsearch indexing template. Please re-index at your earliest convenience, or drop the index and let Zipkin recreate it.

Assets 2
Loading