ceph-exporter scrapes failing on multi-homed server
ceph-exporter only binds to a specific interface. All other monitoring related daemons bind to all (grafana, prometheus, alertmanager and node-exporter)
In my test environment with a multi-homed server, the exporter bound to one address but the prometheus scrape target (defined within cephadm) was set to a different address on the same machine. As a result all scrapes fail.
If ceph-exporter adopts the --addrs 0.0.0.0 parameter, this issue can be avoided and it aligns to the same principles as the other monitoring daemons.