search

SigNoz / signoz

SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
https://signoz.io
Other
19.5k stars 1.32k forks source link

After update to v0.57.0, the front end remains at v0.56.0. #6335

Open fcpimenta opened 3 weeks ago

fcpimenta commented 3 weeks ago

Bug description

After update to v0.57.0, the front end remains at v0.56.0.

Please describe.
If this affects the front-end, screenshots would be of great help.

Expected behavior

You expect to see the correct version on the dashboard, as with other versions.

image

How to reproduce

Do the normal installation:

  1. git checkout main
  2. git pull origin main
  3. cd deploy && ./install.sh

Version information

Additional context

Thank you for your bug report – we love squashing them!

prashant-shahi commented 2 weeks ago

not able to reproduce the error

$ git status
On branch main
Your branch is up to date with 'origin/main'.
$ curl localhost:3301/api/v1/version

{"version":"v0.57.0","ee":"Y","setupCompleted":false}
prashant-shahi commented 2 weeks ago

can you share the output of docker ps and the latest git commit hash?

fcpimenta commented 2 weeks ago

Hi Prashant,

I've got a clue.

When checking the branches, I saw that up until release v.0.55, there was only one docker compose file (signoz/deploy/docker/clickhouse-setup/docker-compose.yaml). Starting with v.0.56, two new files appeared (signoz/deploy/docker/clickhouse-setup/docker-compose-minimal.yaml and signoz/deploy/docker/clickhouse-setup/test-app-docker-compose.yaml).

When upgrading, it seems that my docker compose file is not overwritten and is stucked at v0.56. I have not seen any information about this change.

How should I fix it?