com.df.metricsPath does not work

[remy-tiitre]

I added - com.df.metricsPath=/actuator/prometheus to my service labels but its still shows up as metrics_path: /metrics in Prometheus config.

[anomaly256]

I've noticed this too - oddly though, it did work initially. After restarting some things it seems to have changed from the /api/metrics specified in the service label back to /metrics causing it to no longer scrape my rabbitmq nodes

[anomaly256]

side note: forcing a restart of swarm listener has brought it back, maybe the root of the issue is there and not with docker-flow-monitor.

When I have some time I'll dig deeper and see if I can find the root cause to report on this bug

[raiderx]

I faced with the same issue: after restarting DFM ignores metricsPath from DFSL

$ ARG_CONFIG_FILE=/home/prometheus.yml docker-flow-monitor && cat /home/prometheus.yml
2019/02/09 20:16:21 Requesting services from Docker Flow Swarm Listener
2019/02/09 20:16:21 Processing: [{"distribute":"true","port":"3000","replicas":"1","reqPathSearch":"/grafana","serviceName":"monitor_grafana","servicePath":"/grafana/,/grafana/public,/grafana/api"},{"distribute":"true","port":"9090","replicas":"1","serviceDomain":"192.168.12.130","serviceName":"monitor_monitor","servicePath":"/monitor"},{"appName":"external-service","distribute":"true","metricsPath":"/external-service/metrics","replicas":"1","scrapePort":"8080","serviceName":"external-service-green"}]
2019/02/09 20:16:21 Writing to prometheus.yml
2019/02/09 20:16:21 Starting Docker Flow Monitor
2019/02/09 20:16:21 listen tcp 0.0.0.0:8080: bind: address already in use
global:
  scrape_interval: 10s
scrape_configs:
- job_name: external-service-green
  metrics_path: /metrics
  dns_sd_configs:
  - names:
    - tasks.external-service-green
    type: A
    port: 8080

I think function getScrapeFromMap at server/server.go (line 292) does not read value from json element "metricsPath".