Incorrect IP registered in Consul for Prometheus Output about gnmic HOT 5 CLOSED

This works perfectly. Thanks for the quick turnaround @karimra

from gnmic.

The Prometheus output uses the address part of the listen field to register as a service address in Consul.
If that field is empty, Consul defaults to its own address as a service address.

If you want to register 10.249.1.215 as a service address for the prometheus output you should set listen to listen: 10.249.1.215:9804.
The caveat here is that your prometheus output listens only to that address, not to any address in the system.

from gnmic.

The Prometheus output uses the address part of the listen field to register as a service address in Consul. If that field is empty, Consul defaults to its own address as a service address.

If you want to register 10.249.1.215 as a service address for the prometheus output you should set listen to listen: 10.249.1.215:9804. The caveat here is that your prometheus output listens only to that address, not to any address in the system.

The issue is have is that i'm running gnmic in a docker container via docker-compose with the prometheus endpoint port exposed, so it can't bind to 10.249.1.215:9804

I believe another possible solution to this would be to support the service-address configuration option in the service-registration section of the output in the same fashion that it can be configured in the clustering configuration.

from gnmic.

I see, let me look into it

from gnmic.

@jasonyates-thg can you give v0.30.0 a try?

You can set a service address as below:

outputs:
  prometheus:
    type: prometheus
    listen: :9804 
    path: /metrics 
    event-processors: 
      - interface-descriptions
    service-registration:
      address: 10.249.0.250:8500
      service-address: 10.249.1.215

It will register Address=10.249.1.215 and Port=9804.
You can also set a port with the address service-address: 10.249.1.215:9999 if the external port is different from the internal one.

from gnmic.