https://bugzilla.redhat.com/show_bug.cgi?id=1376856
Bug ID: 1376856
Summary: pmlogger pmcd-restart persistence breaks automatic
pmlogconf
Product: Fedora
Version: rawhide
Component: pcp
Assignee: nathans@xxxxxxxxxx
Reporter: fche@xxxxxxxxxx
QA Contact: extras-qa@xxxxxxxxxxxxxxxxx
CC: brolley@xxxxxxxxxx, fche@xxxxxxxxxx, lberk@xxxxxxxxxx,
mgoodwin@xxxxxxxxxx, nathans@xxxxxxxxxx,
pcp@xxxxxxxxxxx, scox@xxxxxxxxxx
With new pmlogger's persistence when it detects its target pmcd dying and
coming back, it does a "validating metrics" pass and keeps going. This sounds
nice for some purposes.
However, consider the case where the remote pmcd came back because new PMDAs
were installed. But what if we want to log those new PMDAs? Now the pmlogger
manager (whether the cron script or pmmgr) do not know that anything happened,
which means that pmlogconf opportunities are missed. Which means that
auto-logging the new metrics is not done, until the next natural cycle time
(day?).
Please add an option to pmlogger to suppress this auto-reconnection, or reject
it if the pmda suite appears to have changed.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=ibURI7DXnk&a=cc_unsubscribe
|