What were you trying to do that didn't work?

Generating sos reports with pcp installed, gathers all historical PCP archives

What is the impact of this issue to you?

The sos reports are ending up very large, customers are finding it difficult and annoying to upload files of this size. However, the PCP logs do contain performance data that can be really helpful for support cases, so it's important we still capture the relevant parts.

Please provide the package NVR for which the bug is seen:

sos-4.10.0-4.el9_7.noarch

How reproducible is this bug?:

All the time

Steps to reproduce

TAM followed these steps:
1 dnf -y install sos
5 dnf -y install pcp-zeroconf
6 sosreport
10 dd if=/dev/urandom of=/var/log/pcp/pmlogger/amd96.local/file bs=1M count=128
12 sosreport
14 dd if=/dev/urandom of=/var/log/pcp/pmlogger/amd96.local/file2 bs=1M count=256
15 sosreport
17 dd if=/dev/urandom of=/var/log/pcp/pmlogger/amd96.local/file3 bs=1M count=512
18 sosreport

[root@amd96 ~]# ll /var/tmp/
total 1494064
rw------. 1 root root 10681388 Dec 18 06:28 sosreport-amd96-2025-12-18-etydbju.tar.xz
rw-rr-. 1 root root 65 Dec 18 06:28 sosreport-amd96-2025-12-18-etydbju.tar.xz.sha256
rw------. 1 root root 144961952 Dec 18 06:30 sosreport-amd96-2025-12-18-kwhwftm.tar.xz
rw-rr-. 1 root root 65 Dec 18 06:30 sosreport-amd96-2025-12-18-kwhwftm.tar.xz.sha256
rw------. 1 root root 950432136 Dec 18 06:50 sosreport-amd96-2025-12-18-lbkoadp.tar.xz
rw-rr-. 1 root root 65 Dec 18 06:50 sosreport-amd96-2025-12-18-lbkoadp.tar.xz.sha256
rw------. 1 root root 10350908 Dec 18 06:22 sosreport-amd96-2025-12-18-mukyrus.tar.xz
rw-rr-. 1 root root 65 Dec 18 06:22 sosreport-amd96-2025-12-18-mukyrus.tar.xz.sha256
rw------. 1 root root 413432376 Dec 18 06:35 sosreport-amd96-2025-12-18-swpjeov.tar.xz

Expected results

It would be ideal if the sos report only gathered the latest logs by default. Alternatively, perhaps we could look into adding options to limit the collection to specific days?

Actual results

Large sos reports with the pcp plugin is active.