1 # Example configuration file for Munin, generated by 'make build'
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.
9 # htmldir /var/cache/munin/www
10 # logdir /var/log/munin
11 # rundir /var/run/munin
13 # Where to look for the HTML templates
14 # tmpldir /etc/munin/templates
16 # (Exactly one) directory to include all files from.
18 includedir /etc/munin/munin-conf.d
20 # Make graphs show values per minute instead of per second
23 # Graphics files are normaly generated by munin-graph, no matter if
24 # the graphs are used or not. You can change this to
25 # on-demand-graphing by following the instructions in
26 # http://munin.projects.linpro.no/wiki/CgiHowto
30 # munin-cgi-graph is invoked by the web server up to very many times at the
31 # same time. This is not optimal since it results in high CPU and memory
32 # consumption to the degree that the system can thrash. Again the default is
33 # 6. Most likely the optimal number for max_cgi_graph_jobs is the same as
36 #munin_cgi_graph_jobs 6
38 # If the automatic CGI url is wrong for your system override it here:
40 #cgiurl_graph /cgi-bin/munin-cgi-graph
42 # munin-graph runs in parallel, the number of concurrent processes is
43 # 6. If you want munin-graph to not be parallel set to 0. If set too
44 # high it will slow down munin-graph. Some experiments are needed to
45 # determine how many are optimal on your system. On a multi-core
46 # system with good SCSI disks the number can probably be quite high.
50 # Drop somejuser@fnord.comm and anotheruser@blibb.comm an email everytime
51 # something changes (OK -> WARNING, CRITICAL -> OK, etc)
52 #contact.someuser.command mail -s "Munin notification" somejuser@fnord.comm
53 #contact.anotheruser.command mail -s "Munin notification" anotheruser@blibb.comm
55 # For those with Nagios, the following might come in handy. In addition,
56 # the services must be defined in the Nagios server as well.
57 #contact.nagios.command /usr/bin/send_nsca nagios.host.comm -c /etc/nsca.conf
60 [localhost.localdomain]
65 # A more complex example of a host tree
67 ## First our "normal" host.
71 ## Then our other host...
75 ## Then we want totals...
76 # [foo.com;Totals] #Force it into the "foo.com"-domain...
77 # update no # Turn off data-fetching for this "host".
79 # # The graph "load1". We want to see the loads of both machines...
80 # # "fii=fii.foo.com:load.load" means "label=machine:graph.field"
81 # load1.graph_title Loads side by side
82 # load1.graph_order fii=fii.foo.com:load.load fay=fay.foo.com:load.load
84 # # The graph "load2". Now we want them stacked on top of each other.
85 # load2.graph_title Loads on top of each other
86 # load2.dummy_field.stack fii=fii.foo.com:load.load fay=fay.foo.com:load.load
87 # load2.dummy_field.draw AREA # We want area instead the default LINE2.
88 # load2.dummy_field.label dummy # This is needed. Silly, really.
90 # # The graph "load3". Now we want them summarised into one field
91 # load3.graph_title Loads summarised
92 # load3.combined_loads.sum fii.foo.com:load.load fay.foo.com:load.load
93 # load3.combined_loads.label Combined loads # Must be set, as this is
94 # # not a dummy field!
96 ## ...and on a side note, I want them listen in another order (default is
99 # # Since [foo.com] would be interpreted as a host in the domain "com", we
100 # # specify that this is a domain by adding a semicolon.
102 # node_order Totals fii.foo.com fay.foo.com