SigNoz Deployment and Collector Concerns in Multi-Cluster Application
TLDR Romil asks about deploying k8s-infra chart and collector roles in a multi-cluster setup. Ankit recommends deploying k8s-infra chart for each cluster, and mentions the importance of using SigNoz's otel-collector for their data schema.
Ankit
Fri, 17 Mar 2023 03:27:50 UTCideally, k8s-infra chart should be deployed on each of these clusters to collect and forward data to SigNoz from individual clusters
Ankit
Fri, 17 Mar 2023 03:28:44 UTCsignoz's otel-collector prepares data according to schema we support. It cannot be done using non signoz's component
SigNoz Community
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in AppSimilar Threads
Error Installing K8s-Infra Chart for SigNoz on EKS Cluster
Issues with SigNoz Setup and Data Persistence in AKS
Deploying otel+signoz on EC2: Recommended Architecture Pattern
SigNoz Deployment Issue with External ClickHouse and PVC
Deploying SigNoz in AKS Production Cluster with Sample Application
Romil
Thu, 16 Mar 2023 19:20:20 UTCi'm testing an application where i have 20 clusters around the world, feeding them through a single signoz collector then to clickhouse is a huge bottleneck. if i can deploy the k8s-infra chart into each cluster which directly writes to clickhouse then i just need 1 deployment of signoz in the data cluster to visualize. is this going to cause an issue? does the signoz collector have anything special?