Prometheus: scrape RabbitMQ Cluster (#1218)

Extra: remove master_rabbit from simcore targets as we don't run simcore
rabbit on master deployments anymore (either AWS Rabbit or Cluster
Rabbit)

Related issue/s
* #1176

Author: YuryHrytsuk

services/monitoring/prometheus/prometheus-simcore.yml

@@ -92,7 +92,6 @@ scrape_configs:
       - names:
           - "tasks.production_rabbit"
           - "tasks.staging_rabbit"
-          - "tasks.master_rabbit"
         type: "A"
         port: 15692
       - names:

services/rabbit/docker-compose.node0x.yml.j2

@@ -18,6 +18,9 @@ services:
           memory: "1G"
       update_config:
         order: "stop-first"
+      labels:
+        - prometheus-job=rabbit
+        - prometheus-port=15692
     environment:
       # https://www.rabbitmq.com/docs/configure#supported-environment-variables
       RABBITMQ_DEFAULT_USER: ${RABBIT_USER}
@@ -44,6 +47,7 @@ services:
       - rabbit0{{ NODE_INDEX }}_data:/var/lib/rabbitmq
     networks:
       - rabbit
+      - monitored
     healthcheck:
       # see https://hub.docker.com/_/rabbitmq#healthlivenessreadiness-checking
       # https://www.rabbitmq.com/docs/clustering#restarting-readiness-probes
@@ -65,6 +69,9 @@ networks:
   rabbit:
     name: ${RABBIT_NETWORK}
     external: true
+  monitored:
+    name: ${MONITORED_NETWORK}
+    external: true
 
 configs:
   rabbitmq.conf:

services/rabbit/template.env

@@ -12,4 +12,5 @@ RABBIT_LB_REPLICAS=${RABBIT_LB_REPLICAS}
 RABBIT_NETWORK=${RABBIT_NETWORK}
 
 PUBLIC_NETWORK=${PUBLIC_NETWORK}
+MONITORED_NETWORK=${MONITORED_NETWORK}
 MONITORING_DOMAIN=${MONITORING_DOMAIN}