ceph-exporter should get deployed by default with new installations on recent versions, but as a general principle we've avoided adding/removing services from the cluster during an upgrade. There is perhaps a case for this service in particular if the user also has the rest of the monitoring stack deployed, but it would be a behavior change to upgrades I'd be cautious about adding in. On Fri, Aug 2, 2024 at 7:45 AM Frank de Bot (lists) <lists@searchy.net> wrote:

Hi,

When upgrading a cephadm deployed quincy cluster to reef, there will be no ceph-exporter service launched.

Being new in reef (from release notes: ceph-exporter: Now the performance metrics for Ceph daemons are exported by ceph-exporter, which deploys on each daemon rather than using prometheus exporter. This will reduce performance bottlenecks. ), metrics will be missing when the ceph-exporter service is not applied after the upgrade.

Is it intentional it's not added after an upgrade by orchestrator? A ceph orch apply ceph-exporter solves it, but I think it could be included in the upgraded since it may not be clear at first why metrics in grafana are missing.

Regards,

Frank de Bot _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io