Hi Mark,
----- Original Message -----
> RFC - ship a global derived metrics config directory in the pcp package.
> $PCP_VAR_DIR/config/derived along with a config for IOSTAT metrics. Other
> configs can be added.
My initial concern is: this is putting server-platform-specific stuff on
a client-side install - which is kinda going back to the bad old days of
agent Installs on client machines. IOW, your example there (the iostat
metrics) is very Linux-specific.
But, I don't really see any sensible way around it - we need 'em for the
archive case, and there's no server-side derived metric concept either,
by design IIRC (too complex to do in pmcd I'm sure).
> If this is deemed reasonable, then my next commit
> makes pmchart load all configs in this directory by default (and other
> generic monitoring tools such as pmrep, pmval, pmdumptext etc could do
> the same).
Sounds like a libpcp API will be needed here? Oh, or maybe not - we could
do this in the pmGetOptions code (maybe __pmEndOptions) and that will be
visible in all tools without changes then.
> TODO: deb packaging. By default this ships in the 'pcp' package for RPM
> based distros.
Hmm, I wonder if thats the best place or should it be the pcp-conf package?
(for a pcp-libs -only install, which someone might do to support just their
own PMAPI utility)
cheers.
--
Nathan
|