jason plumb

I think @rmfitzpatrick has solved it. Please reopen if this doesn't work for you @carlosalberto.

@nevenamanova are you able to use native otel OTLP exporter to send to jaeger instead?

Yeah, I believe that there are several APIs that are basically now in a bad/broken state -- you can't POST a new entity without an ID (you'll get a 400)...

@hecomp This issue looks stale and the example linked above has been closed as well. Please reopen if this is still a concern. Thanks.

Hey @carlosalberto -- this issue has been around for a while, and I think everything that's been linked to has been merged. Is there anything else actionable on this, or...

Resurrecting an old issue here....surprised that we hadn't ever hashed this one out. I was looking at the `Content-type` for an OTLP HTTP request from Java instrumentation today and saw...

@serrodcal Thanks, can you help us understand specifically which exporters and which HTTP senders you'd like to target with this?

+1 yeah this sounds like a solid approach to me as well. I'm confident that users will ask for user/pass in short order, but I'm also confident that will be...

> Not producing broken traces. tracerC:client:grandchild's parent should be tracerA:server:parent, not tracerB:internal:child. Something that hadn't occurred to me until reading this just now, is that maybe there's an argument to...

OpenTelemetry uses [16-byte trace IDs and 8 byte span IDs](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spancontext), which is consistent with the [w3c trace context](https://www.w3.org/TR/trace-context/#trace-id) format for its default trace context propagation mechanism. If you are using...