pcp
[Top] [All Lists]

Re: [pcp] Dynamic Proc PMDA metrics

To: Martins Innus <minnus@xxxxxxxxxxx>
Subject: Re: [pcp] Dynamic Proc PMDA metrics
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 17 Nov 2014 01:39:44 -0500 (EST)
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <63EB3786-F60E-40C5-AB91-7EC80FD91CA9@xxxxxxxxxxx>
References: <545D2CFA.1050600@xxxxxxxxxxx> <1477043892.10880496.1415600819766.JavaMail.zimbra@xxxxxxxxxx> <54627B7D.6040906@xxxxxxxxxxx> <2023629481.12445911.1415770455874.JavaMail.zimbra@xxxxxxxxxx> <5463C8C8.5010700@xxxxxxxxxxx> <1453660478.13246038.1415858528343.JavaMail.zimbra@xxxxxxxxxx> <54650E07.90908@xxxxxxxxxxx> <63EB3786-F60E-40C5-AB91-7EC80FD91CA9@xxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: aR7zolYWr8UjYBFLwOf6JncCWxU7nw==
Thread-topic: Dynamic Proc PMDA metrics
Hi Martins,

----- Original Message -----
> > [...]
> > This assumption is also made in the following methods:
> > 
> > pmdaDynamicLookupPMID
> > pmdaDynamicLookupText
> > 
> > These will use the first tree that has the matching cluster.
> > 
> > Actually.  Thinking this through. Something like the attached patch could
> > fix this issue once we can get the domain # in the source metric. I can't

(no patch attached?)

> [...]
> I now have a fix for this.  I modified dynamic.c significantly to get rid of
> the checks against cluster and prefix.  They are not used at all, I just
> left the prefix in for now since it is used to do the cluster mask.  I'm not

OK.

> sure if that will be needed in the new cgroups anymore.

Nope.

>    All the checks are now done just against the pmns. This allows there to be
>    only one setup call for dynamic proc metrics.

Yep - sounds simpler & betterer.

cheers.

--
Nathan

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