This message was deleted.

This message was deleted.

This message was deleted.

hi, i try to install Signoz using the Helm chart, and I've got this error:

{"level":"fatal","timestamp":"2024-09-12T07:38:00.777Z","caller":"signozschemamigrator/migrate.go:128","msg":"Failed to run migrations","component":"migrate cli","error":"failed to create database, err: code: 701, message: Requested cluster 'cluster' not found","stacktrace":"main.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-c │
│ ollector/cmd/signozschemamigrator/migrate.go:128\nruntime.main\n\t/opt/hostedtoolcache/go/1.21.13/x64/src/runtime/proc.go:267"}

This message was deleted.

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?

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

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.