munin
munin copied to clipboard
munin-monitoring
Munin needs a persistent database
Munin is in need of a persistent database.
Munin will only display data for hosts and services present in the last run of munin-update.
If a host is down, it disappears from the graphs.
If munin-update is run with options limiting the hosts or services, all other hosts and services are gone from the web pages until the next run of munin-update.
Munin needs a place to store data about inactive hosts, as well as storing other data, like events.
Oh, I am so longing for this feature! ;-)
Seriously, I like munin alot. I even prefer it to cacti, nagios and all the other players in the field. Munin provides mostly what I need without the hassle other sw pieces challenge you with.
BUT, munin should not make hosts unreachable or not reporting back correctly drop from the generated stats list. Maybe mark it red or whatever but I need to know "there's a host with issues to solve".
Right now, it is like "Well, the list of hosts is long, let's count them to see whether all of them are accounted for or something is amiss".
Together with a solution to that "IPv4/IPv6 listen and accept answers" #1175 (I mean the IPv6 reverse lookup and Net::Server part of it) issue it would silence my hickups with munin definitely. ;-)
Cheers
BUT, munin should not make hosts unreachable or not reporting back correctly drop from the generated stats list.
This is indeed a bug (#579), that was just recently fixed (9a94816a2b0051119d9660e0a274e41e8db6da29). Thus you should be freed of this nuisance since v2.0.48.
I hope, this improves your life until munin 3.0 jumps out of its cave :)
@sumpfralle Thank you for your kind words :)
For clarification: I was talking about those "host will disappear messages" in the log files. I find it annoying to loose hosts temporarily unreachable (might be days, sometimes weeks, but they will come back; they always do! ;-) .
Cheers
I am not aware, whether there is currently a mechanism, that will really remove these nodes (but maybe it is hidden somewhere). Up to now they were removed accidentally due to #579.
Thus I think, with this bug fixed the topic is reduced to a log message annoyance.