[performancecopilot/pcp] filesys metrics are (probably) too selective (#113)

[Zack Cerza <notifications@xxxxxxxxxx>]

I won't claim that I need, or want, pcp to monitor all of these:

$ df -h
Filesystem                                               Size  Used Avail Use% Mounted on
udev                                                      16G     0   16G   0% /dev
tmpfs                                                    3.2G  338M  2.9G  11% /run
/dev/vda2                                                2.9T  133G  2.8T   5% /
tmpfs                                                     16G  6.5M   16G   1% /dev/shm
tmpfs                                                    5.0M     0  5.0M   0% /run/lock
tmpfs                                                     16G     0   16G   0% /sys/fs/cgroup
cgmfs                                                    100K     0  100K   0% /run/cgmanager/fs
172.21.5.114:6789,172.21.4.136:6789,172.21.6.130:6789:/  162T  116T   47T  72% /ceph
tmpfs                                                    3.2G     0  3.2G   0% /run/user/1102
[several more tmpfs entries follow]

But this seems a bit too selective:

$ pminfo -f filesys.mountdir
filesys.mountdir
    inst [0 or "/dev/vda2"] value "/"

It would be really helpful if pcp would at least track the ceph fs. I realize there's a ceph pmda, though I don't know what state it's in, but simple free space numbers could be collected pretty easily, it seems.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.