Error with ClickHouse Cluster Name in SigNoz-Otel-Collector

TLDR Shreyash encountered an error related to hardcoded ClickHouse cluster name. Romil suggested renaming the cluster to "cluster" to fix the issue.

Photo of Shreyash
Shreyash
Thu, 23 Feb 2023 15:41:17 UTC

hii , Anyone having idea about the below error? ```kubectl logs signoz-release-otel-collector-metrics-995696d7b-f7m27 --namespace platform Defaulted container "signoz-release-otel-collector-metrics" out of: signoz-release-otel-collector-metrics, signoz-release-otel-collector-metrics-init (init) 2023-02-23T15:37:37.461Z info service/telemetry.go:111 Setting up own telemetry... 2023-02-23T15:37:37.461Z info service/telemetry.go:141 Serving Prometheus metrics {"address": "0.0.0.0:8888", "level": "Basic"} 2023-02-23T15:37:37.462Z info components/components.go:30 Stability level of component is undefined {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite/hostmetrics", "stability": "Undefined"} time="2023-02-23T15:37:37Z" level=info msg="Executing:\nCREATE DATABASE IF NOT EXISTS signoz_metrics ON CLUSTER cluster\n" component=clickhouse```

Photo of nitya-signoz
nitya-signoz
Thu, 23 Feb 2023 16:16:28 UTC

This are all `info` logs, any issue that you are facing ?

Photo of Romil
Romil
Thu, 23 Feb 2023 16:30:22 UTC

i got this too on my install yesterday, it seems that using `cluster` is hardcoded in the code, you have to rename your clickhouse cluster to `cluster` to work

Photo of Romil
Romil
Thu, 23 Feb 2023 16:31:28 UTC

Photo of Romil
Romil
Thu, 23 Feb 2023 16:35:35 UTC

nitya-signoz this particular info log crashes the collector

Photo of nitya-signoz
nitya-signoz
Fri, 24 Feb 2023 03:51:28 UTC

Romil are you using a different/existing clickhouse cluster?