On 05 Aug 05:24, Tom Kun wrote: > Hi folks, > > I'm trying to retrieve metrics from different Swarm clusters into a > Prometheus container which is deployed in an other Swarm cluster dedicated > to the monitoring part of the entire infrastructure. > > I have actually setup the http through the Docker Swarm manager daemon and > I could retrieve from the docker-daemon quite easily. > But I cannot understand what I am missing to retrieve tasks informations > from the other Docker Swarm manager from other Swarm cluster because I > cannot see any node_meta in the Prometheus Web UI.
It seems like a network issue. Your prometheus server can not join the targets. > > - All Docker Swarm Manager nodes have the Docker daemon using HTTPS. > - This is an example of the configuration of the prometheus.yml file using > dockerswarm_sd_configs > using "tasks" role: > The following example is not working in Prometheus > - job_name: "runner-docker-swarm" > dockerswarm_sd_configs: > - host: tcp://10.XXX.XXX.XXX:2376 > role: tasks > relabel_configs: > - source_labels: [__meta_dockerswarm_task_desired_state] > regex: running > action: keep > - source_labels: [__meta_dockerswarm_node_hostname] > target_label: node_name > - source_labels: [__meta_dockerswarm_node_id] > target_label: node_id > > For infrastructure, the dockerswarm_sd_configs is pretty much the same: > - job_name: "infra-docker-swarm" > dockerswarm_sd_configs: > - host: unix:///var/run/docker.sock > role: tasks > relabel_configs: > - source_labels: [__meta_dockerswarm_task_desired_state] > regex: running > action: keep > - source_labels: [__meta_dockerswarm_service_label_prometheus_job] > target_label: job You should add regex: (.+) here so that you do not remove the default prometheus job if the label is not set on the service. > - source_labels: [__meta_dockerswarm_node_hostname] > target_label: node_name > - source_labels: [__meta_dockerswarm_node_id] > target_label: node_id > > Here is a screenshot of the Prometheus node_meta > > > > Targets for the Docker Swarm cluster which embbed Prometheus > > > > Targets for the oher Docker Swarm Cluster to monitor which cannot be > contacted by the Prometheus. > > > > Which configuration I miss on my Swarm clusters or my Swarm Manager nodes? > > Thank in advance for your help. > > Thomas > > -- > 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/3c6c77d9-4ce7-403d-8c81-308012abdc8ao%40googlegroups.com. -- Julien Pivotto @roidelapluie -- 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/20200805122910.GA416888%40oxygen.
