Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server receive sets host explicitly #76

Open
codefromthecrypt opened this issue May 9, 2016 · 2 comments
Open

server receive sets host explicitly #76

codefromthecrypt opened this issue May 9, 2016 · 2 comments

Comments

@codefromthecrypt
Copy link

the zipkin core annotations, cs, sr, ss, cr all have the host/endpoint field to the "local" process, just like if you were making a log statement. So, if you are a client, the "cs" is you, for example.

I noticed that the serviceName is parameterized here:

Not sure this is being misused, just mentioning if the goal is to allocate who the peer is, there's a binary annotation for that, for example "sa" if you are a client and want to log who the server is.

Here's the description in the thrifts:
https://github.com/openzipkin/zipkin/blob/master/zipkin-thrift/src/main/thrift/com/twitter/zipkin/zipkinCore.thrift#L201

Here's how it works in brave:
https://github.com/openzipkin/brave/blob/fd7f09cb61861ce70a60fd0baec0b011a964c1ee/brave-core/src/main/java/com/github/kristofa/brave/ClientRequestAdapter.java#L50
https://github.com/openzipkin/brave/blob/master/brave-core/src/main/java/com/twitter/zipkin/gen/BinaryAnnotation.java#L39

Hope this helps

@levkhomich
Copy link
Owner

Interesting, zipkinCore.thrift was a lot shorter back in time. I will check these annotations and improve interop where needed.

Thank you!

@codefromthecrypt
Copy link
Author

codefromthecrypt commented May 16, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants