On Mon, Apr 16, 2018 at 12:51 PM, Wido den Hollander <wido@xxxxxxxx> wrote:
> Hi,
>
> While working on another Mgr Module I was looking for this information:
>
> root@alpha:~# ceph daemon mon.alpha perf dump|jq '.cluster'
> {
> "num_mon": 3,
> "num_mon_quorum": 3,
> "num_osd": 3,
> "num_osd_up": 3,
> "num_osd_in": 3,
> "osd_epoch": 73,
> "osd_bytes": 32199671808,
> "osd_bytes_used": 3390619648,
> "osd_bytes_avail": 28809052160,
> "num_pool": 7,
> "num_pg": 160,
> "num_pg_active_clean": 160,
> "num_pg_active": 160,
> "num_pg_peering": 0,
> "num_object": 209,
> "num_object_degraded": 0,
> "num_object_misplaced": 0,
> "num_object_unfound": 0,
> "num_bytes": 4984,
> "num_mds_up": 1,
> "num_mds_in": 1,
> "num_mds_failed": 0,
> "mds_epoch": 27
> }
> root@alpha:~#
>
> I can easily fetch this information from the Mons using perf dump, but
> is there a easy way to fetch it in a Mgr module?
The monitor has a MgrClient, which should be sending perf counters
over the to the mgr, where they'd be visible via the
MgrModule.get_counter interface. Counters are filtered by priority
before they get sent to the mgr though, and I don't know if I've ever
actually looked at the mon ones, so can't guarantee anything's
actually being sent!
John
> I think I can fetch most information using:
>
> - df
> - health
> - pg_status
> - pg_summary
> - osd_map
>
> The Mgr seems to get this information in src/mon/MgrStatMonitor.cc where
> MgrStatMonitor::update_logger() send these statistics to the Mgr.
>
> What would be the way to fetch this information from the Mgr?
>
> Wido
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
