This message was deleted.

Hi, i am trying to run signoz in an lxc container. When i start the containers, the "signoz-clickhouse" container fails to start with:

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 6: operation not permitted: unknown

i dont really understand why this is happening, as docker itself is running just fine, and other docker-container run just fin on this configuration. Can someone tell me what i am doing wrong?

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.

This message was deleted.

Hello, my schema migrator seems to contiiously fail lately with the following errors

{"L":"info","timestamp":"2024-12-16T12:21:24.682Z","C":"schema_migrator/manager.go:393","M":"Waiting for mutations to be completed","count":1,"host":"10.244.1.54:9000"}
{"L":"info","timestamp":"2024-12-16T12:21:24.682Z","C":"schema_migrator/manager.go:395","M":"Mutation details","database":"signoz_logs","table":"schema_migrations_v2","command":"UPDATE status = 'finished', error = '', updated_at = '2024-12-16 12:15:13' WHERE migration_id = 4","mutation_id":"0000000003","latest_fail_reason":""}
{"L":"info","timestamp":"2024-12-16T12:22:31.353Z","C":"schema_migrator/manager.go:393","M":"Waiting for mutations to be completed","count":1,"host":"10.244.1.54:9000"}
{"L":"info","timestamp":"2024-12-16T12:22:31.353Z","C":"schema_migrator/manager.go:395","M":"Mutation details","database":"signoz_logs","table":"schema_migrations_v2","command":"UPDATE status = 'finished', error = '', updated_at = '2024-12-16 12:15:13' WHERE migration_id = 4","mutation_id":"0000000003","latest_fail_reason":""}

This message was deleted.

I'm trying to scrape application pod (prometheus) metrics using the k8s-infra chart. I've not been able to find much documenation, but I note that the following configuration exists https://github.com/SigNoz/charts/blob/main/charts/k8s-infra/values.yaml#L349-L352 , which is briefly being discussed at https://community-chat.signoz.io/t/8493962/hi-team-i-ve-installed-signoz-via-helm-chart-initially-there. Setting those labels on my pod exposing a prometheus page doesn't seem to get picked up though. Has anyone successfully scraped prometheus metrics with the setup in the k8s-infra chart?

This message was deleted.