https://signoz.io logo
#support
Title
# support
a

Alexei Zenin

07/28/2022, 6:54 PM
In terms of deploying the SigNoz containers which ones can not be scaled? I assume the frontend and query-service can be scaled to N replicas while the alertmanager can only have 1 instance?
is it recommended to run more than 1 query service or any other of the above containers in PROD?
p

Prashant Shahi

07/28/2022, 8:57 PM
@Alexei Zenin currently, Frontend and OtelCollector can be scaled. It does not make sense to horizontally scale OtelCollector Metrics, as it is used for obtaining metrics via pull based mechanism. Scaling ClickHouse is done using
layouts
(Experimental): https://github.com/SigNoz/charts/blob/main/charts/clickhouse/values.yaml#L174-L180
a

Alexei Zenin

07/28/2022, 8:58 PM
I see thanks, so alert manager and query service cannot
Is there something stateful in the query-service?
p

Prashant Shahi

07/28/2022, 9:08 PM
Alertmanager could be possible, but unsure since we haven't tested it from our end. @Amol Umbark would be the right person to answer that.
For query-service, @Ankit Nayan would be the best person to answer that.
a

Ankit Nayan

07/29/2022, 4:46 AM
nothing specific in query-service except that we use a sqlite db for storing users and dashboards. When we add postgres, it will become horizontally scalable
but usually querying is not heavily used unless we have too many alerts running at fixed interval. Hence we separated ingestion and querying to handle both the loads separately
a

Alexei Zenin

07/29/2022, 2:23 PM
Yeah thats what I was thinking, the file DB would only allow 1 instance of query service. Thanks for the clarifications!
MySQL would be better :)
p

Prashant Shahi

07/29/2022, 2:28 PM
@Alexei Zenin we had been evaluating PostgreSQL as a replacement for SQLite.. But due to lack of bandwidth, it is not on top of our roadmap.
2 Views