This message was deleted.

This should be possible with OpenTelemetry Collectors. You can run OpenTelemetry Collectors in each of your k8s clusters, and then send the data collected by each OpenTelemetry Collector to a single SigNoz instance. Regarding navigating between different SigNoz instance s data, that should be possible with environment variables. @Prashant Shahi might be able to shed more light on this.

Hey @Asaf Fadida 👋 We have

k8s-infra

chart just for that. You can have

signoz

chart installed in one K8s cluster, while

k8s-infra

chart in other K8s clusters.

k8s-infra

chart collects metrics and logs in any external cluster and sends to SigNoz.

Thats great, thanks! What if I want to have multiple SigNoz instances? One for every k8s cluster (SigNoz will be installed on the monitored k8s cluster) + additional SigNoz instance that gets all the other k8s clusters data. Is it possible?

It is possible, but that would be independent signoz clusters.

Works for me. The question is if otel-collector can send metrics to multiple targets (one local-Signoz + one remote SigNoz)

yes, it can.

Perfect. Thanks

But would need to make changes in the config manually.

🙏

Asaf, can you elaborate more on your use case? Why do you want to run local SigNoz instances for each cluster?

Our system might be deployed on both airgapped-on-prem & non-airgapped environments. We want to provide a monitoring solution within the product-deployment itself (deploying SigNoz on the monitored cluster), and where we can (non-airgapped), we would like to see the monitoring-related-data on a single place (centralized SigNoz)

Got it. Makes sense, Asaf.