I've been monitoring my Ceph LAN segment for the last several hours and absolutely no traffic has shown up on any server for port 8765. Furthermore I did a quick review of Prometheus itself and it's only claiming those 9000-series ports I mentioned previously. So I conclude that this isn't literally a Prometheus problem, although it could be something external that's supposed to plug in to Prometheus that isn't part of my standard Ceph setup. Since port 8765 isn't a Well-Known Port, that's about all I can say on that matter. I'd only panic if Prometheus isn't collecting something that's important to me. Tim On Wed, 2024-09-04 at 16:22 +0100, Matthew Vernon wrote:
Hi,
I tracked it down to 2 issues:
* our ipv6-only deployment (a bug fixed in 18.2.4, though that has buggy .debs)
* Discovery service is only run on the active mgr
The latter point is surely a bug? Isn't the point of running a service discovery endpoint that one could point e.g. an external Prometheus scraper at the service discovery endpoint of any mgr and it would then tell Prometheus where to scrape metrics from (i.e. the active mgr)?
Thanks,
Matthew _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io