pcp
[Top] [All Lists]

Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: Multi-Volume Archive + Live Data Playback for PCP Client Tools
From: Dave Brolley <brolley@xxxxxxxxxx>
Date: Thu, 02 Oct 2014 11:55:23 -0400
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <y0m1tqqcym4.fsf@xxxxxxxx>
References: <542C21AE.1010504@xxxxxxxxxx> <y0megurfxp7.fsf@xxxxxxxx> <542C4EC1.4040407@xxxxxxxxxx> <408521091.60123629.1412223728964.JavaMail.zimbra@xxxxxxxxxx> <y0m1tqqcym4.fsf@xxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
On 10/02/2014 10:52 AM, Frank Ch. Eigler wrote:
nathans wrote:

I didn't follow the need to talk to pmlogger - what was the rationale
there?
In the grand unified world, there will be a need to talk to
-something- that has both historical data and live data.  Making
pmlogger into a network server would make it possible to have libpcp
engage in conversation with only a single thing.  pmlogger already
knows about its own archives as well as the pmcd it's pulling from.
No coincidences or client-side magic required, so to speak.
Yes, that was the idea behind this suggestion. This would only be required for archive-transitioning-to-live situations. Historical-only, which is what I will address initially need not use a pmlogger and, in fact, a pmlogger need not even be running for this case.

It just seemed to me that the archive-to-live case implied the existence of one or more running pmloggers and that each was already managing everything needed to make the transition.

Dave

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