Adrian Cole

let's go with the simplified armeria format I think because there's little chance of api drift and easier to deal with. `user-agent: armeria/0.89.0` so.. artifact/version or.. `user-agent: zipkin-sender-okhttp3/2.10.2` @anuraaga @trustin...

first thought is to say "in addition to" as we can host both and would need to for the foreseeable future. This is also an alternative to add partitioning to...

nothing official at the moment. I did see this https://github.com/893949088/Grpc-MicroService

> > I think this issue is part of a bigger story to give more flexibility to > users to override default behaviors without having to re-code part of the...

this will also make certain practice more straightforward, such as messaging, as it eliminates the possibility of accidentally using the wrong annotations

Well yes. Sending to the v2 endpoint requires v2 encoding (json at the moment), but the v2 api style can convert to old encoding with some effort On 2 Jan...

So are you saying every trace has a specific tag (ex named namespace?) can you give an example expression and how many of these (roughly) you have?

this project is in need of more help. if you want to make a grpc example it will be nice. On Tue, Jun 23, 2020, 11:04 AM xu729963245 wrote: >...

ignoring my other comment.. deferring is certainly worth doing, independent of this issue, which I've retitled to making things disruptor based https://github.com/openzipkin/zipkin-reporter-java/pull/84

The related change out in zipkin-reporter 2.2 had much more impact in benchmark vs microbenchmark. Here's an example https://github.com/spring-cloud/spring-cloud-sleuth/pull/808