> Let me elaborate on this:
>
> > rrdtool update test.rrd 1477433700:15
> > # rrdtool update test.rrd 1477434000:NaN # here is a missed measuring
> > point
> > rrdtool update test.rrd 1477434300:8
>
> > Can anyone advise how to setup the rrd, so that one missing PDP gets
> > exactly one NaN ?
Let me elaborate on this:
> rrdtool update test.rrd 1477433700:15
> # rrdtool update test.rrd 1477434000:NaN # here is a missed measuring
> point
> rrdtool update test.rrd 1477434300:8
> Can anyone advise how to setup the rrd, so that one missing PDP gets
> exactly one NaN ?
The problem is
> Alex van den Bogaerdt wrote:
>
>> You are not writing points, you are writing rates which are measured
>> during some interval.
>> The rate "8" is for time 1477433700..1477434300. This is however not
>> allowed because of your heartbeat setting and gets lost.
>>
>> What
> > Hi,
> >
> > we use rrd to get an overview of our server farm. Every data point
> > that is monitored (disk usage, cpu, mem, temp., iops, bandwidth and so
> > on) gets written to rrd (and then gets visualized via drraw).
> >
> > Every now and then we get some timeout from the monitoring system
Alex van den Bogaerdt wrote:
> You are not writing points, you are writing rates which are measured
> during some interval.
> The rate "8" is for time 1477433700..1477434300. This is however not
> allowed because of your heartbeat setting and gets lost.
>
> What happens
> Hi,
>
> we use rrd to get an overview of our server farm. Every data point that is
> monitored (disk usage, cpu, mem, temp., iops, bandwidth and so on) gets
> written to rrd (and then gets visualized via drraw).
>
> Every now and then we get some timeout from the monitoring system (read: a
>
Hi,
we use rrd to get an overview of our server farm. Every data point that is
monitored (disk usage, cpu, mem, temp., iops, bandwidth and so on) gets written
to rrd (and then gets visualized via drraw).
Every now and then we get some timeout from the monitoring system (read: a
missing data