pcp
[Top] [All Lists]

Re: PCP versions of console tools - Next Steps

To: Sitaram Shelke <sitaramshelke@xxxxxxxxx>, Ryan Doyle <ryan.doy@xxxxxxxxx>, pcp@xxxxxxxxxxx
Subject: Re: PCP versions of console tools - Next Steps
From: Ryan Doyle <ryan@xxxxxxxxxxxx>
Date: Sun, 08 May 2016 19:26:54 +1000
Cc: Nathan Scott <nathans@xxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <CAHnM1zzTfNgt4Hsgt_Pgq7M-yz+ewd_FehB+QMxixE1MFfKOvA@xxxxxxxxxxxxxx>
References: <CAHnM1zzTfNgt4Hsgt_Pgq7M-yz+ewd_FehB+QMxixE1MFfKOvA@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.3.0
Hi Sitaram

> I am really sorry but I think there has been some issue with my mail
> account as I did not recieve any mails from your mail id

That's weird, I've been sending to the mailing list as well as sending to you directly. Have you been receiving other emails from the mailing list? If we continue to have trouble I might just switch over to using my GMail account.

> Now that I have read all the mails, I'll start immediately. As mentioned
> in the mail I would be writing a simple code to use pmapi.h to grab
> disk.all.read metric and then we can start with the pidstat.

Sounds good. I'd suggest starting with the Python version of pmapi instead of the C pmpai.h version. It's most likely what we will want to use for writing a PCP-variant pidstat. Have a look at 'src/pcp/uptime/pcp-uptime.py' as a starting point.

If you've already had a look at the C pmapi.h thats great - what you've learned in that applies pretty much 1-to-1 for the Python pmapi.

For the first task of printing out 'disk.all.read', are you able to put the code up somewhere on-line that we can check out?

We'll have a chat again about pidstat once you've had a chance to play with pmapi.

Cheers!
Ryan

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