On Wed, 2007-10-24 at 11:18 +1000, Mark Goodwin wrote:
> Hi Nathan,
>
> poking around in the CHANGELOG, most recent changes are:
>
> pcp-2.7.4 (7 Sep 2007)
> - MaxOSX and Debian/Ubuntu build/package fixes
> - Add sqlserver active_transactions metrics to the Windows PMDA.
> - Fix a pmie_check typo causing mis-identification of pmie
> processes.
> - Allow pmie and/or operators to function with some data missing.
> - Resolve path naming issues with more recent versions of
> autoconf.
> - pmlogsummary report sum option
> - pmval kmtime support
> - Additional Linux SNMP metrics
> - Fix Linux vmstat nr_slab metrics
> - Make pcp status command report build version
> - Windows split_io metrics
> - Fix pmdapmcd empty pmie instance
> - pmdamailq filename regex
> - Windows TCP metrics
> - pmie log file rotation
> - Changed the default compression program to be bzip2(1)
>
>
> How much of your git commit (below) is not documented in the
> CHANGELOG, e.g. what are the libpcp changes (and libpcp_pmc?).
Much of that particular git commit is SGI code (merged into my git
tree).
Not sure which libpcp_pmc/libpcp changes you mean there, I haven't
changed anything in either of those for ages. Theres odds and ends
going into the pcp git tree from time to time, but Michael works
through those and merges them back into your internal trees as time
permits.
> Michael, what's the plan for reconciling this into the master
> internal dev tree? A fair bit of review work will be needed,
> followed by another round of qa and push to oss.
That is the plan (I'd imagine). Then rinse, repeat, rinse, repeat -
as new stuff is incoming all the time.
BTW, at some point it'd be good to discuss the libpcp changes for
different contexts with different proxy hosts (and the associated
pmMetricSpec changes you mentioned the other day Mark) - is this
something you guys might look at developing? Its not going to see
light of day from me for a long time (kmchart eating lots of time),
but the user interface support for that in kmchart is mostly there
and it'd be a _really_ useful feature...
Maybe you guys could write it up (if you have cycles to implement
it), and post a plan/detailed design? Theres some notes at the end of
the kmchart/README file about this, but doesn't go into enough detail.
And its a core PCP change, with API extensions, so I'd really prefer it
if you guys could take it on (I'll happily sign up for implementing the
kmchart side of things if you implement the libpcp support).
cheers.
--
Nathan
|