Hi Team,

We have configured few node and url, but the metrics are not getting 
scraped. 

There is a minion between the customer server and the node exporter server.

Below is the configuration done.

On Prometheus server for Apigee(customer) url

- job_name: 'apigeeurl'
    metrics_path: /probe
    scheme: http
    params:
        module: [http_2xx]
    file_sd_configs:
        - files:
              - /etc/prometheus/targets.yml
    relabel_configs:
        - source_labels: [__address__]
          target_label: instance
        - source_labels: [__address__]
          target_label: __metrics_path__
        - target_label: __address__
          replacement: 10.1.3.17:8080

For APigee node

- job_name: 'apigeenode'
    static_configs:
      - targets:
        - 10.2.0.85
        - 10.2.0.86
        - 10.2.0.87
        - 10.2.0.101
        - 10.2.0.102
        - 10.2.0.103
        - 10.2.0.117
        - 10.2.0.118
        - 10.2.0.119
        - 10.2.16.85
        - 10.2.16.86
        - 10.2.16.87
        - 10.2.16.101
        - 10.2.16.102
        - 10.2.16.103
        - 10.2.16.117
        - 10.2.16.118
        - 10.2.16.119

    relabel_configs:
      - source_labels: [__address__]
        target_label: instance
      - source_labels: [__address__]
        target_label: __metrics_path__
      - target_label: __address__
        replacement: 10.1.3.17:8080


On prometheus exporter server :-

root@prodexporter01:/opt/promitor_azure_exporter/prodmon# docker ps -a
CONTAINER ID        IMAGE                                      COMMAND      
            CREATED             STATUS              PORTS  
                                                                            
                           NAMES
18a29bfa41b1        pambrose/prometheus-proxy:1.6.4            "java 
-server -XX:+U…"   14 hours ago        Up 14 hours         0.0.0.0
:8080->8080/tcp, 0.0.0.0:8082->8082/tcp, 0.0.0.0:8092->8092/tcp, 
0.0.0.0:50051->50051/tcp, 50440/tcp   prometheus-proxy


Logs for prometheus proxy 

12:28:26.433 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.16.119 [DefaultDispatcher-worker-6]
12:28:26.470 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.0.119ps9 [DefaultDispatcher-worker-4]
12:28:27.719 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.0.102 [DefaultDispatcher-worker-6]
12:28:28.496 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.0.117 [DefaultDispatcher-worker-4]
12:28:28.639 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.16.103qs6 [DefaultDispatcher-worker-5]
12:28:28.792 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.16.87 [DefaultDispatcher-worker-4]
12:28:29.914 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.0.86rtr2 [DefaultDispatcher-worker-5]
12:28:30.034 INFO  [ProxyHttpConfig.kt:116] - Invalid path request 
/10.2.0.85ms1 [DefaultDispatcher-worker-4]

-- 
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/061c8284-ec8c-4d9f-a8ab-8cd71c2750f8o%40googlegroups.com.

Reply via email to