--
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 prometheus-users+unsubscribe@googlegroups.com.
To post to this group, send email to prometheus-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/e5286c96-917f-4e7e-a47e-1dc47c962cdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Not a Prometheus operator expert here, but I found this, which might be helpful: https://github.com/coreos/prometheus-operator/pull/1100
On Sun, May 6, 2018 at 2:54 PM, Maciek Strzelecki <strzelec...@gmail.com> wrote:
Hi, i have several k8s clusters, each one has a prometheus operator and kube-prometheus installed via helm.
One k8s cluster is the main one. One where id like to set up central prometheus instance with persistance and much more resources assigned, as well as all the grafana dashboards.
My plan is to (inside every k8s cluster) apply my own service exposing each prometheus 9090 and then "somehow" use these endpoints to create a federate config snippet.
The real question here is - how do i nicely make the prometheus-operator aware that apart from the (awesome) servicemonitor based config build i need that custom snippet federate-job appended.
Or maybe thats a job for servicemonitor crd with some special annotations/config?
Thanks!
--
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 prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.