This message was deleted.

This message was deleted.

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 SigNoz Team, my query relates to histogram quantiles. Prior to upgrading to v0.42.0, we had a working time series panel that plotted histogram quantiles for various histogram bucket metrics, e.g.

kestrel_connection_duration_bucket

in this case. Since upgrading, these panels are showing no data (see snip below for Hist_quantile_50). In a related problem, when creating a new panel in v0.42.0 we see that SigNoz will only show the relevant aggregation functions for the given metric, e.g. "P50 by"... in the case of a histogram bucket. However, this time series also shows no data (see image below for the same

kestrel_connection_duration_bucket

metric). We can successfully plot data for the histogram count and sum metrics. Thanks for your help.

Hi team, I am experience missing traces in signoz. I was using tempo and migrating to signoz. The traces that I was able to find in tempo was not available in signoz. I use opentelemetry collector to send trace to both tempo and signoz. At the time the trace is generated, my opentelemetry collector

otelcol_exporter_send_failed_spans

was not increasing, and on signoz side, the

otelcol_receiver_refused_spans

was 0,

otelcol_receiver_refused_spans

was 0. Is there a way to trouble shoot why the span is missing?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

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