Srikanth Chekuri

@luna215 Does it consistently fail?

Technically, it could be disabled (with some config changes), but we recommend not doing that. It scrapes the APM metrics and internal metrics of the main collector(s). If you were...

@luizbafilho, you mentioned, you tried updating. Where did you do that?

We need to add this to `.spec.configuration.settings` to take this effect.

In the first comment description, you mentioned _you tried doing ..._ I was asking how you updated that and where the spec config did you modify?

Here is the detail. In general, the time series data doesn't change often. The same set of labels keeps reporting the data. Example `{serice:frontend, api_name:query_range}` would report data every 30...

It is already part of the codebase https://github.com/SigNoz/signoz/blob/12be6ce02070f8670c8591e5219eb6e9d09ba11e/pkg/query-service/app/metrics/v4/helpers/sub_query.go#L18-L50.

Please try adding the `timeout: 10s` to the clickhousetraces exporter and check if that resolves the issue. override-values.yaml ``` otelCollector: config: exporters: clickhousetraces: timeout: 10s ```

How much resoruces were provisioned and how much data do you ingest?

First I will tell you why it worked in the past but now you see some errors. There was a bug in the exporter code that didn't respect the context...