Hi Team, I have successfully deployed SigNoz on K...
# support
v
Hi Team, I have successfully deployed SigNoz on Kubernetes and created several dashboards and alerts. I now need to replicate these dashboards and alerts in another account. Despite attempting to use the SigNoz query database backup and restoration process, the dashboards appear without any data. Could you please guide me on how to achieve this migration effectively? Any detailed steps or documentation would be greatly appreciated.
n
the dashboards appear without any data.
Do you mean the dashboards are not present or the dashboards are not rendering any data ? If it’s the second one is the data getting ingested there ?
v
@nitya-signoz, All dashboards are present but there is no data into them.
getting this log in signoz-infra-otel-collector kind":"exporter","data_type":"logs","name":"clickhouselogsexporter","error":"StatementSendcode 243, message: Cannot reserve 1.00 MiB, not enough space","interval":"6.621795521s"} {"level":"info","ts":1741078257.7023506,"caller":"internal/retry_sender.go:118","msg":"Exporting failed. Will retry the request after interval.","kind":"exporter","data_type":"logs","name":"clickhouselogsexporter","error":"StatementSendcode 243, message: Cannot reserve 1.00 MiB, not enough space","interval":"6.722909985s"} {"level":"error","ts":1741078257.7687016,"caller":"internal/base_exporter.go:153","msg":"Exporting failed. Rejecting data.","kind":"exporter","data_type":"logs","name":"clickhouselogsexporter","error":"sending queue is full","rejected_items":66,"stacktrace":"go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*BaseExporter).Send\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.111.0/exporterhelper/internal/base_exporter.go:153\ngo.opentelemetry.io/collector/exporter/exporterhelper.NewLogsRequestExporter.func1\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.111.0/exporterhelper/logs.go:136\ngo.opentelemetry.io/collector/consumer.ConsumeLogsFunc.ConsumeLogs\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/consumer@v0.111.0/logs.go:26\ngo.opentelemetry.io/collector/processor/batchprocessor.(*batchLogs).export\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/processor/batchprocessor@v0.111.0/batch_processor.go:526\ngo.opentelemetry.io/collector/processor/batchprocessor.(*shard).sendItems\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/processor/batchprocessor@v0.111.0/batch_processor.go:277\ngo.opentelemetry.io/collector/processor/batchprocessor.(*shard).startLoop\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/processor/batchprocessor@v0.111.0/batch_processor.go:237"} {"level":"warn","ts":1741078257.768784,"caller":"batchprocessor@v0.111.0/batch_processor.go:279","msg":"Sender failed","kind":"processor","name":"batch","pipeline":"logs","error":"sending queue is full"}
n
check disk space for clickhouse
v
Thanks @nitya-signoz, It is resolved now, disk was full and signoz.db was corrupted, so increased the disk size of click house and restore the latest backup.