The upgrade of 0.52.0 to 0.53.0 failed with this error. How can I fix this? I couldn't find any other help for this problem.

✘ Container otel-migrator          service "otel-collector-migrator" didn't complete successfully: exit 1

And the log of this container is

otel-migrator          | {"level":"info","timestamp":"2024-09-04T13:17:05.624Z","caller":"migrationmanager/manager.go:76","msg":"Running migrations for all migrators","component":"migrationmanager"}
otel-migrator          | {"level":"info","timestamp":"2024-09-04T13:17:05.624Z","caller":"migrationmanager/manager.go:78","msg":"Running migrations for logs","component":"migrationmanager","migrator":"logs"}
otel-migrator          | {"level":"error","timestamp":"2024-09-04T13:17:05.713Z","caller":"migrationmanager/manager.go:81","msg":"Failed to run migrations for migrator","component":"migrationmanager","migrator":"logs","error":"clickhouse migrate failed to run, error: Dirty database version 14. Fix and force version.","stacktrace":"<http://github.com/SigNoz/signoz-otel-collector/migrationmanager.(*MigrationManager).Migrate|github.com/SigNoz/signoz-otel-collector/migrationmanager.(*MigrationManager).Migrate>\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/migrationmanager/manager.go:81\nmain.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:126\nruntime.main\n\t/opt/hostedtoolcache/go/1.21.13/x64/src/runtime/proc.go:267"}
otel-migrator          | {"level":"fatal","timestamp":"2024-09-04T13:17:05.714Z","caller":"signozschemamigrator/migrate.go:128","msg":"Failed to run migrations","component":"migrate cli","error":"clickhouse migrate failed to run, error: Dirty database version 14. Fix and force version.","stacktrace":"main.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:128\nruntime.main\n\t/opt/hostedtoolcache/go/1.21.13/x64/src/runtime/proc.go:267"}

Hi @nitya-signoz, Is it possible to collect JVM metrics directly using the

opentelemetry-javaagent.jar

installed in each Java pod, without relying on Prometheus, according to the SigNoz tutorial? Through the predefined JVM dashboard in the SigNoz repository, I see that it collects some metrics like

jvm_memory_used

, but the data does not match when I validate it by connecting directly to the pod via JMX. What other configuration should I adjust?

Hi @nitya-signoz, I want to add Haproxy load balancer in signoz-clickhouse. I have two clickhouse node (ck_1, ck_2) with password protected. Can you please guide how to add user and password in haproxy backend server?

Hey all, We currently evaluating Signoz for observability. How to export metrics and traces of Traefik to SigNoz, our Traefik is running with v2.9.6. Signoz documentation for same is for traefik version 3 or above. https://signoz.io/docs/tutorial/traefik-observability/

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.