Hello can we run multiple replicas of the otel collector and otel metrics collector? It will not add duplicate data to clickhouse?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hi there, first of all thanks for Signoz, it seems to be a quite nice product! I'm currently trying it on one of my kube but I stumble upon something weird. I'm following the quick start guide. I got the signoz up and running but now I'm trying to deploy k8s-infra helm in the same NS. Following the doc, I set the value as follow, but I see no error but no metrics either in signoz UI. Am I missing something obvious ? I see logs and otel metric pipeline looks good to me. (signoz-otel-collector exists and has a endpoint) [Signoz 0.75.0 / k8s-infra helm 0.12.1]

global:
  cloud: others
  clusterName: test-k01
  deploymentEnvironment: prod
otelCollectorEndpoint: signoz-otel-collector:4317
otelInsecure: true
presets:
  otlpExporter:
    enabled: true
  loggingExporter:
    enabled: false

#C01HWUTP4HH Hi everyone, I am having issues instrumenting my Node Application to Signoz cloud. After setting all the required environment variables correctly on my terminal, I got this error message "{"stack":"OTLPExporterError: Not Found\n at IncomingMessage.<anonymous> (C:\\Users\\LENOVO\\Desktop\\Reliability-Metrics-Demo\\node_modules\\@opentelemetry\\otlp-exporter-base\\build\\src\\platform\\node\\http-transport-utils.js6231)\n at C:\\Users\\LENOVO\\Desktop\\Reliability-Metrics-Demo\\node_modules\\@opentelemetry\\context-async-hooks\\build\\src\\AbstractAsyncHooksContextManager.js5055\n at AsyncLocalStorage.run (nodeasync hooks316:14)\n at AsyncLocalStorageContextManager.with (C:\\Users\\LENOVO\\Desktop\\Reliability-Metrics-Demo\\node_modules\\@opentelemetry\\context-async-hooks\\build\\src\\AsyncLocalStorageContextManager.js3340)\n at IncomingMessage.contextWrapper (C:\\Users\\LENOVO\\Desktop\\Reliability-Metrics-Demo\\node_modules\\@opentelemetry\\context-async-hooks\\build\\src\\AbstractAsyncHooksContextManager.js5032)\n at IncomingMessage.emit (nodeevents539:35)\n at endReadableNT (nodeinternal/streams/readable1345:12)\n at processTicksAndRejections (nodeinternal/process/task queues83:21)","message":"Not Found","name":"OTLPExporterError","code":"404"} " In the logs, it shows that the span is created and the application is instrumented successfully but the Traces are not exported to the Signoz cloud. Kindly help me out

#C01HWQ1R0BC Hello , I have an error after upgrade signoz. otel-migrator-sync is in error on startup. I have this log : {"L":"info","timestamp":"2024-11-26T142423.166Z","C":"schema_migrator/manager.go:861","M":"Running operation","sql":"ALTER TABLE signoz_metrics.time_series_v4_1week ON CLUSTER cluster ADD COLUMN IF NOT EXISTS attrs Map(LowCardinality(String), String) DEFAULT map() CODEC(ZSTD(1))"} {"L":"info","timestamp":"2024-11-26T142423.227Z","C":"schema_migrator/manager.go:810","M":"Updating migration entry","query":"ALTER TABLE signoz_metrics.schema_migrations_v2 ON CLUSTER cluster UPDATE status = $1, error = $2, updated_at = $3 WHERE migration_id = $4","status":"failed","error":"code: 60, message: There was an error on [clickhouse9000] Code: 60. DB:Exception Could not find table: time_series_v4_1week. (UNKNOWN_TABLE) (version 24.1.2.5 (official build))","migration_id":1000} Error: code: 60, message: There was an error on [clickhouse9000] Code: 60. DB:Exception Could not find table: time_series_v4_1week. (UNKNOWN_TABLE) (version 24.1.2.5 (official build)) Usage:.... Any idea please ? Thanks, KP

Slow performance A few days ago, I recreated my Signoz deployment from scratch. I'm now using a 3 sharded cluster / 1 replica each. Ever since I did that, Signoz is unbearably slow up to the point of timing out. How can I begin troubleshooting this?