| Cheshire Cat Computing http://www.steveshipway.org/forum/ |
|
| Cur In/Out and Last always 0.0 http://www.steveshipway.org/forum/viewtopic.php?f=2&t=1112 |
Page 1 of 1 |
| Author: | ecornwell [ Thu May 17, 2007 7:29 am ] |
| Post subject: | Cur In/Out and Last always 0.0 |
Hello! I just had a quick question. Whenever I look at all my graphs they all show Cur In and Out or Last as 0.0. I just went from 2.17 beta 8 to v2.18beta2 and it is still doing it. I've got two sets of configs. One in a common directory and a second set that I've got in a folder I call "Locations" for grouping. My RRD log files are broken up into folders for each type of device. Routers, Switches, Wireless, Other. I'm not sure if I have something configured wrong or just setup wrong. Any ideas? Thanks! -E |
|
| Author: | stevesh [ Thu May 17, 2007 11:09 am ] |
| Post subject: | |
This is due to a race condition with MRTG/RRD. Data is collected by MRTG and logged by RRDTool against the 5-min window in which it appears. However, if you subsequently generate a graph while in the next window, you can get this. EG, collect data at 12:04 and log it. It goes against the 12:00-12:05 window. Then, generate a graph at 12:06. This is in the next window, so the last same is displayed as 0 (unknown). routers2 does some tricks to try and get around this, but it is harder to avoid on userdefined graphs. What you can do to avoid it is one of these. 1. Make sure you data collection runs at the beginning of the 5-min window (hard) 2. Set the uselastupdate=yes option in the routers2.conf. This works, but if a device is down then you end up with a graph based on the last actual data retrieval (probably OK). This is what we do here. 3. Live with it (probably not what you want else you'd not have posted here) 4. Set the 'unknasprev' option in the routers.cgi*Options[]. This makes the graphs behave as per native MRTG, IE, with unknown data being displayed as the last known value. This may result in misleading graphs, though, if the device is ever unavailable. I'd suggest using the uselastupdate=yes option, as this alters the base time on the displayed graph to being the last update time of the RRD, rather than 'now'. Therefore, even if the time is 12:06 (and you're in the next timewindow) then the graph will be based at 12:05 (the end of the last updated window). |
|
| Author: | ecornwell [ Fri May 18, 2007 1:23 am ] |
| Post subject: | |
Steve you are awesome! I think I'm going to use the "uselastupdate" option. I imagine you've probably thought of this, but would it be possible to mix two of the options? Say it checks to see if the lastudate was within a window of say 10 min or so if it is, it uses the last update, if not it just shows nothing? Thank you for your quick response and great work on this project!!! -E |
|
| Author: | stevesh [ Fri May 18, 2007 10:50 am ] |
| Post subject: | |
Actually, the existing magic built into routers2 tries to do this - it goes back one sample if the last sample is unknown. However, it cannot always do this (due to various reasons) and sometimes it still shows the 0s. Also, if you have 'unknaszero' set, then routers2 has no way to know when the last real data was as an unknown is read as zero anyway! |
|
| Page 1 of 1 | All times are UTC + 12 hours [ DST ] |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|