pcp
[Top] [All Lists]

Re: [pcp] PCP Network Latency PMDA

To: William Cohen <wcohen@xxxxxxxxxx>
Subject: Re: [pcp] PCP Network Latency PMDA
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Wed, 20 Aug 2014 16:48:18 -0400
Cc: David Smith <dsmith@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <53F5049A.8040509@xxxxxxxxxx>
References: <53A34A47.3060008@xxxxxxxxxx> <y0mk38caa4t.fsf@xxxxxxxx> <53A353C8.8030704@xxxxxxxxxx> <53A35C00.1070703@xxxxxxxxxx> <53EA6650.6040500@xxxxxxxxxx> <53EB7A09.7070503@xxxxxxxxxx> <53EB9262.104@xxxxxxxxxx> <53EBB063.9040103@xxxxxxxxxx> <53F5049A.8040509@xxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -

> $ ../install/bin/stap  ../../net_xmit_mmv.stp em1 loem1 0
> lo 1
> argv[1] = em1, inst[em1] = 0
> argv[2] = lo, inst[lo] = 1
> 
> In another window can get information out with mmvdump:
> [...]

OK, it should take only one small step past this before getting the
data through normal pcp clients: namely arranging for that /mmv
file to be visible to the mmv pmda agent process.  To do that,
add to the mmv.stp tapset something like this:

probe begin {
  system(sprintf("ln -s /proc/systemtap/%s/mmv /var/lib/pcp/tmp/mmv/%s",
                 module_name(), module_name()))
}
probe end,error {
  system(sprintf("rm -f /var/lib/pcp/tmp/mmv/%s",
                 module_name()))
}

Then, something like  

% pminfo -f mmv

should show the values.


- FChE

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