Open codeboten opened 4 years ago
With each exporter contained within BatchSpanProcessor
which has its own queue, isn't this the case already? So you just create multiple exporters?
I agree. We can consider using multiple processor each with it's own instance of OTLP exporter as a solution for this. Looks like the spec just recommends having one queue per destination which would be satisfied by such a setup. There's no point in re-implementing BatchSpanProcessor's queue inside the exporter IMO.
If we agree with this, this should just be a small documentation change.
Using multiple exports+processors does probably not technically satisfy the spec as the spec clearly talks about multi-destination exporting in the context of OTLP exporter but still, we can still recommend wrapping multiple OTLP exporters with different processors to achieve the same result. I realize it may not truly satisfy the spec but it addresses the problem the spec is trying to solve in a rather elegant way without adding too much logic/responsibility to the exporter.
@owais I agree. The less changes we make the better. So this will just simply be a doc change then to instruct users to go that route to solve this usecase?
This issue was marked stale due to lack of activity. It will be closed in 30 days.
I somehow missed your comment @lzchen. Yes, I think we should document "how to export to multiple destinations" and it should cover using different exporters or multiple instances of same exporter.
As per spec: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/protocol/otlp.md#multi-destination-exporting