Contributing otel-collector as an Exporter to OpenTelemetry Collector Contrib

[haihh05]

I hope you're doing well. I'm curious why it hasn't been contributed as an exporter to the OpenTelemetry Collector Contrib project (https://github.com/open-telemetry/opentelemetry-collector-contrib).

Contributing your otel-collector to OpenTelemetry Collector Contrib could offer several benefits, including increased visibility, community-driven enhancements, and wider adoption. I would appreciate any insights you can provide on the decision to maintain the otel-collector separately and whether there are specific considerations involved.

Thank you for your time and any information you can share on this matter.

[ocraviotto]

I'd like to echo this request, as having the exporter being available as part of the OpenTelemetry Collector would make users' lives easier when already using the collector.

[lmangani]

Thanks for bumping this! We're planning around this problem, but first we need to explore any opportunity to extend the existing clickhouse exporter to maximize the potential also in terms of future maintenance. If that's not possible, we'll most definitely go ahead and join the contrib circle with our exporter.

Note: With the loki receiver working, the contrib represents a full replacement for the qryn-js ingestion pipeline.