Hi Team,, I recently started noticing Page not found in traces, When i checked the collector pod logs, i get

{"level":"warn","ts":1724310180.336868,"caller":"signozspanmetricsprocessor/processor.go:1176","msg":"Too many operations to track, using overflow operation name","kind":"processor","name":"signozspanmetrics/delta","pipeline":"traces","maxNumberOfOperationsToTrackPerService":2048}
{"level":"warn","ts":1724310180.5888464,"caller":"signozspanmetricsprocessor/processor.go:1176","msg":"Too many operations to track, using overflow operation name","kind":"processor","name":"signozspanmetrics/cumulative","pipeline":"traces","maxNumberOfOperationsToTrackPerService":2048}

What can I do to fix this issue.

Hello, I am trying to deploy Signoz in AWS EKS cluster, How to pass SMTP HOST, PORT, AUTh information to Helm chart?

This message was deleted.

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.

Hi team- I'm experimenting with signoz right now, and trying to get it stood up in k8s using the helm chart. We already use clickhouse, so I was seeing if I could just attach to that installation rather than having signoz spin up a new one. After some adjustments, I've gotten many things to spin up and run correctly, including the schema migration tool. However, the query service raises an error:

error connecting to primary db: code: 516, message: signoz: Authentication failed: password is incorrect, or there is no user with such name.

More details in 🧵 ... any help is greatly appreciated! UPDATE: fixed ... 1. quick workaround: don't use

+

chars in the password for credentials signoz uses to connect to the external instance. specifically the query service uses a URL format, and passwords are not properly url-encoded, so `+`'s turn into spaces according to the url. 2. https://github.com/SigNoz/charts/issues/473

This message was deleted.

This message was deleted.

This message was deleted.