Project

General

Profile

Actions

Bug #62558

open

mgr/cephadm is not configuring the prometheus endpoints for ganesha

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

Status:
In Progress
Priority:
High
Assignee:
-
Category:
cephadm/monitoring
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
reef
Regression:
No
Severity:
3 - minor
Reviewed:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

After deploying Ganesha, the Prometheus configuration should be updated to reflect the metrics endpoint exposed on each ganesha node (port 9587)

Actions #1

Updated by Avan Thakkar 9 months ago

Paul Cuzner wrote:

After deploying Ganesha, the Prometheus configuration should be updated to reflect the metrics endpoint exposed on each ganesha node (port 9587)

It seems to enabled monitoring for nfs-ganesha we need to enable the config option `USE_MONITORING` somehow https://github.com/nfs-ganesha/nfs-ganesha/blob/f348f0e45f78fa2d11936569d5d6cbfbd9b06289/src/include/gsh_config.h#L478. Not sure how it can be done

Metrics exposed: https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/monitoring/monitoring.cc#L106-L236

Actions #2

Updated by John Mulligan 9 months ago

@avan thakkar, since that's an ifdef, I suspect that's a compile time option. But I haven't confirmed by looking beyond the code you linked.

@Paul, is it safe to assume that if ganesha is running behind ingress that this Prometheus metrics port also needs to be added to the haproxy/keepalive configurations as needed. IOW, the metrics will also be available over the ingress IPs?

Actions #3

Updated by Avan Thakkar 4 months ago

  • Status changed from New to In Progress
  • Pull request ID set to 55050
Actions

Also available in: Atom PDF