Srikanth Chekuri

> The third reason is postProcess functions need to align timeshift A query result https://github.com/SigNoz/signoz/blob/204728ff60346c906dbf13b7a53d99bf585a2be4/pkg/query-service/app/queryBuilder/functions.go#L312 https://github.com/SigNoz/signoz/blob/204728ff60346c906dbf13b7a53d99bf585a2be4/pkg/query-service/postprocess/process.go#L36

> But the alert with timeshift functions is still not good, because the timeshift is not calculated correctly when evaluating alert rule in backend What do you mean by this?...

You are correct. We will fix that bug as well.

@amlannandy I was going through it, why is it 25000 {count}/s instead of 25k c/s? If it were 1.5 million in number, would it be shown as 1,500,000 {count}/s?

This will require backend changes as well @amlannandy, specifically at https://github.com/SigNoz/signoz/tree/0acbcf8322fa211d093292a9dcb865e25b365d65/pkg/query-service/formatter and https://github.com/SigNoz/signoz/tree/0acbcf8322fa211d093292a9dcb865e25b365d65/pkg/query-service/converter

@amlannandy, thanks for the change. Please add tests for the converter and formatter with the additional units. Since these are used in alerting, we should add some tests there as...

@amlannandy it's not clear to me how the units of the form {...} we receive from OpenTelemetry are handled in the code. For example, take the `k8s.replicaset.available` or `system.network.packets` or...

Superseded by https://github.com/SigNoz/signoz/pull/8909

It is already a POST request https://github.com/SigNoz/alertmanager/blob/459221155d33fd43963c3095fe928c587ea7e1b9/notify/webhook/webhook.go#L103

- Users can use start_time and end_time in queries https://github.com/SigNoz/signoz/pull/5714 - We will cap the number of values in dropdown https://github.com/SigNoz/signoz/issues/5761