2022/11/02 102124 collector server run finished with error: failed to get config: cannot unmarshal the configuration: unknown exporters type "clickhouselogsexporter" for "clickhouselogsexporter" (valid values: [awsemf clickhouse honeycomb newrelic opencensus prometheusremotewrite skywalking sumologic alibabacloud_logservice file splunk_hec awsprometheusremotewrite awsxray f5cloud jaeger logging prometheus signalfx awskinesis elasticsearch googlecloud kafka logzio sapm zipkin carbon humio loki stackdriver tencentcloud_logservice azuremonitor clickhousemetricswrite datadog dynatrace elastic jaeger_thrift loadbalancing otlp otlphttp parquet influxdb sentry tanzuobservability])

What version are trying to upgrade from and which version is giving this error?

@Ashna From the above logs, it's likely that you are trying to downgrade SigNoz using OtelCollector config of latest release.

Hi,Please find the below versions I am using signoz/frontend:0.9.0 signoz/query-service:0.9.0 signoz/otelcontribcol:0.43.0-0.1 clickhouse/clickhouse-server:22.4-alpine

If you are using older version, you should use older Chart version (or git checkout to release tag/branch) as well.

While Trying to upgrade with old volumes its not reflecting in the latest version

can you share how are you upgrading?

upgrade from 0.7.1 to 0.11.1

you would have to incrementally upgrade across the versions with breaking changes and run the migration scripts

Hi , I tried to upgrade to 0.8.0 from 0.7.2 and changed to these below values Alertmanager 0.23.0-0.1, OtelCollector 0.43.0-0.1

The Helm chart and the OtelCollector configuration you are using is for v0.11.x while you are using SigNoz version v0.9.x

Okay

old data can only be retained if you follow the step-by-step upgradation and run migration script

By while doing step by step migration I am getting the error that I shared yestrday

I don't think you are pointing

helm

to correct chart versions.

Hi,

Oh, I see. That means you would have to

git checkout

to release branch or tag of each breaking changes incrementally and also run the migration scripts.

Hi

That flag was removed long back.

I was following the same steps that you have mentioned in the document

can you please make sure that you do not have any local changes in the otel-collector config or docker-compose YAML?

hi

Hi @Ashna 👋 How can I help you?

While connecting to grpc using nginx we are getting the below error. Please have a check. [error] 30#30: *1 upstream rejected request with error 1 while reading response header from upstream, client: , server: , request: "GET /favicon.ico HTTP/1.1", u