Hi there, was facing issues while setting up log exporter on my express app. I have setup a docker container for otel-collector on my node machine to push the collected logs to the signoz backend. but getting this in the logs.

exporterhelper/retry_sender.go:177      Exporting failed. Will retry the request after interval.        {"kind": "exporter", "data_type": "logs", "name": "otlp/log", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp <ip>:<port>: connect: connection refused\"", "interval": "28.45818814s"}

Have replaced ip and port with variables. I am using the basic docker-config for installing signoz on my ec2 instance. I have opened all the required ports: 3301: http, 4318: http, 4317: grpc for my EC2. Any reason I am unable to get the logs up and running.

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?

This message was deleted.

This message was deleted.

error	clickhousetracesexporter/writer.go:419	Could not write a batch of spans to model table: {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "error": "code: 252, message: Too many parts (3003 with average size of 3.22 MiB) in table 'signoz_traces.signoz_spans (10128c23-7659-4528-91e0-0979de9fe932)'. Merges are processing significantly slower than inserts"}

getting the above error continuously

Hello, I have observed a significant increase in CPU utilization after the Signoz version upgrade to v0.41.1. Additionally, we're encountering the following error in the ClickHouse pod. 2024.03.21 130442.644576 [ 1011 ] {bc235080-bd8e-4a26-99d6-69e10ec9bee9} <Error> TCPHandler: Code: 210. DB:NetException I/O error: Broken pipe, while writing to socket ([:ffff10.0.145.23]:9000 -> [:ffff10.0.129.149]:33502). (NETWORK_ERROR), Stack trace (when copying this message, always include the lines below): 0. DB:Exception:Exception(DB:Exception:MessageMasked&&, int, bool) @ 0x000000000c800f1b in /usr/bin/clickhouse 1. DB:NetException:NetException<String, String, String>(int, FormatStringHelperImpl<std:type identity&lt;String&gt;:type, std:type identity&lt;String&gt;:type, std:type identity&lt;String&gt;:type>, String&&, String&&, String&&) @ 0x000000000caa69a1 in /usr/bin/clickhouse 2. DB:WriteBufferFromPocoSocket:nextImpl() @ 0x000000000caa733e in /usr/bin/clickhouse 3. DB:TCPHandler:runImpl() @ 0x000000001292120f in /usr/bin/clickhouse 4. DB:TCPHandler:run() @ 0x0000000012933eb9 in /usr/bin/clickhouse 5. Poco:NetTCPServerConnection:start() @ 0x00000000153a5a72 in /usr/bin/clickhouse 6. Poco:NetTCPServerDispatcher:run() @ 0x00000000153a6871 in /usr/bin/clickhouse 7. Poco:PooledThread:run() @ 0x000000001549f047 in /usr/bin/clickhouse 8. Poco:ThreadImpl:runnableEntry(void*) @ 0x000000001549d67d in /usr/bin/clickhouse

This message was deleted.

This message was deleted.

This message was deleted.

Hi, I had a quick question about scaling the database (clickhouse), I've already sharded it so that it can handle the ingestion load, but now the ingest is way better but reads are slow, because the cpu and memory is always high on there. is there a way to setup read only replicas of the shards and make the query service pointed at those? cc: @Srikanth Chekuri