Has anyone had much success deploying SigNoz with ...
# support
j
Has anyone had much success deploying SigNoz with ClickHouse Cloud? I’m using Helm with a fairly basic config - I’m not sure if I’m missing something super simple, but it keeps failing on the
schema-migrator
. I'm assuming it's the TCP connection as HTTP seems fine. I've tried a few different ports but haven't had any luck. overrides.yaml
Copy code
clickhouse:
    enabled: false
  externalClickhouse:
    host: XXXXX.eu-west-2.aws.clickhouse.cloud
    httpPort: 8443
    tcpPort: 9000 -- I've also tried 9440
    cluster: cluster
    secure: true
    user: default
    password: XXXX
Error from `signoz-schema-migrator`:
Copy code
Defaulted container "schema-migrator" out of: schema-migrator, schema-migrator-sync-init (init)
{"L":"info","timestamp":"2025-03-24T20:46:37.463Z","C":"signozschemamigrator/main.go:91","M":"Running migrations in sync mode","dsn":"<tcp://default:XXXX@XXX.eu-west-2.aws.clickhouse.cloud:9000>","replication":false,"cluster-name":"cluster"}
{"L":"info","timestamp":"2025-03-24T20:46:37.463Z","C":"signozschemamigrator/main.go:104","M":"Up migrations","versions":[]}
{"L":"info","timestamp":"2025-03-24T20:46:37.463Z","C":"signozschemamigrator/main.go:117","M":"Down migrations","versions":[]}
{"L":"info","timestamp":"2025-03-24T20:46:37.463Z","C":"signozschemamigrator/main.go:127","M":"Parsed DSN","optsError":"json: unsupported type: func(context.Context, string) (net.Conn, error)"}
{"L":"info","timestamp":"2025-03-24T20:46:37.464Z","C":"signozschemamigrator/main.go:133","M":"Opened connection"}
Error: failed to bootstrap migrations: failed to create dbs
failed to create dbs
dial tcp 18.134.36.146:9000: i/o timeout
Usage:
  signoz-schema-migrator sync [flags]

Flags:
      --down string   Down migrations to run, comma separated. Must provide down migrations explicitly to run
  -h, --help          help for sync
      --up string     Up migrations to run, comma separated. Leave empty to run all up migrations
a
@Joe Fairburn looks like network connectivity issue as log has timeout :
dial tcp 18.134.36.146:9000: i/o timeout
check connectivity of clickhouse endpoint from where signoz is deployed.
j
Thanks @Abhay - so I've tested ClickHouse using the
clickhouse-client
which works fine from the same deployment, I think that uses HTTP though? I'm guessing it might be related to the port - if I switch TCP to 9440 I get the same error without the timeout:
Copy code
{"L":"info","timestamp":"2025-03-25T08:10:17.859Z","C":"signozschemamigrator/main.go:127","M":"Parsed DSN","optsError":"json: unsupported type: func(context.Context, string) (net.Conn, error)"}
{"L":"info","timestamp":"2025-03-25T08:10:17.860Z","C":"signozschemamigrator/main.go:133","M":"Opened connection"}
Error: failed to bootstrap migrations: failed to create dbs
failed to create dbs
read: EOF
a
@Joe Fairburn is it similar to https://github.com/SigNoz/signoz/issues/6314
j
Ah yep @Abhay - it's the exact same error message!
n
Hey @Joe Fairburn can you checkout the steps from the following docs and let us know if you're still facing the issue: https://signoz.io/docs/operate/clickhouse/external-clickhouse/
j
Thanks @Nagesh Bansal - my setup is following the Kubernetes instructions on that page, which I'm running with Helm in Minikube. I'm using ClickHouse Cloud so I was playing around with my config a little - I think they require a secure connection.
n
Were you able to make it work?
j
Unfortunately not 😞