hi, we've updated SigNoz to 0.49.1 (self hosted k8s setup, chart 0.45.2) and a link that was previously working https://<our_domain>/api/v3/query_range now drops "404 page not found". Is this a bug or during the upgrade something changed?

nothing about the endpoint changed

We tried to POST insted of GET and we got: {"status":"error","errorType":"unauthorized","error":"failed to parse jwt token: token contains an invalid number of segments"} But our Settings page doesn't have the Access Token subpage as suggested in https://signoz.io/docs/logs-management/logs-api/overview/ . We are using the CE, is this only available in Enterprise version? (somehow it was working for us until latest update)

We are using the CE, is this only available in Enterprise version?

Yes, are you sure you are not mixing the jwt token with this?

I might be mixing stuff, I don't know really, we never used the EE version, only the CE one (or the version that comes from the helm chart) and until the 0.49.1 upgrade the /api/v3/query_range link wasn't throwing a 404 error. That's why I'm trying to find out why it stopped working 🙂

It still shouldn't throw error because it is not removed.