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

brave: allows AsyncZipkinSpanHandler to be built with custom formats #239

Merged
merged 2 commits into from
Jan 9, 2024

Conversation

codefromthecrypt
Copy link
Member

This is needed for stackdriver and any future OTLP work, as well as developing a standard proto encoder.

* @since 3.1
*/
// AsyncZipkinSpanHandler not SpanHandler, so that Flushable and Closeable are accessible
public AsyncZipkinSpanHandler build(BytesEncoder<MutableSpan> encoder) {
Copy link
Member Author

Choose a reason for hiding this comment

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

I noticed that we can't really move off zipkin types without this, as this handler only worked with json! Will release 3.1.0 shortly afterwards.

@codefromthecrypt codefromthecrypt changed the title brave: allows AsyncZipkinSpanHandler to be build with custom formats brave: allows AsyncZipkinSpanHandler to be built with custom formats Jan 9, 2024
This is needed for stackdriver and any future OTLP work, as well as
developing a standard proto encoder.

Signed-off-by: Adrian Cole <adrian@tetrate.io>
@codefromthecrypt
Copy link
Member Author

added tests and will merge on green. Thanks for the look @anuraaga!

Signed-off-by: Adrian Cole <adrian@tetrate.io>
@codefromthecrypt
Copy link
Member Author

after this https://github.com/openzipkin-contrib/zipkin-otel can have a brave encoder and sender without dependencies on zipkin types.

@codefromthecrypt codefromthecrypt merged commit dea1650 into master Jan 9, 2024
3 checks passed
@codefromthecrypt codefromthecrypt deleted the custom-format branch January 9, 2024 06:43
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.

2 participants