This message was deleted.

This message was deleted.

Hi. We are playing around with external clickhouse setup (every other part of signoz runs on k8s), latest version of chart (0.56.2, signoz 0.58.2). When we use the default clickhouse user with empty password: externalClickhouse: host: 10.10.10.10 user: default password: "" everything works correctly, signoz deployment finishes, schema-migrator completes. But when we setup a password for the default user: user: default password: yyyy or password: "yyyy" or password: 'yyyy' schema migrator seems to complete part of migrations but then fails and goes into CrashLoopBack and timeouts with this error:

Error: failed to run squashed migrations: failed to run squashed migrations

code: 516, message: Received from 10.10.10.10:9000. DB::Exception: default: Authentication failed: password is incorrect, or there is no user with such name.

If we change the user, delete the deployment and helm install fresh - same situation, same error. We use the default clickhouse ports (8123, 9000) so we don't setup them in the yaml file. Connecting locally or externally to clickhouse instance on 10.10.10.10 with the default user or the other user and providing yyyy password - works without any issues. Any idea what we are doing incorrectly?

Hello, I'm trying to work on the Alertmanager for this issue: https://github.com/SigNoz/signoz/issues/5095. I installed Go version 1.22.5 (linux/amd64), but when I execute "make," I get an error related to the Go version.

Hello, I have added a custom resource attribute to my traces via the sidecar collector:

resource/k8s:
        attributes:
          - key: test.foo
            value: bar
            action: insert
          - key: k8s.cluster.name
            from_attribute: k8s-cluster
            action: insert
          - key: k8s.namespace.name
            from_attribute: k8s-namespace
            action: insert

I can use that resource attribute to filter in the Traces area of Signoz, but the Services area will not show it as a filter option - only the signoz collector id shows up as filterable. Any ideas on why it wouldn't be allowing the Service filter on another but the collector id even thought the data is there and filterable in the traces area?

This message was deleted.

This message was deleted.

Hello, Does anyone have metrics on CPU requirements based on the number of requests per second? Our installation has 8 cores and is receiving around 150 requests per second, the CPU sits around 100% and we are dropping a number of requests. https://www.restack.io/docs/signoz-knowledge-signoz-hardware-requirements

CPU: The minimal CPU requirement is 4 cores. To ensure smoother operation and to accommodate higher workloads, 8 cores are recommended.

850979 101       20   0   44.0g   1.7g  62076 S 471.2  17.7  29208:00 clickhouse-serv
1592062 root      20   0 7168288   4.2g  93568 S 301.7  44.0   3:18.29 signoz-collecto

Any details on upper limits would be helpful.

This message was deleted.

This message was deleted.