Repository
Munin (contrib)
Last change
2020-03-26
Graph Categories
Family
auto
Capabilities
Keywords
Language
Shell

load_extended

Sadly there is no documentation for this plugin

#!/bin/sh
#
# Plugin to monitor the load average on a system.
#
# Usage: Link or copy into /etc/munin/node.d/
#
# $Log$
# Revision 1.5  2004/05/20 19:02:37  jimmyo
# Set categories on a bunch of plugins
#
# Revision 1.4  2004/05/20 13:57:12  jimmyo
# Set categories to some of the plugins.
#
# Revision 1.3  2004/05/16 12:41:04  jimmyo
# Changed load plot from lastminute to last 5 minutes.
#
# Revision 1.2  2004/05/16 12:34:26  jimmyo
# Added "info"-fields to linux/cpu and linux/load plugins, to demonstrate how it works.
#
# Revision 1.1  2004/01/02 18:50:01  jimmyo
# Renamed occurrences of lrrd -> munin
#
# Revision 1.1.1.1  2004/01/02 15:18:07  jimmyo
# Import of LRRD CVS tree after renaming to Munin
#
# Revision 1.4  2003/11/15 11:10:28  jimmyo
# Various fixes
#
# Revision 1.3  2003/11/07 17:43:16  jimmyo
# Cleanups and log entries
#
#
#
# Magic markers (optional - only used by munin-config and some
# installation scripts):
#
#%# family=auto
#%# capabilities=autoconf



# If run with the "autoconf"-parameter, give our opinion on whether we
# should be run on this system or not. This is optional, and only used by
# munin-config. In the case of this plugin, we should most probably
# always be included.

if [ "$1" = "autoconf" ]; then
	echo yes
	exit 0
fi

# If run with the "config"-parameter, give out information on how the
# graphs should look.

if [ "$1" = "config" ]; then
	# The host name this plugin is for. (Can be overridden to have
	# one machine answer for several)

	# The title of the graph
	echo 'graph_title Load average'
	# Arguments to "rrdtool graph". In this case, tell it that the
	# lower limit of the graph is '0', and that 1k=1000 (not 1024)
	echo 'graph_args --base 1000 -l 0'
	# The Y-axis label
	echo 'graph_vlabel load'
	# We want Cur/Min/Avg/Max unscaled (i.e. 0.42 load instead of
	# 420 milliload)
	echo 'graph_scale no'
	# Graph category. Defaults to 'other'
	echo 'graph_category system'
	# The fields. "label" is used in the legend. "label" is the only
	# required subfield.
	echo 'load1.label load 1 min avg'
	echo 'load1.draw AREA'
	echo 'load5.label load 5 min avg'
	echo 'load5.draw AREA'
	echo 'load15.label load 15 min avg'
	echo 'load15.draw AREA'
	# These 6 are optional. They are only used if you have
	# configured your munin to tell a Nagios-server about any
	# problems
	echo 'load1.warning 10'
	echo 'load1.critical 120'
	echo 'load5.warning 10'
	echo 'load5.critical 120'
	echo 'load15.warning 10'
	echo 'load15.critical 120'
	# This one is purely to add an explanation to the web page. The first
	# one is for the graph itself, while the second one is for the field
	# "load".
	echo 'graph_info The load average of the machine describes how many processes are in the run-queue (scheduled to run "immediately").'
	echo 'load1.info Average load for 1 minute avg.'
	echo 'load5.info Average load for 5  minutes avg.'
	echo 'load15.info Average load for 15 minutes avg.'

	# Last, if run with the "config"-parameter, quit here (don't
	# display any data)
	exit 0
fi

# If not run with any parameters at all (or only unknown ones), do the
# real work - i.e. display the data. Almost always this will be
# "value" subfield for every data field.

echo -n "load1.value "
cut -f1 -d' ' < /proc/loadavg

echo -n "load5.value "
cut -f2 -d' ' < /proc/loadavg

echo -n "load15.value "
cut -f3 -d' ' < /proc/loadavg

# How could this plugin have been written in its simplest form?
# Something like this:
#
# ---------------------
# #!/bin/sh

#
# if [ "$1" = "config" ]; then

# 	echo "graph_title Load average"
#	echo 'graph_args --base 1000 -l 0'
#	echo 'graph_vlabel load'
# 	echo "load.label load"
# 	exit 0
# fi
# echo -n "load.value "
# cut -f1 -d' ' < /proc/loadavg
# ---------------------
#
# Except for the Nagios-warnings (which most people don't have any need
# for) and things used by installation scripts and munin-config (which
# you don't need if you don't plan on submitting your plugin to the
# package), and the scaling (no milliload numbers) the two versions will
# work identically.