One of my servers has an internal and an external ip address. The
hostname belongs to the external address, while the prometheus server
should connect to the internal address.
-> 10.0.0.1 external example
myserver.domain -> 192.168.0.1 internal example
Hostname defined in Uyuni = myserver.domain.com
IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT)
and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the
prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100:
connect: connection refused
What can I do to change the connection string to:
that is accessible from the prometheus server?
I tried to change the prometheus_exporter Address: field from :9100 to
myserver.domain:9100 and the Argument field from
--web.listen-address="myserver.domain:9100", but that changes nothing.
The prometheus server catches the mgr-clients from the uyuni server:
# Auto discover clients of uyuni
- job_name: 'mgr-clients'
- host: https://uyuni.domain
Same problem with the apache Exporter :)