+++ This bug was initially created as a clone of Bug #1456262 +++

As of pcp-3.11.10 in Fedora, the  /var/lib/pcp/config/pmlogconf/zeroconf/* files are included in the base pcp package.  These files cause frequent logging of high-churn proc.* metrics if one runs pmlogconf, even if one did not opt into the "pcp-zeroconf" subpackage.  This could mean a large unintended & undocumented increase to the default amount of data being logged ... except that normal pmloggers run under uid pcp, thus can't fetch most of those proc metrics unless running with "pmdaproc -A"!

Please consider moving these pmlogconf/zeroconf/* files out of the pcp base package, and check their functionality vs. pmdaproc non-A.

--- Additional comment from Nathan Scott on 2017-05-28 18:01:57 EDT ---

Must be something specific to fedora.spec I guess, the ./Makepkgs build don't exhibit this problem - could you take a peek please Lukas?

Thanks.

--- Additional comment from Mark Goodwin on 2017-05-28 20:39 EDT ---

Attached patch (untested) should fix it by filtering all zeroconf files out of base.list. This would of course have to be pushed to fedora separately as a spec update.

--- Additional comment from Frank Ch. Eigler on 2017-05-29 10:45:39 EDT ---

Since these proc.* metrics are only available to -h local:  type connections, not remote ones (in default pmdaproc configs), perhaps they should be somehow identified specially.  That way, only a 'primary' pmlogger would see them, not remote-pmcd ones.  Reminds me of the customized configuration of the 'primary' pmie.