chore: update query service telemetry

[makeavish]

And add new distination for saas telemetry

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[ankitnayan]

Since we are removing /api/v2/metrics/query_range altogether rather than adding /api/v3/query_range, we would be losing analytics for those.

[ankitnayan]

Since IdentifyUser is not called on query-service restarts, the SetUserEmail and SetCompanyDomain won't be called there. SetCompanyDomain was hence called separately at InitializeOrgpreferences at

signoz/pkg/query-service/dao/sqlite/connection.go

Line 145 in cb155a1

telemetry.GetInstance().SetCompanyDomain(users[countUsers-1].Email)

So, restart of the query-service will cause no events to be sent any further due to check at https://github.com/SigNoz/signoz/pull/3735/files#diff-8a30fc5d1386f1d6463d9edd9b054e6396e8544640566ff7f3174d4058127d83R377

[makeavish]

Since we are removing /api/v2/metrics/query_range altogether rather than adding /api/v3/query_range, we would be losing analytics for those.

No we are not using /api/v2/metrics/query_range in SigNoz at all so we won't be losing any analytics.

[ankitnayan]

This causes metrics datasource to change to active. You should check for empty filters in the payload?
#3753

[ankitnayan]

trying to create an empty panel makes it active metrics which is incorrect. You should check if metric_name is present or not for it to be marked as active in metrics

[makeavish]

trying to create an empty panel makes it active metrics which is incorrect. You should check if metric_name is present or not for it to be marked as active in metrics

Updated.