pcp
[Top] [All Lists]

Re: Archive pmLookupDesc errors (global derived metrics induced)

To: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Subject: Re: Archive pmLookupDesc errors (global derived metrics induced)
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 20 Apr 2016 00:20:40 -0400 (EDT)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5717011B.80607@xxxxxxxxxx>
References: <523501625.42032893.1461122796378.JavaMail.zimbra@xxxxxxxxxx> <5717011B.80607@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 9FwzvIiyFiMs9Smbly5dfhYdSYIYOw==
Thread-topic: Archive pmLookupDesc errors (global derived metrics induced)

----- Original Message -----
> On 04/20/2016 01:26 PM, Nathan Scott wrote:
> hmm, the root cause seems to be that derived metrics are always defined
> in the namespace, even if their operand metrics are not present in the
> archive, as below. It looks like event.flags and event.missed sort of
> similarly exhibit this issue too - they're both globally derived metrics
> defined by a call to __pmRegisterAnon() from __dminit() in libpcp.

Yep, but they're "safe" in that they are always valid.

> The global derived metrics should be omitted from the pmns somehow I guess,
> or maybe only defined if all their operands are present?

Yeah - the latter sounds better to me, if its possible - implementing it may
prove tricky.

cheers.

--
Nathan

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