pcp
[Top] [All Lists]

Re: [pcp] Querying a single instance of metric

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] Querying a single instance of metric
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Thu, 29 Mar 2012 09:44:12 +1100
In-reply-to: <4F736B36.1050604@xxxxxxxxxxxxxxxx>
References: <1494230283.380626.1332889667045.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx> <4F736B36.1050604@xxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1
On 03/29/2012 06:49 AM, Ken McDonell wrote:
I suspect it is worth making this change.

The original history (if I recall it from so long ago) was that pminfo needed to
be as lightweight as possible (the Akmal factor for those who remember) and this
was before pmprobe existed. The extra PDU round-trips to fetch and validate the
instance domains were to be avoided.

I vaguely remember some history here too - the semantics were a bit
too messy when a non-leaf is specified. e.g.
pminfo -f kernel.percpu.cpu["cpu0","cpu1"]
would be ok because all metrics in that subtree share the same
instance domain, but it gets messy when they don't. pminfo
currently allows a non-leaf to be queried and will happily
fetch all instances for all metrics in the subtree. But that
wont consistently work if a specific instance is requested.

pmdumptext just returns an error if a nonleaf node is requested:

$ pmdumptext kernel.percpu.cpu["cpu0"]
pmdumptext: Error: r/lib/pcp/config/pmcd/pmcd.options:ib/pcp/config/pmcd/pmcd.conf: Metric name is not a leaf in PMNS
pmdumptext: no valid metrics, exiting.

hmm, there's a bug in the error handling somewhere ...

Regards
-- Mark

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