This message was deleted.

I got this error. Does anyone know how to fix it. Thanks.

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.

This message was deleted.

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?

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":""}

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.

This message was deleted.

I am confused about the instructions for sending host metrics from an external linux host to Signoz. Do I need to enable the prometheus configuration on both the signoz server and the linux host, then configure the signoz server to scrape the available endpoint? Or is is possible to send the metrics via the OTLP connections (GRPC or HTTP)? [10:17 AM] Rajeev https://signoz.io/docs/userguide/send-metrics/#metrics-from-hostmetrics-receiver SigNoz Send Metrics to SigNoz (Self Hosted) Learn how to send metrics to self-hosted SigNoz using OpenTelemetry. Follow detailed steps to enable and configure metric receivers. [10:17 AM] Rajeev Can someone please advise?

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?