Bug 1994254

Description of problem:
In pcp-5.2.5 we have seen the introduction of zeroconf metrics in the base package, which has resulted in a substantial increase in pmlogger log file size. For example:

# grep logged pmlogger.log
} logged once: 4752 bytes
} logged every 60 sec: 51768 bytes or 71.09 Mbytes/day
} logged every 300 sec: 7032 bytes or 1.93 Mbytes/day
} logged every 30 sec: 168956 bytes or 464.05 Mbytes/day
} logged every 600 sec: 1924 bytes or 0.26 Mbytes/day

The 'logged every 30 sec' output is the result of the zeroconf metrics.

Version-Release number of selected component (if applicable):
pcp-5.2.5-4.el8.x86_64

How reproducible:
Always


Steps to Reproduce:
1. Install pcp: dnf install -y pcp-5.2.5-4.el8.x86_64
2. Start the pmlogger service: systemctl start pmlogger
3. Check pmlogger estimated output: grep logged /var/log/pcp/pmlogger/$(hostname)/pmlogger.log
4. Remove zeroconf metrics: rm -rf /var/lib/pcp/config/pmlogconf/zeroconf/
5. Restart pmlogger service: systemctl restart pmlogger
6. Check pmlogger estimated output (should now be much less): grep logged /var/log/pcp/pmlogger/$(hostname)/pmlogger.log

Actual results:
With the zeroconf metrics included in the base pcp package the pmlogger output size is substantially bigger.

Expected results:
The zeroconf metrics should not be included in the base pcp package.

Additional info: