Munin - Revision history

PhilippeTeuwen: Reverted edits by Etegohy (Talk) to last revision by PhilippeTeuwen

2010-11-24T20:34:09Z

Reverted edits by Etegohy (Talk) to last revision by PhilippeTeuwen

Can't load revision 6826

at 00:28, 24 November 2010

2010-11-24T00:28:50Z

Can't load revision 6665

PhilippeTeuwen: /* sensors_ plugin */

2008-02-12T23:19:34Z

sensors_ plugin

@@ Line 55: / Line 55: @@
 But sth is really wrong no way to get a section only considered by the -isa- and the other by -i2c-, whatever I tried both sections were submitted to the same filtering rules :-(
 But the entry order was not the same as before, the sections have to be inverted and some new values must be postponed to the end to keep the uniformity in the history values.
  [sensors_*]
  env.sensors sensors|awk 'b==1{p=p"\n"$0};b==2&&/^in/{o=o"\n"$0;next};b==2;/^$/{b+=1};END{print p o}'
 ====Other plugins====

85.234.199.11: /* sensors_ plugin */

2006-11-29T23:38:24Z

sensors_ plugin

← Older revision		Revision as of 23:38, 29 November 2006
Line 57:		Line 57:
	Last resort was to change the output of sensors when called by munin:		Last resort was to change the output of sensors when called by munin:
	<br>In /etc/munin/plugin-conf.d/munin-node:		<br>In /etc/munin/plugin-conf.d/munin-node:
	[sensors_]		[sensors_*]
	env.sensors sensors\|sed '1,+14d'		env.sensors sensors\|sed '1,+14d'
			But the entry order was not the same as before, the sections have to be inverted and some new values must be postponed to the end to keep the uniformity in the history values.
			<br>So it becomes:
			[sensors_*]
			env.sensors sensors\|awk 'b==1{p=p"\n"$0};b==2&&/^in/{o=o"\n"$0;next};b==2;/^$/{b+=1};END{print p o}'

	====Other plugins====		====Other plugins====

85.234.199.11: /* sensors_ plugin */

2006-11-29T21:54:25Z

sensors_ plugin

← Older revision		Revision as of 21:54, 29 November 2006
Line 58:		Line 58:
	<br>In /etc/munin/plugin-conf.d/munin-node:		<br>In /etc/munin/plugin-conf.d/munin-node:
	[sensors_]		[sensors_]
	env.sensors=sensors\|sed '1,+14d'		env.sensors sensors\|sed '1,+14d'


	====Other plugins====		====Other plugins====
	More info on plugins incl. how to write yours: http://munin.projects.linpro.no/wiki/HowToWritePlugins		More info on plugins incl. how to write yours: http://munin.projects.linpro.no/wiki/HowToWritePlugins

85.234.199.11: /* Other plugins */

2006-11-29T21:47:31Z

Other plugins

← Older revision		Revision as of 21:47, 29 November 2006
Line 61:		Line 61:

	====Other plugins====		====Other plugins====
	More info on plugins incl. how to write yours: http://munin.projects.linpro.no/wiki/~~plugins~~		More info on plugins incl. how to write yours: http://munin.projects.linpro.no/wiki/HowToWritePlugins

85.234.199.11: /* ip_ plugin */

2006-11-29T21:40:07Z

ip_ plugin

← Older revision		Revision as of 21:40, 29 November 2006
Line 36:		Line 36:
	</pre>		</pre>
	====ip_ plugin====		====ip_ plugin====
	Add to /etc/munin/plugin-conf.d/munin-node:		Add to /etc/munin/plugin-conf.d/munin-node (normally it is already done in the last versions):
	[ip_*]		[ip_*]
	user root		user root

85.234.199.11 at 21:35, 29 November 2006

2006-11-29T21:35:06Z

New page

Munin is a nice Monitoring framework

==Sites==
* http://munin.projects.linpro.no/
* http://www.debian-administration.org/articles/229
* http://www.debianhelp.co.uk/munin.htm

==Installation==
===On the collector===
apt-get install munin libdate-manip-perl
Configure /etc/munin/munin.conf to add nodes to collect
===On each node===
apt-get install munin-node libnet-snmp-perl libio-socket-ssl-perl libcrypt-des-perl libdigest-hmac-perl libio-socket-inet6-perl libwww-perl libnet-irc-perl smartmontools ethtool
Maybe you will have to relax the firewall when installing munin otherwise install will stall during plugin detection if loopback connections to port 3128 are dropped.
 Bind the monitor only to the wanted IP in /etc/munin/munin-node.conf and tell which server can get the info:
host <my_ip>
allow ^<regex IP of the collector>$ (see examples)
Select plugins from /usr/share/munin/plugins by adding a symlink in /etc/munin/plugins
 To know if a plugin could work, try it with argument "autoconf", if it says yes then it is usable otherwise look inside the plugin code (perl) for hints.
 Some plugins require some options to be configured, do that in /etc/munin/plugin-conf.d/munin-node

====apache_* plugin====
Activate apache2 extended status (cf http://www.debian-administration.org/articles/161):
 Install mod_info:
a2enmod info
Activate in /etc/apache2/apache2.conf the section:
<Location /server-status> etc
and add just above this section the following line:
ExtendedStatus On

/etc/init.d/apache2 force-reload
Add to /etc/munin/plugin-conf.d/munin-node:
<pre>
[apache_*]
env.lrrd_url "http://<my_ip>:%d/server-status?auto"
</pre>
====ip_ plugin====
Add to /etc/munin/plugin-conf.d/munin-node:
[ip_*]
user root
Add iptables dummy rules to collect stats on a particular IP:
iptables -A INPUT -d <ip>;iptables -A OUTPUT -s <ip>
Install the plugin for this ip:
ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_<ip>

====sensors_ plugin====
Usually you create symlinks calles sensors_fan, sensors_volt and sensors_temp.

I had many troubles after a kernel upgrade:
 Now the output of "sensors" features a "phantom" chip w83627hf-i2c-0-28 with no valid values, aside the 2 others, w83782d-i2c-0-29 and w83627hf-isa-0290.
 One more or less correct way would be to e.g. add an entry at the end of /etc/sensors.conf with
chip "w83627hf-i2c-*"
ignore in0
...
But sth is really wrong no way to get a section only considered by the -isa- and the other by -i2c-, whatever I tried both sections were submitted to the same filtering rules :-(

Last resort was to change the output of sensors when called by munin:
 In /etc/munin/plugin-conf.d/munin-node:
[sensors_]
env.sensors=sensors|sed '1,+14d'

====Other plugins====
More info on plugins incl. how to write yours: http://munin.projects.linpro.no/wiki/plugins