Srikanth Chekuri

This came up in upstream discussions. This not getting picked up anytime soon.

This is a harmless one-time error when the collector bootstraps.

See https://github.com/SigNoz/signoz-otel-collector/pull/152

I imagine you are referring filestorage persistent queue and it is very much alpha. See https://github.com/SigNoz/signoz-otel-collector/pull/176, https://github.com/SigNoz/signoz-otel-collector/issues/181. This will be addressed as a part of them.

I do not think we should recommend it, but if users want to use it, they should be free to do so. Please see https://github.com/open-telemetry/opentelemetry-collector/issues/5902 and several other issues related...

This isn't a fork of the _vanilla otel-collector_ but rather a SigNoz [distribution](https://opentelemetry.io/docs/concepts/distributions/) of OTEL Collector with some changes specific to us because many of these customisations can't take part...

Can you also make it work with the `build-signoz-collector` target? I think where the binary is placed is not correct.

Also binary doesn't seem to work https://signoz-community.slack.com/archives/C01HWUTP4HH/p1686387848259869?thread_ts=1686347913.928499&cid=C01HWUTP4HH

Is there a reason for this update other than _there is a new operator version with fixes and enhancements_? ClickHouse upgrade triggers the chaos, please test in cloud environment

@prashant-shahi