On Tue, 2010-06-15 at 12:02 +1000, nathans@xxxxxxxxxx wrote:
> ----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote:
>
> > I am proposing changing pmlogconf in the following ways:
> >
> >
> >
> > 1. The pmlogconf version will go from 1.0 to 2.0
> > 2. Replace in-line groups (currently defined in the pmlogconf
> > script) by external files, one group of metrics per file. The files
> > will live in an arbitrary tree structure below the (new) config
> > directory $PCP_VAR_DIR/config/pmlogconf. With the exception of the
> > v1.0 directory (see below), when pmlogconf is run to create a new
> > configuration file, all the group files below
> > $PCP_VAR_DIR/config/pmlogconf will be processed. So add-ons, private
> > PMDAs, local admins etc can add new group files as desired either in
> > an existing subirectory (not recommended) or by adding their own
> > subdirectory.
> > 3. Group files will have the following format:
> >
> > 4. one or more lines starting with the keyword "ident"
> > 5. either a "probe" or a "force" control line (see below)
> > 6. lines beginning with white space are metrics to be logged, one
> > per line
> > 7. lines beginning with # are comments
> > 8. blank lines are ignored
>
> What about a default logging interval? hinv metrics and the like might
> be "log once" ... filesys.used might be logged relatively infrequently,
> compared to critical application/utilisation metrics, etc.
As I started to do this, I added a "delta" control line to those above
for just this purpose ... in the absence of a delta control line the
default is "default".
> I wouldn't put too much effort in catering for existing files, as noone
> will be using current version in oss land (its so IRIX specific), and no
> one in IRIX land will be using oss PCP (maybe thats a brave assumption).
> Just a "fail" approach with 1.0 files will likely be enough, rather than
> trying to migrate ... unless its trivial.
Migration is not really hard ... and I'm almost done.
|