This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello, I've noticed numerous warnings in my collector logs stating

Too many operations to track, using overflow operation name

. Could someone please advise on how I might resolve this issue? Thank you

Hi devs, I've installed Signoz using helm on a local minikube cluster and deployed a simple instrumented express app to the same cluster. Services and traces form the app are visible in the Signoz UI. The docs say "When you deploy SigNoz to your kubernetes cluster it will automatically start collecting all the pod logs." Is there some additional setup needed to get the logs coming in, as I'm not seeing anything out of the box? Thanks

Hello Everyone, I am already using a self-hosted signoz for tracing, now i want to get a metrics of my different back-ends, and my back-ends is running on GKE (Google Kubernetes Cluster), I have Kafka, Redis, CockroachDb, Solr in my backends, I want to get CPU, Memory Usage Metrics and Healthcheck Metrics of this. So how can i do that? @Prashant Shahi

Hi Team, as we tried to upgrade signoz with chart version 0.44.1 to 0.45.3 we had migration issue for click house, any help would be much appreciated, Thank you

{"level":"fatal","timestamp":"2024-07-19T14:30:17.010Z","caller":"signozschemamigrator/migrate.go:128","msg":"Failed to run migrations","component":"migrate cli","error":"clickhouse migrate failed to run, error: Dirty database version 10. Fix and force version.","stacktrace":"main.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:128\nruntime.main\n\t/opt/hostedtoolcache/go/1.21.11/x64/src/runtime/proc.go:267"}