pcp
[Top] [All Lists]

Re: [pcp] Culling code from libpcp

To: Max Matveev <makc@xxxxxxxxx>
Subject: Re: [pcp] Culling code from libpcp
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Fri, 7 May 2010 16:07:24 +1000 (EST)
Cc: pcp@xxxxxxxxxxx, kenj@xxxxxxxxxxxxxxxx
In-reply-to: <19426.46840.738870.51216@xxxxxxxxxxxx>
----- "Max Matveev" <makc@xxxxxxxxx> wrote:

>  kenj> No ... if one separates the UI event-driven goo from the sync
> PCP glop
>  kenj> things tend to "just work".
> As gnb has said, if there a sudden drop in TCP or if pmcd on one of
> the hosts takes a bit too long to extract metrics then it just stops
> working and attempts to catch up later by skipping all hosts just to
> cater for a slow one.

That's just not what happens.  It might appear that way, but its not.
And I certainly have seen many occurrences of data dropped/missed/lost
connection on one host of five being monitored that is successfully
handled with just that host missing data in one of many charts.

What platform are you running pmchart on OOC?

> Speaking of bloat - I've got a unfinished wireshark dissector written
> in Lua which can grok PCP protocol and display if nicely when added
> to
> Lua-enabled wireshark and I'm looking for a home for it. Should I
> park
> it somewhere in the pcp tree or is there a better place for it?

>From a quick google (lua wireshark wiki), sounds look lua is for
prototyping and better to write plugins in C (lua support is not
mergedin wireshare?) ... if the pcp protocol support could get
merged into wireshark, that would be much better of course... is
that feasible, so that it can work out-of-the-box?

Feels like it may just bitrot in the source tree, but maybe not.
A separate git tree (with links on web pages?) on oss would be
another decent option.

cheers.

-- 
Nathan

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