Ticket #447 (assigned enhancement)

Opened 5 years ago

Last modified 2 weeks ago

Better error detection/handling

Reported by: lkstrand - lars at linpro no Assigned to: janl (accepted)
Priority: normal Milestone: Munin 2.1
Component: master Version:
Severity: normal Keywords:
Cc:

Description

I would really like to see the following improvement in Munin:

  • More verbosity upon detecting errors when parsing the munin.conf file. As of today, pinning down exactly what is wrong in the config file can be a tiresome exercise when dealing with aggregated graphs. Example: When grap_order lists a unknown field, the graph just don't generate. Some sort of verbosity level setting would be nice.
  • Some way of telling when a host no long is responsive (no contact, host is down for say 15 minutes) on the front page. This can for example be denoted by a red star (*) after the hostname. I am aware that we usually have Nagios or other tools to detect more immediate alerts, but take for example: I just checked a host by random today, and munin had not getting any data for the last 5 days(!). The host was up and Nagios reported no problems. It turns out that the munin-node was not running on that particular hosts. This could easily been detected by some form of notice on the front-page.

Change History

11/12/06 17:15:00 changed by janl

  • owner changed from nobody to janl.
  • status changed from new to assigned.
  • version deleted.
  • milestone set to Munin 1.4.

Pt. 1 is not high on my priority list. Pt. 2 is on my agenda already.

11/14/09 23:40:53 changed by janl

  • milestone changed from Munin 1.4 to Munin 1.5.

01/24/12 16:35:24 changed by snide

  • milestone changed from Munin 2.0 to Munin 2.1.