> Interesting! I used to do this, but in a "convoluted" sort of way - > running a shell script (via crontab) which checks various logs for > "hits" (i.e. when a packet is bounced by netfilter for example) and > then > logs them to RRD. Although the "hits" produced are obviously not > happening regularly, the script checking these is. Out of interest, > what > would happen if I do run and log data at irregular intervals to RRD?
If you log data at irregular intervals, then you'll get three effects. 1. Data normalisation - your samples will be modified to fit into the RRD's interval. This is common; however for small values, this can cause problems, particularly if you are interested in the actual values and not the rate. 2. XFF making RRA cdps unknown. If you have insufficient samples in an interval, then an RRA may set the value for that cdp to unknown. 3. Heartbeat making data points unknown. This is your biggest risk. You MUST have a sample AT LEAST as often as the heartbeat. If the heartbeat is smaller than your interval, then an interval will be set to unknown unless multiple values are received during it. If your heartbeat is exceptionally large, then one sample may case several data points to be created! This can be strange. You could, for example, log the total number of bounced packets on a regular basis. This would work. Or, every (regular) interval, log the number of packets bounced since the last update. What you should not do is to only log something if and when you bounce a packet. Steve Steve Shipway ITS Unix Services Design Lead University of Auckland, New Zealand Floor 1, 58 Symonds Street, Auckland Phone: +64 (0)9 3737599 ext 86487 DDI: +64 (0)9 924 6487 Mobile: +64 (0)21 753 189 Email: [email protected] Please consider the environment before printing this e-mail
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
