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

Document how service names are chosen in the trace summary screen #32

Open
codefromthecrypt opened this issue May 12, 2016 · 0 comments

Comments

@codefromthecrypt
Copy link
Member

We have unit tests, etc, and generally most zipkin instrumentation logs zipkin annotations.

However, we occasionally get questions by folks who aren't logging zipkin annotations, or are otherwise curious about why a service name is chosen. By documenting the algorithm, we can help them find bugs or constraints that could lead to a better understanding or experience.

openzipkin/zipkin#962

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

No branches or pull requests

1 participant