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

Hi, Retention period seems to have reset to default values for some reason. We have set Retention Period following docs @ https://signoz.io/docs/userguide/retention-period/ We set this months ago when we initially installed Signoz as it is recommended to set retention period early in the lifecycle of the platform. In sqlite signoz.db we can see the values: 54 c2da421ae3ae4c1197e0b7ee05377176 2024-03-28 133806.07271329+00:00 2024-03-28 133806.456254169+00:00 signoz_metrics.samples_v2 31104000 604800 success After 7 days(604800) move to S3 cold storage for 1 year(31104000). We have done this for Metrics, Traces and Logs. Since this time(back in March) we have done a number of upgrades of SigNoz and have just noticed there is a change to our Metrics retention period. It is now showing as 1 month and no cold storage setting. See attached image What would have caused this to have changed and why did it only do it for Metrics and not all(Traces and Logs also)? Also we now have months of metrics data, will there be an issue with us changing the retention now?

This message was deleted.

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.

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 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.

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?

This message was deleted.

This message was deleted.