Open rongfengliang opened 2 years ago
Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.
Thanks @rongfengliang for the issue. Can you share more details on what you mean by large service
? Is it a service which serves lots of traffic? Would be great if you can share more details on your use case
Are you deploying SigNoz in a kubernetes cluster?
@pranay01 Thanks. large service
means we have many applications that need to trace. we can deploy with k8s but the dashboard and alert need a shared database, currently, if we deploy multi-instance some dashboards will be lost. we need one practice for large service deployment
Also believe it would be nice to add some references to scalability best practices for tracing and metrics for multiple applications.
Ideally best practices focusing on fault tolerance and load balancing of incoming data.
We have published a doc regarding the configs/practices for production: https://signoz.io/docs/production-readiness
Is your feature request related to a problem?
can we provide some practice for deployment
signoz
in Production with large serviceDescribe the solution you'd like
with cluster deployment && performance tuning docs