[pcp] Proposal for handling dynamic metric names (and hence dynamic metrics)
nscott at aconex.com
Thu Jul 9 19:33:13 CDT 2009
----- "Ken McDonell" <kenj at internode.on.net> wrote:
> (news, kvm, dbping, zimbra, netfilter, bonding, systemtap, vmware,
> memcache, oracle, mysql) - Nathan, what needs to happen here as the
> pmda support seems to be using libpcp_pmda and PMDA_INTERFACE_LATEST?
That should be PMDA_INTERFACE_3, yeah, until such time as support
for the new callbacks is added to the Perl API. I''l fix that up.
> I think if a dynamic PMNS works as I plan, then mmv could use this
> rather than the NOTREADY-READY approach.
Yep, that'd be good.
> > And having a 'pad' field in the middle of a structure seems kind
> > of funky, but I can see the reasoning for wanting it there. Maybe
> > just use up the two existing pad bits and call it 'flags'? (with
> > room for three more flag values in the future, one of which could
> > be to flag an extended range of domain values).
> There seems to be support for moving to 9 bits of domain and dropping
> the pad ... I happy to do that and include it in the QA validation
> for the other pmns changes.
+1 vote from me there.
More information about the pcp