On Fri, 2011-05-13 at 21:37 +1000, Nathan Scott wrote:
> Hi guys,
> Following up from some IRC discussion in the last couple of days,
> we're not too far off a pcp-3.5.1 release ... early next week I'm
> expecting we'll have something releasable.
> Ken, Max, & Mark I believe all your recent changes are merged.
There is one more of mine that I don't think is merged yet, ...
90f0e1e1c47a0d6fc54afda813d8c6bc36ef4345 rc scripts and pmie_check - Mac
OS X porting
otherwise, I'm done.
> So, what I'm planning is:
> - make logger.perfile.xxx.records "off" by default, and require a
> pmstore to enable them. This means only those (hosts) with metric
> store capability can enable and "see" these values. We could then
> have a "localhost"-only pmstore policy in our prod environment,
> which would give us an appropriate level of control in our (web
> application logs) setting.
> - extend pmevent with an option to be able to store a "1" to any
> event type metric before attempting to read records ... to enable
> the usual mode of operation.
> - all of the other metrics, in particular the throughput metrics I
> added recently (which count the amount of log traffic), would be
> enabled & visible remotely by default, as normal.
With Frank's suggestion of a per-file config option to the logger PMDA
to enable/disable this behaviour, and assuming the pmStore is benign if
the metric does not have sensitive mode enabled, then this seems like an
acceptable short-term fix.
Longer-term we probably need to grasp the nettle of authentication and
capabilities to control access to parts of the PCP exported info, but no
one seems to be volunteering to take ownership of this (even though it
is on the PCP 4.0 wish list).