I noticed that signoz deploys a custom otel collector https://github.com/SigNoz/signoz-otel-collector This collector has exporters for clickhouse but doesn't have many of the other exporters/processors/receivers that otel contrib has. The otel contrib collector has a clickhouseexporter https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/clickhouseexporter Is there a reason why signoz doesn't use otel contrib? Is it possible that I can use otel contrib to send data to clickhouse instead of the signoz custom collector?

Hey @Gage Miller ! The SigNoz distro of OTel collector works just like the normal OTel collector. What use-case are you trying to solve ? Are you not able to solve it using the SigNoz OTel collector ?

@Chitransh Gupta I need to use exporters and processors that are not inside of the signoz distro of otel such as AWS xray.

Is there a reason why signoz doesn't use otel contrib? Is it possible that I can use otel contrib to send data to clickhouse instead of the signoz custom collector?

Because SigNoz maintains it's own ways of writing and working with the data. SigNoz schemas evolve based on our learnings and experiments.

Put another way - I guess the ask is - what is the plan on syncing your fork with the new things in the contrib repo ?