Project

General

Profile

Bug #61669

ceph-exporter scrapes failing on multi-homed server

Added by Paul Cuzner 6 months ago. Updated 4 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
avan thakkar
Category:
prometheus module
Target version:
Ceph - v18.1.0
% Done:

0%

Source:
Tags:
backport_processed
Backport:
reef
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
52084
Crash signature (v1):
Crash signature (v2):

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.

Related issues

Copied to mgr - Backport #62220: reef: ceph-exporter scrapes failing on multi-homed server In Progress

History

#1 Updated by Redouane Kachach Elhichou 5 months ago

  • Pull request ID set to 52084

#2 Updated by Radoslaw Zarzynski 4 months ago

  • Status changed from New to Fix Under Review

#3 Updated by Avan Thakkar 4 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to reef

#4 Updated by Backport Bot 4 months ago

  • Copied to Backport #62220: reef: ceph-exporter scrapes failing on multi-homed server added

#5 Updated by Backport Bot 4 months ago

  • Tags set to backport_processed

Also available in: Atom PDF