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

Add bin. annotation http.path for every request #93

Closed

Conversation

pavolloffay
Copy link

Even though incoming request comes from a traced service it is not guaranteed that http.path|url|uri was added at a client side.

@jcarres-mdsol could you please review?

@jcarres-mdsol
Copy link
Collaborator

@adriancole knows more about all the other implementations out there.
The two I know more about C# and Ruby will always set the path in the client so we avoid setting it again in the server.
In what environment is this failing for you?

@@ -53,7 +53,7 @@ def annotate_plugin(env, status, response_headers, response_body)

def trace!(span, zipkin_env, &block)
# if called by a service, the caller already added the information
trace_request_information(span, zipkin_env.env) unless zipkin_env.called_with_zipkin_headers?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in a shared span (which is the current model), this will duplicate the entry (once for the client and again for the server). For many, making this change will clutter the span view and also add data with no value unless there's some proxy going on. I'm working in the java (Brave) codebase to make something like this opt-in vs required for all users.

when/if we move to a single-host model, I'd agree with this change regardless, but for now I do think it will clutter most people's span detail screen.
openzipkin/zipkin#939 (comment)

@pavolloffay
Copy link
Author

@jcarres-mdsol @adriancole thanks for feedback. I'm closing it.

@pavolloffay pavolloffay closed this Dec 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants