[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rrd-users
Subject:    Re: [rrd-users] setting up the steps and heartbeat for database
From:       Jean-Yves Avenard <jyavenard () gmail ! com>
Date:       2010-01-09 23:28:04
Message-ID: cb44e8371001091528w5a48b0d9t516417b8ce58b7ce () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi

2010/1/10 Marc Tobien <Marc@tobien.net>

> Every set of dates is holding the exact timestamp of measurement.
>
> I do not have the problem to write the dates with update  into the rdd
> database , but the unknown entered automatically if dates are not coming =
in
> time or with a bad interval are messing up the average. See my example.
> There can be a time different between taking the measurement and getting =
the
> data=92s of 35 minutes. That is normal. If there is a breakdown of the li=
ne,
> time can rise up to 900 minutes, that is the buffer of the  Device.
>
> Data=92s will then be deliver after a reconnect.
>

Then when you do the rrd update, you should simply specify the timestamp at
which the measurement was done ; and you won't experience that issue.

The issue of rrd putting unknown only occurs if the time between various
updates' timestamp is more than the set heartbeat.

 There's no problem if you're doing the update every 900 minutes as long as
each update has the right timestamp.

Hope that makes sense to you...

[Attachment #5 (text/html)]

Hi<br><br><div class="gmail_quote">2010/1/10 Marc Tobien <span dir="ltr">&lt;<a \
href="mailto:Marc@tobien.net">Marc@tobien.net</a>&gt;</span><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div link="blue" vlink="purple" lang="DE"><div>











<span lang="EN-US">Every set of dates is holding the exact timestamp
of measurement.</span>

<p class="MsoNormal"><span lang="EN-US">I do not have the problem to write the dates
with update  into the rdd database , but the unknown entered automatically
if dates are not coming in time or with a bad interval are messing up the
average. See my example.  There can be a time different between taking the
measurement and getting the data’s of 35 minutes. That is normal. If
there is a breakdown of the line, time can rise up to 900 minutes, that is the
buffer of the  Device.</span></p>

<p class="MsoNormal"><span lang="EN-US">Data’s will then be deliver after a \
reconnect.</span></p></div></div></blockquote><div> </div><div>Then when you do the \
rrd update, you should simply specify the timestamp at which the measurement was done \
; and you won&#39;t experience that issue.<br> <br>The issue of rrd putting unknown \
only occurs if the time between various updates&#39; timestamp is more than the set \
heartbeat.<br><br> There&#39;s no problem if you&#39;re doing the update every 900 \
minutes as long as each update has the right timestamp.<br> <br>Hope that makes sense \
to you...<br></div></div>



_______________________________________________
rrd-users mailing list
rrd-users@lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users


[prev in list] [next in list] [prev in thread] [next in thread]