pcp
[Top] [All Lists]

Re: [pcp] GSOC 2016 idea for PCP

To: Lukas Berk <lberk@xxxxxxxxxx>
Subject: Re: [pcp] GSOC 2016 idea for PCP
From: Charles Cui <charles.cui1984@xxxxxxxxx>
Date: Sat, 12 Mar 2016 20:17:01 -0800
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=pdtJmAObZoJblvyO54AxTZezUmjAvmBPX2f0iEe+7hc=; b=HY4jgJE6Rvk43V2ozym48T85TtM3WakIxr0YYZneyX5tBc/z2KPDwQx5cpu5C0BcH4 OSRobHcosespjm+ukgMzb3sDGD0RWnRcrHbu1kguz4xmL2LbIANCx5KOfKk2DdnymcHe jZ8yqmd0QJnPhEs1mezYaYMxfOp8W+JigwOYhivTBiAsio9VwGLh3eG/Dmq3AiQY53xX Rhy3tTPCxT6aF62ND9xieJsBTKMmKyKI9LLdmfvUSxu6rjwmMICMV3EmkFDJ5HNQgCA+ eiTT8hoeWqAMZF4D+Ii64BnuCEhOjCrAAWz8aRVCiDmN5hBf39AmRCaUpBQkkAhHkyOW riCA==
In-reply-to: <87io0v8iv2.fsf@xxxxxxxxxx>
References: <CA+SXE9v2ExnLbnGfQJxeeJA1V6fJdNHcLyyo8-ZYHoaE25MSFQ@xxxxxxxxxxxxxx> <87si089svf.fsf@xxxxxxxxxx> <CA+SXE9tcjaMpz1BL8D_6PEAWte1YTPPBW_W7XUX1RBST=yML4w@xxxxxxxxxxxxxx> <874mcntvhv.fsf@xxxxxxxxxx> <CA+SXE9u6W16mmN9eEkQh=ZXwGFNGkwo-avqW+gNAyEoMvaoxew@xxxxxxxxxxxxxx> <CA+SXE9vODZDqMAnn8MKvxp7QRka+8S0-NYFbLjT1fp4FsndDyw@xxxxxxxxxxxxxx> <874mch8xsf.fsf@xxxxxxxxxx> <CA+SXE9tU==8M2AqthqwsjmrL9DqHh+M8koSSQEEfvoH=NvhWug@xxxxxxxxxxxxxx> <87io0w794p.fsf@xxxxxxxxxx> <CA+SXE9sqGQwHsYTqkJbnH98BOzFrz9KBGVsY1z6tnw3Xx+g5bg@xxxxxxxxxxxxxx> <87io0v8iv2.fsf@xxxxxxxxxx>
Hi Lukas,

   Some updates for this project.
I tried to install and use simple and trivial pmda, and they can
report me the expected metrics.
Now, I am thinking of steps of writing the pmds using golang.
Some thoughts are given below, correct me if I am wrong.
Basically, there are 2 ways to go.
1>  I need to at first to create a wrapper of lib pcp_pmda using golang, where
provides similar name to functions in lib pcp_pmda but implemented
using golang.
For each function in the wrapper, it calls the lib pcp_pmda to
complete the function.
Then, create an agent (with golang) to talk with my wrapper.
or
2> rewrite lib pcp_pmda using golang

which way is preferred by the community?

Thanks, Charles

2016-03-09 13:02 GMT-08:00 Lukas Berk <lberk@xxxxxxxxxx>:
> Hi Charles,
>
> Charles Cui <charles.cui1984@xxxxxxxxx> writes:
> [...]
>> I add the pcpqa user into the system, and run test under the
>> pcp-testsuite package.
>> When I run "./check -g sanity -x flakey" it has permission problem.
>> So, I issued the command with sudo, which executed without any errors.
>
> Awesome!  Yes, pcpqa requires sudo (staring stopping pcp services, among
> other things).  Personally I have it setup under sudo with nopasswd to
> make things eaiser, however I'm aware some individuals aren't
> comfortable doing so, up to you.
>
>> In terms of the testsuite, (sudo ./check 000-)
>> some tests report problem like output mismatch, or some packages are
>> not found(e,g, no docker binary found),
>> but most of these tests pass.
>> Do I need to investigate the test with problems and fix them?
>
> Having tests return '[notrun] ...' is perfectly fine.  So long as there
> doesn't seem to be any major problems with the setup I wouldn't be
> overly worried about a few fails for now (assuming there isn't a clear
> pattern you can see with them).  QA is quite important to the pcp
> community as a whole, might be worth mentioning your testing plan in a
> propsal at some point :)
>
> [...]
>>     Sure, just be aware that we do have a memcache pmda, as well as
>>     several
>>     database pmdas already (check src/pmdas/ for a full list). That
>>     being
>>     said, there are always more databases to monitor. Feel free to
>>     choose
>>     one you're interested in and detail it in your proposal.
>> I looked at the listed provided, I think I can write agents to monitor
>> redis or cassandra database,
>> if that's possible.
>
> Sure, keep in mind that some data sources are easier to extract
> meaningful metrics out of than others, and feel free to detail the
> decisions behind your choice in the proposal!
>
> Cheers,
>
> Lukas

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