This message was deleted.
# supports
Slackbot
12/16/2022, 1:33 AMThis message was deleted.
p
Pranay
12/16/2022, 1:49 AM
@Cody Helbling are you upgrading to v0.12.0? From which version?
c
Cody Helbling
12/16/2022, 1:57 AMoh, sorry yes. upgrading to v0.12.0 from v0.11.4
p
Prashant Shahi
12/16/2022, 4:07 AMHi @Cody Helbling 👋
Could you share the steps you followed to upgrade?
Prashant Shahi
12/16/2022, 4:09 AMAlso, how is SigNoz deployed?
Is it on Docker, Swarm, or K8s?
c
Cody Helbling
12/16/2022, 5:10 AMhi @Prashant Shahi!
thanks for reaching out!
it was our dev environment so i didn't pin the dependency as i wasn't concerned w/ it breaking on updates.
running in k8s, deployed using ArgoCD.
ArgoCD would automatically update Signoz as the helm chart updated (will pin moving forward 🙂 ).
i uninstalled and reinstalled to get it working again. the bummer is we lost some configured alerting, and user accounts from the reset... but it's a dev env so not a huge deal.
i don't need help w/ it at this point, but will be more methodical about updates moving forward, and testing update in dev env first.
p
Prashant Shahi
12/16/2022, 5:17 AMIt is likely caused by older version of otel-collector and/or otel-collector-metrics.
Make sure to compare provided values in ArgoCD with the latest one from the chart.
https://github.com/SigNoz/charts/blob/main/charts/signoz/values.yaml
👍 1
Prashant Shahi
12/16/2022, 5:17 AM@Cody Helbling Thanks for sharing that re-install resolves it.
👍 1
10 Views