pcp
[Top] [All Lists]

Re: Gathering metrics from other hosts.

To: "Brent M. Clements" <bclem@xxxxxxxx>, David Chatterton <chatz@xxxxxxxxxxxxxxxxx>
Subject: Re: Gathering metrics from other hosts.
From: Kevin Wang <kjw@xxxxxxxxxxxxx>
Date: Sat, 27 Mar 2004 18:14:05 -0800
Cc: pcp@xxxxxxxxxxx, Jan-Frode Myklebust <janfrode@xxxxxxxxxxxxxxx>
In-reply-to: <40660C14.8060004@melbourne.sgi.com> <Pine.GSO.4.58.0403271340290.29724@is.rice.edu>
References: <Pine.GSO.4.58.0403271340290.29724@is.rice.edu> <20040327205404.GA11064@ii.uib.no> <Pine.GSO.4.58.0403271505270.6245@is.rice.edu> <40660C14.8060004@melbourne.sgi.com> <Pine.GSO.4.58.0403271340290.29724@is.rice.edu>
Sender: pcp-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
 From Brent M. Clements
> According to the pcp project page
> 
> "A client-server architecture allows multiple clients to monitor the same
> host, and a single client to monitor multiple hosts (e.g. in a Beowulf
> cluster). This enables centralized monitoring of distributed processing."
> 
> But, there is nowhere in the documentation that explains how to do this.
> 
> If I wanted to do the following:
> 
> Centralized Monitoring Server(master node in cluster) would gather metrics
> from multiple hosts(compute nodes in a cluster). How would one actually do
> this?

As David Chatterton elaborated, pcp is made up of servers and client
software.

pmcd is the daemon that listens on the network for requests for data,

pmlogger is *one* of the clients that talks to the networked pmcd daemons.
There are lots of other tools available, but all of the tools have the
ability to talk across the network to any server.

The tools are extremely generalized and they all can read/write from
the standard pmcd network daemons and archive files.

Note that any network requests are lossy, so if you're collecting
performance data and can't afford to lose any data points, you still
need to log locally to disk.

   - Kevin Wang, kjw@xxxxxxxxxxxxx

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