Bug 1376575 - omnibus pcp pmda RFEs regarding automation & documentation
omnibus pcp pmda RFEs regarding automation & documentation
Status: NEW
Product: Fedora
Classification: Fedora
Component: pcp (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: pcp-maint
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-09-15 15:00 EDT by Frank Ch. Eigler
Modified: 2017-08-23 11:02 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Frank Ch. Eigler 2016-09-15 15:00:43 EDT
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.
Comment 1 Frank Ch. Eigler 2016-09-16 11:12:36 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.