- job_name: "aurora_job" serverset_sd_configs: - servers: {% for host in groups["zookeeper"] %} - "{{ host }}:2181" {% endfor %} paths: - "/aurora/serversets" relabel_configs: - source_labels: [ __meta_serverset_path ] regex: '^/aurora/serversets/[^/]+/[^/]+/([^/]+)/.*' target_label: job replacement: "${1}" - source_labels: [ __address__ ] regex: '(ip-\d+-\d+-\d+-\d+)\..*:(\d+)' target_label: __address__ replacement: "${1}:${2}"
that will come in handy. Thanks for that!
I have thought about using prometheus together with the Mesos and Aurora exporters. Your feature would even allow us to start both exports on Aurora and let Prometheus discover them automatically. However, it might be a bit risky to use Aurora/Mesos to host its own monitoring solution...
How have you organized the deployment of your Prometheus components?
Regards,
Stephan
________________________________________
From: Brian Brazil <brian....@boxever.com>
Sent: Wednesday, July 1, 2015 4:54 PM
To: d...@aurora.apache.org; prometheus-developers
Subject: Using Prometheus with Aurora
Hi Brian,
that will come in handy. Thanks for that!
I have thought about using prometheus together with the Mesos and Aurora exporters. Your feature would even allow us to start both exports on Aurora and let Prometheus discover them automatically. However, it might be a bit risky to use Aurora/Mesos to host its own monitoring solution...
How have you organized the deployment of your Prometheus components?
--
You received this message because you are subscribed to the Google Groups "Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.