pcp
[Top] [All Lists]

Re: [pcp] PCP libvirt PMDA

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] PCP libvirt PMDA
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 22 Jul 2016 09:13:33 +1000
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <569e19e4-d304-ebee-828f-629ac82a3b5e@xxxxxxxxxx>
References: <1fa58d82-ac73-7747-c58d-acf880bc2155@xxxxxxxxxx> <20ae899d-50c6-1457-644f-f45ad26c63d4@xxxxxxxxxx> <37250089.6949181.1468900166388.JavaMail.zimbra@xxxxxxxxxx> <fc9e92aa-355e-6cc1-7586-599847cf6cbe@xxxxxxxxxx> <1473242169.7374530.1468971331935.JavaMail.zimbra@xxxxxxxxxx> <810341356.7539206.1469047436415.JavaMail.zimbra@xxxxxxxxxx> <569e19e4-d304-ebee-828f-629ac82a3b5e@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
On 22/07/16 09:06, Marko Myllynen wrote:
...
On 2016-07-20 23:43, Nathan Scott wrote:
...
I forgot another biggie yesterday - related to the persistence of PMIDs.
Its important to a number of the client tools (pmlogger, pmie, pmchart,
hmmm pretty much all actually) that if pmcd is restarted, metrics return
with the same PMID as before (this is pretty much part of the protocol
over-the-wire, and its also necessary on-disk between archives of the
same host).

This becomes very difficult to ensure in the case of dynamic metrics -
it was the main reason we switch cgroups to using this model IIRC.  And
the pmdaCache interfaces support persisting instance identifiers well of
course.

Just a note in passing ...

With only a slight bending of the semantics, the pmdaCache routines can be used to maintain a persistent mapping between the tail of a metric name and the low-order bits of a PMID. Just choose an (otherwise unused) instance domain for the PMDA, then ...

pmns name -> external instance name
pmid -> internal instance name

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