Description of problem: [root@localhost ~]# ip l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:0a:6b:42 brd ff:ff:ff:ff:ff:ff 3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:22:c7:44 brd ff:ff:ff:ff:ff:ff [root@localhost ~]# pminfo -f network.interface.speed network.interface.speed inst [2 or "virbr0-nic"] value 78126.195 [root@localhost ~]# pminfo -F network.interface.speed network.interface.speed inst [2 or "virbr0-nic"] value 78126.195 [root@localhost ~]# pmval -s 1 network.interface.speed metric: network.interface.speed host: localhost.localdomain semantics: discrete instantaneous value units: Mbyte / sec samples: 1 lo virbr0 virbr0-nic ens3 ? ? 7.813E+04 ? [root@localhost ~]# getenforce Permissive [root@localhost ~]# rpm -q pcp pcp-3.11.2-2.fc24.x86_64 [root@localhost ~]# Since pminfo(1) states -f Fetch and print values for all instances. it would seem the above is a bug not a feature.
I suspect this is because the device drivers for those interfaces don't provide any value for that metric - IOW, the interface exists, is up, but no value is available. The pminfo response looks correct, assuming that's the case?
(In reply to Nathan Scott from comment #1) > I suspect this is because the device drivers for those interfaces don't > provide any value for that metric - IOW, the interface exists, is up, but no > value is available. > > The pminfo response looks correct, assuming that's the case? Sorry for being a bit vague here - based on the man page I would expect pminfo to report all instances with -f regardless of their values (IOW, whether available or not). Thanks.
When I say "no value is available" I mean, the kernel does not provide this information for those interfaces (iow, some device drivers do not support it). I think the PCP code is handling this as best it possibly can, under those circumstances.