Actions
Bug #61669
closedceph-exporter scrapes failing on multi-homed server
% Done:
0%
Source:
Tags:
backport_processed
Backport:
reef
Regression:
No
Severity:
2 - major
Reviewed:
Description
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.
Updated by Radoslaw Zarzynski 10 months ago
- Status changed from New to Fix Under Review
Updated by Avan Thakkar 10 months ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to reef
Updated by Backport Bot 10 months ago
- Copied to Backport #62220: reef: ceph-exporter scrapes failing on multi-homed server added
Updated by Ilya Dryomov 5 months ago
- Status changed from Pending Backport to Resolved
- Target version deleted (
v18.1.0)
Actions