1# Example configuration file for Munin, generated by 'make build'
2
3# The next three variables specifies where the location of the RRD
4# databases, the HTML output, logs and the lock/pid files.  They all
5# must be writable by the user running munin-cron.  They are all
6# defaulted to the values you see here.
7#
8#dbdir	@@DBDIR@@
9#htmldir @@HTMLDIR@@
10#logdir @@LOGDIR@@
11#rundir  @@STATEDIR@@
12
13# Where to look for the HTML templates
14#
15#tmpldir	@@CONFDIR@@/templates
16
17# Where to look for the static www files
18#
19#staticdir @@CONFDIR@@/static
20
21# temporary cgi files are here. note that it has to be writable by
22# the cgi user (usually nobody or httpd).
23#
24# cgitmpdir @@DBDIR@@/cgi-tmp
25
26# (Exactly one) directory to include all files from.
27includedir @@CONFDIR@@/munin-conf.d
28
29# You can choose the time reference for "DERIVE" like graphs, and show
30# "per minute", "per hour" values instead of the default "per second"
31#
32#graph_period second
33
34# Graphics files are generated either via cron or by a CGI process.
35# See http://munin-monitoring.org/wiki/CgiHowto2 for more
36# documentation.
37# Since 2.0, munin-graph has been rewritten to use the cgi code.
38# It is single threaded *by design* now.
39#
40#graph_strategy cron
41
42# munin-cgi-graph is invoked by the web server up to very many times at the
43# same time.  This is not optimal since it results in high CPU and memory
44# consumption to the degree that the system can thrash.  Again the default is
45# 6.  Most likely the optimal number for max_cgi_graph_jobs is the same as
46# max_graph_jobs.
47#
48#munin_cgi_graph_jobs 6
49
50# If the automatic CGI url is wrong for your system override it here:
51#
52#cgiurl_graph /munin-cgi/munin-cgi-graph
53
54# max_size_x and max_size_y are the max size of images in pixel.
55# Default is 4000. Do not make it too large otherwise RRD might use all
56# RAM to generate the images.
57#
58#max_size_x 4000
59#max_size_y 4000
60
61# HTML files are normally generated by munin-html, no matter if the
62# files are used or not. You can change this to on-demand generation
63# by following the instructions in http://munin-monitoring.org/wiki/CgiHowto2
64#
65# Notes:
66# - moving to CGI for HTML means you cannot have graph generated by cron.
67# - cgi html has some bugs, mostly you still have to launch munin-html by hand
68#
69#html_strategy cron
70
71# munin-update runs in parallel.
72#
73# The default max number of processes is 16, and is probably ok for you.
74#
75# If set too high, it might hit some process/ram/filedesc limits.
76# If set too low, munin-update might take more than 5 min.
77#
78# If you want munin-update to not be parallel set it to 0.
79#
80#max_processes 16
81
82# RRD updates are per default, performed directly on the rrd files.
83# To reduce IO and enable the use of the rrdcached, uncomment it and set it to
84# the location of the socket that rrdcached uses.
85#
86#rrdcached_socket /var/run/rrdcached.sock
87
88# Drop somejuser@fnord.comm and anotheruser@blibb.comm an email everytime
89# something changes (OK -> WARNING, CRITICAL -> OK, etc)
90#contact.someuser.command mail -s "Munin ${var:worst}: ${var:group}::${var:host}::${var:plugin}" somejuser@fnord.comm
91#contact.anotheruser.command mail -s "Munin ${var:worst}: ${var:group}::${var:host}::${var:plugin}" anotheruser@blibb.comm
92#
93# For those with Nagios, the following might come in handy. In addition,
94# the services must be defined in the Nagios server as well.
95#contact.nagios.command /usr/bin/send_nsca nagios.host.comm -c /etc/nsca.conf
96
97# The maximum time the munin-update may take to get updates from all nodes,
98# this might be interesting when using munin-async in case of large transactions and/or backlog.
99# When using the munin protocol to connect to a node, then this value shouldn't be set higher than 240.
100# In case it's higher, gaps might be seen in the graphs.
101timeout_fetch_all_nodes 240
102
103# The maximum amount of time in seconds we may work on 1 node.
104# The value will be limited with timeout_fetch_all_nodes.
105timeout_fetch_one_node 180
106
107# a simple host tree
108[@@HOSTNAME@@]
109    address 127.0.0.1
110    use_node_name yes
111
112#
113# A more complex example of a host tree
114#
115## First our "normal" host.
116# [fii.foo.com]
117#       address foo
118#
119## Then our other host...
120# [fay.foo.com]
121#       address fay
122#
123## IPv6 host. note that the ip adress has to be in brackets
124# [ip6.foo.com]
125#       address [2001::1234:1]
126#
127## Then we want totals...
128# [foo.com;Totals] #Force it into the "foo.com"-domain...
129#       update no   # Turn off data-fetching for this "host".
130#
131#   # The graph "load1". We want to see the loads of both machines...
132#   # "fii=fii.foo.com:load.load" means "label=machine:graph.field"
133#       load1.graph_title Loads side by side
134#       load1.graph_order fii=fii.foo.com:load.load fay=fay.foo.com:load.load
135#
136#   # The graph "load2". Now we want them stacked on top of each other.
137#       load2.graph_title Loads on top of each other
138#       load2.dummy_field.stack fii=fii.foo.com:load.load fay=fay.foo.com:load.load
139#       load2.dummy_field.draw AREA # We want area instead the default LINE2.
140#       load2.dummy_field.label dummy # This is needed. Silly, really.
141#
142#   # The graph "load3". Now we want them summarised into one field
143#       load3.graph_title Loads summarised
144#       load3.combined_loads.sum fii.foo.com:load.load fay.foo.com:load.load
145#       load3.combined_loads.label Combined loads # Must be set, as this is
146#                                                 # not a dummy field!
147#
148## ...and on a side note, I want them listen in another order (default is
149## alphabetically)
150#
151# # Since [foo.com] would be interpreted as a host in the domain "com", we
152# # specify that this is a domain by adding a semicolon.
153# [foo.com;]
154#       node_order Totals fii.foo.com fay.foo.com
155#
156