Specifically - we slowly increase the load of micro-service data - but we are facing challenges - with the query builder and unable to load. - any idea or suggestion - or any pointer talks about the scalability of the system.

If you configured the tiered volume policy for the data clickhouse reads it from s3. How much load/scale are you planning for?

Well, we wanted to scale for 200 micro-service

Did you mean query-service? It loads the time series in memory to support prometheus. What is the volume of data ingested and retention requirements?

@rakesh shah Otel Collector and Frontend can be horizontally scaled as per your need.

OK.

Query-Service is currently not scalable mainly because of dependency to SQLiteDB for storing users, orgs and dashboards data. When we migrate to PostgreSQL, Query-Service should be horizontally scalable.

OK

Yes, the time series is cached for prometheus support. What is the approximate number of time series you generate?

We don't use prometheus - until it is used by Signoz internally

What metric system do you use? Or you are just using signoz just for tracing?

How metric data is displayed by signoz?

You can build dashboards using it. Or you can set alerts using them. https://signoz.io/docs/userguide/alerts-management/ https://signoz.io/docs/userguide/manage-dashboards-and-panels/

OK.

@rakesh shah is signoz working smoothly or you still facing problems in query-builder?

Hi Ankit, We have moved time-being to grafana tempp

ok. no worries. check us out sometime later when you might need some aggregations and custom dashboards on trace data. BTW was the loading issue of query-service primarily the reason?