pcp
[Top] [All Lists]

Re: [pcp] Dynamic metric rework

To: Martins Innus <minnus@xxxxxxxxxxx>
Subject: Re: [pcp] Dynamic metric rework
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Fri, 12 Dec 2014 01:25:13 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5489F5D1.6050208@xxxxxxxxxxx>
References: <5481E4D7.8050700@xxxxxxxxxxx> <991616924.12928901.1418084187235.JavaMail.zimbra@xxxxxxxxxx> <54876B8F.2050106@xxxxxxxxxxx> <428025601.13619915.1418163615228.JavaMail.zimbra@xxxxxxxxxx> <548897F5.4010905@xxxxxxxxxxx> <1194215403.14908758.1418289588303.JavaMail.zimbra@xxxxxxxxxx> <5489F5D1.6050208@xxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: dxMY/xJlaDspB2DQiCt0JCxqxVEY7Q==
Thread-topic: Dynamic metric rework
Hi Martins,

----- Original Message -----
> [...]
> OK, how about something like this?  The first test is the actual
> failure, the next 2 are contrived, the last is making sure there are
> some dynamic metrics generated.  I have made the assumption that there
> should be at least 3 interrupts on any platform that the linux pmda runs
> on.  If it ends up failing somewhere, will need to be made conditional
> on something ( architecture?).
> 
> Test as well as good and bad files attached.

Looking good!  One gotcha to watch for is the "getdesc on" which will cause
a DESC pdu to be sent, I think (you can use -Dpdu on dbpmda command line to
verify that).

cheers.

--
Nathan

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