File: munin.README.Debian

package info (click to toggle)
munin 2.0.63-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 7,008 kB
  • sloc: perl: 11,644; java: 1,924; sh: 1,619; makefile: 636; javascript: 365; python: 267
file content (104 lines) | stat: -rw-r--r-- 4,222 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
Debian-specific information regarding Munin
===========================================

  Getting started
  ---------------

    Using Munin requires to run a Munin master, which needs the munin
    package installed and an arbitrary number of Munin nodes, with the
    munin-node package installed. The master can and should also be a node.

    On the master system point your browser to http://localhost/munin - to
    customize edit /etc/munin/apache.conf if you are using apache2.

    On the nodes, /etc/munin/munin-node.conf needs to be edited to allow
    access from the master node. Restart munin-node after any configuration
    change.

    Plugins reside in /usr/share/munin/plugins/, their usage is activated
    by linking them to /etc/munin/plugins/ (restart munin-node afterwards).
    Plugin configuration is best done in /etc/munin/plugin-conf.d/

    Further reading: http://guide.munin-monitoring.org/


  Allow non-local access to web interface
  ---------------------------------------

    By default access to the munin web interface is restricted to
    local requests.
    If you need to access the web interface remotely, you should replace
    all occurrences of "Require local" with "Require all granted" in
    /etc/apache2/conf-enabled/munin.conf and restart apache2.


  Performance considerations: generate visualization on-demand or via cron
  ------------------------------------------------------------------------

    By default munin generates its HTML output and its graphs periodically
    (via cron). This is suitable for small installations.

    If performance is an issue (e.g. if one master is collecting data from
    dozens or hundreds of nodes), the visualization can also be configured
    to be generated on demand.
    The following steps are required for this change:
      * set "html_strategy" and/or "graph_strategy" to "cgi"
        (see /etc/munin/munin.conf and /etc/munin/munin-conf.d/)
      * adjust the apache configuration for munin
        (see the end of /etc/apache2/conf-enabled/munin.conf)
      * enable one of the CGI handlers for apache:
          * cgi: "a2enmod cgid"
          * fcgid: "apt install libapache2-mod-fcgid && a2enmod fcgid"
      * restart apache2 and visit http://localhost/munin/


  Using a different webserver (e.g. nxinx)
  ----------------------------------------

    Apache2 is preconfigured for the munin master web interface when
    installing the munin package.  Alternatively you may choose to
    serve the munin web interface with a different webserver.
    In this case you may want to configure socket activation for HTML
    and graph generation:

        cp /usr/share/doc/munin/examples/systemd-fastcgi/munin-* /etc/systemd/system/
        systemctl daemon-reload
        systemctl enable munin-graph.socket
        systemctl enable munin-html.socket
        systemctl start munin-graph.socket
        systemctl start munin-html.socket

    In case of nginx you can start with the included example
    configuration file:

        cp /usr/share/doc/munin/examples/nginx/munin.nginx.conf /etc/nginx/sites-available/munin.conf
        ln -s ../sites-available/munin.conf /etc/nginx/sites-enabled/
        service nginx restart

    Probably you should tweak the "listen" and "server_name" settings
    in this configuration file according to your needs.


  Find the upstream source
  ------------------------

    This Debian package uses the upstream tarball located here:
      http://downloads.munin-monitoring.org/

    It also uses quilt to apply some debian specific patches located in
    ./debian/patches/


  Suggestions? Impressions? Questions? Fanmail? Love letters? Murder threats?
  ---------------------------------------------------------------------------

    We've got a mailing list.  You'll find subscription information at
    <http://lists.sourceforge.net/lists/listinfo/munin-users>.  All feedback
    are welcome.

    If you feel like sending us things that can't be represented in binary (for
    example beautiful people fluent in assembly, bacillus anthracis, cash,
    explosives, and so on), take contact off-list, and we'll find a way of
    arranging the logistics.

 Enjoy!  :-)