Multiple users complain that:
- Many pmdas are not activated when their subrpms are installed,
even when they don't require configuration and they don't take
up resources when idle. These should be auto-.NeedInstall'd.
- Many pmdas man pages are 95% boilerplate. They should instead
elaborate the kinds of metrics that are available.
- Many pmdas don't come with pmlogconf files at all. The particularly
lightweight ones should not only come with pmlogconf files, but mark
the key metrics "include" (auto-enabled) for logging.
In order to ease centralized logging of remote targets with different pools of pmdas, it would be desirable for the central site to easily get hold of the potential remote pmlogconf files.
Since we don't have a mechanism to upload those from the target pmcd/pmdas to the remote logger, so we need a less automatic facility.
One possibility is to change the pcp packaging system so that the subpackages that contain pmlogconf and/or pmlogger and/or pmmgr to include/require a copy of all the pmlogconf/* fragments from all the pmdas we ship, already installed under $PCP_VAR/.../pmlogconf, as though someone ./Install'd all the pmda's centrally, in "m" monitoring mode only.
There have been many pcp changes since this BZ was opened, and pcp-zeroconf solves many of the issues in a more practical way than described here. The description of pmlogconf files in the BZ is also incorrect - for the most part, these reside in the (central) pcp package already. No further work on this BZ is planned by the pcp team. However, please feel free to work on any ideas in upstream PCP, and have them filter back via the usual Fedora update mechanisms.