Skip to content

Conversation

breedx-splk
Copy link

This allows users to get access to the guts of the Zipkin OkHttpSender.Builder in order to do things like add custom headers and control compression settings, etc. The sender used in both paths (with or without disk buffering) can be impacted by this customizer.

It also includes a sample usage in the sample app.

This would ideally supersede #739. Thanks to @magdamagda for the original ideas and inspiration here.

@magdamagda
Copy link

@breedx-splk this approach will cover the functionality of #739. Thank you!
Hope it will be released soon.


package com.splunk.rum.incubating;

import zipkin2.reporter.okhttp3.OkHttpSender;

Choose a reason for hiding this comment

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

Shucks, I was hoping this might be forward-compatible if/when we move to OTLP....

Copy link
Author

Choose a reason for hiding this comment

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

Well, headers can be specified through OtlpHttpSpanExporterBuilder.setHeaders() and compression can be swizzled with OtlpHttpSpanExporterBuilder.setCompression().

These methods also exist on OtlpHttpLogRecordExporterBuilder, so I think we'll be ok.

Copy link

@johnbley johnbley left a comment

Choose a reason for hiding this comment

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

LGTM

@breedx-splk breedx-splk merged commit 47ab538 into signalfx:main Jan 31, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jan 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants