pcp
[Top] [All Lists]

Re: [pcp] Containers analysis with PCP

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] Containers analysis with PCP
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Tue, 10 Feb 2015 11:10:39 +1000
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1959010667.1788714.1423530305916.JavaMail.zimbra@xxxxxxxxxx>
References: <2100915892.5240937.1422867358164.JavaMail.zimbra@xxxxxxxxxx> <768474811.5242777.1422867576642.JavaMail.zimbra@xxxxxxxxxx> <y0m7fvr3tem.fsf@xxxxxxxx> <54D9447B.203@xxxxxxxxxx> <743115533.1781377.1423528533840.JavaMail.zimbra@xxxxxxxxxx> <54D955EB.4040201@xxxxxxxxxx> <54D95796.9050106@xxxxxxxxxx> <1959010667.1788714.1423530305916.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
On 02/10/2015 11:05 AM, Nathan Scott wrote:


----- Original Message -----
[...]
Also, would it be a bit more user-friendly if the external instance
names were the container name instead of the container-id?

Yeah, I thought alot about that but went with the hash in the end because it
means we need to do alot less work in the PMDA for each instance refresh.

well the id<->name is 1:1 isn't it? So shouldn't be a lot of extra work??
And you could have a containers.id metric whose indom is the name and value
is the id (to export the mapping). An ascii string name is a lot easier to
use (and remember) than a whopping 64 character hash id :)


BTW  pminfo -f containers.state.running  shows none are running, but I know
for sure that one of them is.

Hmm, thats a good clue.  Can you send through the container.pid values?, keen
to see what pmdaroot discovered there.

containers.pid should pid is 0 for all containers.

I'll fire up gdb and see where the ENOSUP is coming from (might
not be until later today ...)

Cheers

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