#support

Troubleshooting Signoz Instance on Azure

TLDR Nicolai encountered errors when setting up a Signoz instance on Azure using an external Clickhouse instance. Nocnica suggested a test ping.

Powered by Struct AI

1

Oct 31, 2023 (1 month ago)
Nicolai
Photo of md5-65498b9bc5ffb73ba57e2b3fba9a6b7d
Nicolai
04:23 PM
Hey 🙂

I'm trying to spin up a Signoz instance on Azure - Using an external Clickhouse instance.

I'm getting the following error in the signozschemamigrator:

{
    "level": "fatal",
    "timestamp": "2023-10-31T16:03:57.316Z",
    "caller": "signozschemamigrator/migrate.go:79",
    "msg": "Failed to create migration manager",
    "component": "migrate cli",
    "error": "failed to parse dsn: parse \"tcp://<redacted>.aws.clickhouse.cloud:%!s(float64=9000)?username=default&password=<redacted>\": invalid port \":%!s(float64=9000)\" after host",
    "stacktrace": "main.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:79\nruntime.main\n\t/opt/hostedtoolcache/go/1.20.10/x64/src/runtime/proc.go:250"
}

04:23
Nicolai
04:23 PM
I've set the port in the Helm Chart values to 9000.
04:46
Nicolai
04:46 PM
I figured it out - Port had to be a string.

New issue - it fails to ping the clickhouse instance.
I'm using Clickhouse Cloud - any suggestions?
Nocnica
Photo of md5-7d3e7e5883af6e145e90d5d5a7a25acf
Nocnica
07:25 PM
I felt so smart noticing (float64=9000) but it looks like you figured out that bit,

does a test ping to your clickhouse cloud instance succeed?

1

Nicolai
Photo of md5-65498b9bc5ffb73ba57e2b3fba9a6b7d
Nicolai
07:26 PM
Do you mean a simple ping from the command line on my pc?
Nocnica
Photo of md5-7d3e7e5883af6e145e90d5d5a7a25acf
Nocnica
07:27 PM
yeah, like, is the instance available at :9000 ?