https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
âś… 1
s
Yes, you need to upgrade the collector to 
v0.45.1-1.3
.
a
I see I was on 
0.45.1-1.1
, I think the release notes should be updated to reflect this as its a hard dependency
s
Agree, this should have been mentioned there. One of us will update it soon.
đź‘Ť 1
cc @Prashant Shahi
a
seems like my already ingested data doesn’t show up anymore for services, is there a data migration needed?
s
No, it should eventually show up.
a
hmm, i can see the spans in the signoz_spans table in clickhouse, the app is no longer sending data (this is just a test env).
Doesn’t seem like this upgrade allows to view historical services which sent data
s
What does your telemetry generation look like? Don't your application send data? If application runs and sends enough data they all show up.
p
@Alexei Zenin can you upgrade the chart to the latest one? There is a hotfix with otel ports. Follow this guide: https://signoz.io/docs/operate/kubernetes/#upgrade
a
Im using ECS, so my own Cloudfomation setup. I was sending data for a few hours with my Spring boot app this afternoon and could see all traces and services for it today before I upgraded.
p
data prior to upgrade will remain intact
a
Using this collector version: 
0.45.1-1.3
Query and frontend: 
0.10.1
Alert manager: 
0.23.0-0.2
p
yes, those are correct signoz component versions. They remain the same.
a
Not from what I am seeing in the UI, can’t see my data from this afternoon
s
And it will even show up if your application runs once after the migration
p
After you follow the upgrade guide above, you should be able to see your applications.
a
I see, thanks for the help, ill try running the application again and see if it restores access to the historical data before the upgrade. Unfortunately not familiar with helm and not using Kubernetes
@Srikanth Chekuri thanks for the suggestion, it worked and can see all previous data for the service. I think I would have expected for the historical data to be available even if the service never ran again, but this is an edge case and fine for now. It could warrant a migration if people expect this
s
Yes, the data still remains and it is generally expected that services are sending the data so it should be fine.
13 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by