This message was deleted.

Do you have already some existing data? Or is this a fresh installation? Can you share exit status code for query service?

@Srikanth Chekuri I can not get the exit code, is it exposed by signoz ? I get an empty response:

kubectl get pod signoz-query-service-0 -n platform -o jsonpath='{.status.containerStatuses[?(@.name=="signoz-query-service")].state.terminated.exitCode}'

shouldn’t it be

lastState.terminated.exitCode

? The most common and known one is OOM with 137 when the query service doesn’t have enough memory. What are the resource limits for this?

Yes, it was 137. The resouces are:

resources:
            limits:
              memory: 2000Mi
            requests:
              cpu: 500m
              memory: 2000Mi

What’s the amount of data you are ingesting? Can you share the number of time series you have (run

select count() from signoz_metrics.time_series_v2;

from clickhouse client)? Right now the query service needs resources adjusted for the volume of time series. So if you can share the what’s the avg number of time series you expect in total a resource limit can be suggested.

@Srikanth Chekuri ok, make sense. The query result is 464302

Can you upgrade tot

0.11.1

? We did some improvement and it should run fine for the above number.

yes, looks it works

You can make rough estimation of 1M series ~ 1-1.5GB or RAM

That amount of timse series is based by time ? for example each 5 min, or something like that ?

No, it’s based on the data being ingested. For instance number of status codes, method types etc.. Say you have http requests with 4 status codes and 5 methods then you have 20 time series.

@Srikanth Chekuri thanks you! you save my day! 🙂

I haven’t followed the recent developments there but I believe it was changed to daemonset for some reason. @Prashant Shahi can give you more details on it.

I think actually is running as daemonset because it needs to grab Logs, but would be nice if Logs is not required take an option to disable Logs and deploy as deployment, probably it required some chart modification.

@Alejandro Decchi we have moved back to Deployment. There is a release PR pending. It will be merged after review from @Ankit Nayan. You can track it here: https://github.com/SigNoz/charts/pull/82

@Prashant Shahi excellent news, Chart version 0.4.0 is that correct ?