Project

General

Profile

Actions

Bug #61669

closed

ceph-exporter scrapes failing on multi-homed server

Added by Paul Cuzner 11 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
prometheus module
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
reef
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
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 1 (0 open1 closed)

Copied to mgr - Backport #62220: reef: ceph-exporter scrapes failing on multi-homed serverResolvedAvan ThakkarActions
Actions #1

Updated by Redouane Kachach Elhichou 11 months ago

  • Pull request ID set to 52084
Actions #2

Updated by Radoslaw Zarzynski 10 months ago

  • Status changed from New to Fix Under Review
Actions #3

Updated by Avan Thakkar 10 months ago

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

Updated by Backport Bot 10 months ago

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

Updated by Backport Bot 10 months ago

  • Tags set to backport_processed
Actions #6

Updated by Ilya Dryomov 5 months ago

  • Status changed from Pending Backport to Resolved
  • Target version deleted (v18.1.0)
Actions

Also available in: Atom PDF