Archive:System Monitoring

From Tardis
Revision as of 21:00, 12 October 2013 by Hayden (talk | contribs) (Text replace - "^" to "<div style="width:55%;margin:0 auto;border:2px solid;border-left:20px solid;border-color:#d9534f;text-align:center;padding:5px;font-weight:bold;">This page is out of date and needs rewriting.<br /> The content is likely to be incomp)
Jump to: navigation, search
This page is out of date and needs rewriting.
The content is likely to be incomplete or incorrect.
This service does not currently exist if you would like to reinstate it please contact us. The following information should be for historical interest only.

Munin

We're running munin for some out of the box monitoring fun, which can be seen at [1].

To add a new host to this, on the box you wish to monitor:

colin:~# apt-get install munin-node
...
colin:~# vim /etc/munin/munin-node.conf

and add...

allow ^193\.62\.81\.11$

and don't forget to...

colin:~# /etc/init.d/munin-node restart

Also on davros, edit /etc/munin/munin.conf to add:

[colin.tardis.ed.ac.uk]
    address 193.62.81.8
    use_node_name yes

Custom plugins

Some custom plugins have been written to monitor:

  • The number of items in the support inbox
  • The number of people logged into gallifrey

WOTAN uses the IPMI monitoring plugin from here. It has been changed to suit the idiosyncrasies of WOTAN's IPMI implementation. These changes should be documented some time...

Piper uses the standard sensors_ plugin, which relies on data from lm-sensors.

Malcolm

  • Munin occasionally sends reports to Malcolm, bung's irc bot, for example when cpu usage exceeds a threshold. These alerts can be seen in #tardismon