Hi team! I upgraded Signoz from version 0.54 to 0....
# support
к
Hi team! I upgraded Signoz from version 0.54 to 0.75 and am encountering an issue: I don't see traces for some endpoints, even though the endpoints appear in "Key Operations."
image.png,image.png
Everything worked fine on version 0.54. The update was performed by completely removing the old version and deploying the new one from scratch.
p
@Nagesh Bansal do you have any suggestions here?
n
Hey @Кирилл Алтухов, can you please try with the migration guide for upgrading to version >0.70: https://signoz.io/docs/operate/migration/upgrade-0.70
n
As Nagesh mentioned you will have to run the migrations, and you will have to run them in order v0.55, 0.64, 0.70 . https://signoz.io/docs/operate/migration/
к
Hi @Nagesh Bansal! I don't need migration, because I have deleted signoz 0.54 with all data and have installed 0.75
Can it be related with count of traces? the endpoint which don't have info have a lot of DB calls
It looks like there's an issue with building filters in the Explorer tab. For example: In Key Operations, I have an endpoint with the name
"GET api/v20/aggregate/accounts/(?P<_uid>[^/.]+)/$"
. When I click on the name, the Explorer tab opens. In this tab, I have an enabled filter:
"name IN GET api/v20/aggregate/accounts/(?P<_uid>[^/.] )/$"
. However, in this filter, the
+
symbol is replaced with a space. If I modify the filter to
"name IN GET api/v20/aggregate/accounts/(?P<_uid>[^/.]+)/$"
, everything works as expected, and the data is displayed correctly.
n
Hey @nitya-signoz, can you help @Кирилл Алтухов for this
n
Let us get back to you on this.
@Shaheer Kochai
s
will check it out and update the thread
n