Description of problem:

The current pcp-zeroconf has proc.psinfo gathered every 10 seconds. This generates 20-30GB per day on a big machine, and the .meta being 7-9GB that is never compressed also not during archiving.

With large cpu systems the proc.psinfo gather includes per CPU ~ 7 kernel threads.
For a 384 cpu servers that means 2688 processes are included.

-----------
proc.nprocs
    value 2761
--------

The PCP has the hotproc feature to limit the information.
---------
cat /var/lib/pcp/pmdas/proc/samplehotproc.conf
#pmdahotproc
Version 1.0

uname != "root" || cpuburn > 0.05

sudo cp /var/lib/pcp/pmdas/proc/samplehotproc.conf /var/lib/pcp/pmdas/proc/hotproc.conf
sudo service pmcd restart
Redirecting to /bin/systemctl restart  pmcd.service
pminfo -f proc.nprocs hotproc.nprocs

proc.nprocs
    value 2762

hotproc.nprocs
    value 16

-----------

Before hotproc with standard pcp-zeroconf using 'proc':
-----------
tail -n5 /var/log/pcp/pmlogger/x/pmlogger.log
        proc.psinfo.pid
} logged every 10 sec: 1553280 bytes or 12798.63 Mbytes/day
-----------

After using enable the sampe hotproc and updating the zeroconf provided atop-proc replacing 'proc.' with 'hotproc.':
-----------
sudo sed 's/^\([[:space:]]\)proc\./\1hotproc./' -i /var/lib/pcp/config/pmlogconf/puppet/atop-proc
sudo service pmlogger restart
Redirecting to /bin/systemctl restart  pmlogger.service
tail -n5 /var/log/pcp/pmlogger/x/pmlogger.log
        hotproc.psinfo.pid
        proc.runq.blocked
        proc.runq.runnable
        proc.nprocs
} logged every 10 sec: 243124 bytes or 2003.28 Mbytes/day
-----------

Is it possible to improve the out-of-the-box Recommended/BestPractice pcp-zeroconf configuration to enable the (sample) hotproc instead and the atop-proc pmlogger configuration to use hotproc.


Version-Release number of selected component (if applicable):
RHEL 7

How reproducible:
Easy, always

Steps to Reproduce:
1.Use the zeroconf that advice proc and not hotproc
2.Use a lot of processes or a big machine
3.Check the size used by the gathered data

Actual results:
12 GB logged every day
All process monitored

Expected results:
By default, zero-conf should be set to hotproc and not proc, unless performance reason
2 GB and only noticeable processes should be monitored 

Additional info: