Thank you, I wasn't aware of that. That led me to some more reading. ;)

The values were selected by rrdtool at the time of the logic, I had no
input into the conversion between the log file format and the rrd format.
As I'm looking at the data, I'm seeing the heartbeat set to 120. So
basically, that means that I'll get socked with "unknown" values twice for
every 5 minute data point? If so and that were an acceptable result, what
would be the way to initiate that? The current RRD is storing data for
every 300 seconds, so even though MRTG/rrdtool is cron-ed to run every
minute, I'm still only keeping data at a 5 minute resolution.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex van den
Bogaerdt
Sent: Tuesday, June 15, 2004 9:12 PM
To: [email protected]
Subject: [rrd-users] Re: RRD migration


On Tue, Jun 15, 2004 at 10:25:17AM -0500, [EMAIL PROTECTED] wrote:

> I'd like to fix this, though I realize that you can't increase the 
> resolution of historical data, only decrease. What I'm wondering is if 
> I can dump the data, build new RRD's with 60 second resolution, 
> duplicate each record an additional 3 times and reimport it, thus 
> giving me an appropriate 60 second breakdown.

If the heartbeat is set to a number large enough, one single update will
fill more than one CDP.  No need to duplicate data.

HTH
Alex
-- 
I ask you to respect any "Reply-To" and "Mail-Follow-Up" headers.  If you
reply to me off-list, you'd better tell me you're doing so.  If you don't,
and if I reply to the list, that's your problem, not mine.

--
Unsubscribe mailto:[EMAIL PROTECTED]
Help        mailto:[EMAIL PROTECTED]
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi



--
Unsubscribe mailto:[EMAIL PROTECTED]
Help        mailto:[EMAIL PROTECTED]
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

Reply via email to