Declarative option to use HttpSender and bypass agent use

[bmozaffa]

The use of HttpSender instead of UdpSender would allow the Jaeger client stack to directly send tracing data to the collector, thereby removing the need for a running agent in the application or elsewhere. Ideally, such functionality would be configurable in an environment like WildFly Swarm without the need to write code.

If the call using HttpSender can be made outside the running application thread, shielding the business code from both the lag and potential failure, it can be a viable alternative to having agents deployed.

[yurishkuro]

Extending config options (and env vars) to support http sender sounds fine to me. Are you interested in contributing this as a feature?

[yurishkuro]

Extending config options (and env vars) to support http sender sounds fine to me. Are you interested in contributing this as a feature?

[bmozaffa]

I can't commit to that yet. I'm exploring several paths and am likely to contribute some code, but as of now, the priority is on future issues that I will open!

[bmozaffa]

I can't commit to that yet. I'm exploring several paths and am likely to contribute some code, but as of now, the priority is on future issues that I will open!

[fzakaria]

I was also curious about such an option -- however the HttpSender would have to be async as to not block the current thread (i.e. queue the work to be batched on an interval on a separate thread)

[fzakaria]

I was also curious about such an option -- however the HttpSender would have to be async as to not block the current thread (i.e. queue the work to be batched on an interval on a separate thread)

[jpkrohling]

I'm closing this, as exposing the env var JAEGER_ENDPOINT is enough to get the HttpSender to be used since the client version 0.26.0.

[jpkrohling]

I'm closing this, as exposing the env var JAEGER_ENDPOINT is enough to get the HttpSender to be used since the client version 0.26.0.