pcp
[Top] [All Lists]

Re: Problems with pmlogrewriting

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: Problems with pmlogrewriting
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 07 Aug 2013 10:59:52 +1000
Cc: PCP Development Team <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <644882556.10408085.1375687830312.JavaMail.root@xxxxxxxxxx>
References: <644882556.10408085.1375687830312.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
On 05/08/13 17:30, Nathan Scott wrote:
Hi Ken,

I've been having some problems with pmlogrewrite today,
with an odd corner case (perhaps?) that the pmdalinux/
pmdaxfs split is causing.

The fundamental problem is that the quota.state.* and
filesys.* metrics share an indom.  I've been trying to
come up with a pmlogrewrite ruleset that will preserve
both the old indom (for filesys.*) and add a new indom
(for quota.state.*).

Clunk [sound of requirement falling outside design brief]

I've added a test to git://oss.sgi.com/nathans/pcp.git
which shows the problem (see qa/src/new_xfs.*), qa/945
and src/pmdas/linux_xfs/linux_xfs_migrate.conf.

Is it possible to do this?

Not with the pmlogrwrite today.

I've started thinking about this and think to address this case we need a clause of the form

indom 60.16 { indom -> duplicate 11.* }

rather than

indom 60.16 { indom -> 11.* }

This would leave indom 60.16 alone and create a new indom 11.16 with _identical_ instances.

This involves some messy logic to _add_ indom records (rather than just rewrite them) to the metadata file at multiple points in time.

I've done the easy flex/bison changes ... the rest will require some thought and time.

Feedback would be good before I charge too far into this bog of eternal stench.


<Prev in Thread] Current Thread [Next in Thread>