Hi<br><br><div class="gmail_quote">2010/1/10 Marc Tobien <span dir="ltr"><<a href="mailto:Marc@tobien.net">Marc@tobien.net</a>></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't experience that issue.<br>
<br>The issue of rrd putting unknown only occurs if the time between various updates' timestamp is more than the set heartbeat.<br><br> There's no problem if you'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>