@Ben: Thanks for the suggestion! I heard that remote-write consumes more system resources like CPU utilization when compared to the federation. I can test and cross-check it myself but I would like to hear feedback from the Prometheus experts. @Stuart: Ideally, it is possible to manage the complete stack with instance-1 but the current case is about deploying and monitoring multiple workloads/software owned by different vendors.
/Teja On Monday, July 18, 2022 at 8:52:59 PM UTC+2 Stuart Clark wrote: > On 18/07/2022 18:00, tejaswini vadlamudi wrote: > > Hello Stuart, > > I have the 4 Prometheus instances in the same cluster. > > - Instance-1, monitoring k8s & cadvisor > - Instance-2, monitoring workload-1 in namespace-1 > - Instance-3, monitoring workload-2 in namespace-2 > - Instance-4 is the central one collecting metrics from all 3 > instances (for global querying and alerting). not sure if the federation > is > a good fit for this sort of deployment pattern. > > What's the reason for having all the different instances? Are these all > full instances of Prometheus (with local storage) or using agent mode? > > If you are just going to copy everything to the "central" instance on the > same cluster, why not just do without the extra three clusters and have > just the one instance that monitors everything? > > -- > Stuart Clark > > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/cd955a3f-fb4c-43f8-87e2-4eb006bc7df8n%40googlegroups.com.
