You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debian Bug #97352
mrtg: a way to ignore hosts that are unreachable.
Reported by: Sami Haahtinen [email protected]
Date: Sun, 13 May 2001 18:48:17 UTC
Severity: wishlist
Found in version 2.9.10-1
it would be nice to have a feature to ignore hosts that are down, at the moment (atleast hosts that need to be walked) give out a warning and appear as void in the graphs. and as the graph is drawn from the void data it appears that the host had for example the same load while it was down. which is not true.
This might be good for hosts that aren't in the same network, but it's not a good thing for hosts that tend to be down now and then.
the right way to deal with this would be to dump 0 as the value when a host is down.
The text was updated successfully, but these errors were encountered:
I've wanted something like this for a while and also something to better detect device reboots (as measured by sysUpTime) when rrdtool is used (i get counter overflow handling kicking in and massive graph spikes). I lack decent perl coding skills but was starting to tinker around with adding some extra flag in the target defs to teach mrtg 'stuff zeros into the graph if this host is offline' where offline is determined by some other external probe.
This is a bug from Debian. Thanks.
Debian Bug #97352
mrtg: a way to ignore hosts that are unreachable.
Reported by: Sami Haahtinen [email protected]
Date: Sun, 13 May 2001 18:48:17 UTC
Severity: wishlist
Found in version 2.9.10-1
it would be nice to have a feature to ignore hosts that are down, at the moment (atleast hosts that need to be walked) give out a warning and appear as void in the graphs. and as the graph is drawn from the void data it appears that the host had for example the same load while it was down. which is not true.
This might be good for hosts that aren't in the same network, but it's not a good thing for hosts that tend to be down now and then.
the right way to deal with this would be to dump 0 as the value when a host is down.
The text was updated successfully, but these errors were encountered: