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 Zipkin protobuf support and remove zipkin from roadmap #295

Merged
merged 2 commits into from
Sep 2, 2019

Conversation

pavolloffay
Copy link
Member

Resolves #292

@@ -53,5 +53,5 @@ also supported). Logs are written to standard out using the structured logging l
Although we recommend instrumenting applications with OpenTracing API and binding to Jaeger client libraries to benefit
from advanced features not available elsewhere, if your organization has already invested in the instrumentation
using Zipkin libraries, you do not have to rewrite all that code. Jaeger provides backwards compatibility with Zipkin
by accepting spans in Zipkin formats (Thrift or JSON v1/v2) over HTTP. Switching from Zipkin backend is just a matter
by accepting spans in Zipkin formats (Thrift, JSON v1/v2 and Protobof) over HTTP. Switching from Zipkin backend is just a matter
Copy link
Contributor

Choose a reason for hiding this comment

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

"Protocof" -> "Protobuf"

Signed-off-by: Pavol Loffay <[email protected]>
@pavolloffay pavolloffay merged commit 4ce5672 into jaegertracing:master Sep 2, 2019
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.

Update Zipkin related docs in v1.14
2 participants