File: README.rst

package info (click to toggle)
munin 2.999.14-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 10,036 kB
  • sloc: perl: 31,052; sh: 12,473; java: 1,924; python: 852; makefile: 336; ruby: 232; awk: 169; xml: 45; sql: 11
file content (75 lines) | stat: -rw-r--r-- 2,818 bytes parent folder | download
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
This is Munin
=============

Munin the monitoring tool surveys all your computers and remembers what it saw.
It presents all the information in graphs through a web interface.
Its emphasis is on plug and play capabilities.
After completing a installation a high number of monitoring plugins will be
playing with no more effort.

Additional plugins can be easily developed and contributed.
See the `Plugin Gallery <http://gallery.munin-monitoring.org/>`_ for a wide
range of more than a thousand community supported plugins.

Munin is distributed under the GNU GPL version 2.  Munin is copyrighted
2002-2018 by its various authors as identified in the source files.


Resources
=========

* Website: http://munin-monitoring.org/
* Documentation: http://guide.munin-monitoring.org/
* `IRC channel <irc://irc.oftc.net/#munin>`_: ``#munin`` on OFTC
* Mailing List: https://lists.sourceforge.net/lists/listinfo/munin-users
* Plugin Gallery: http://gallery.munin-monitoring.org/
* Live Demo (development): http://demo.munin-monitoring.org/


Note to contributors
--------------------

By sending us patches, you automatically license the code under the same terms
as Munin.

We also might edit your commits metadata (the comment part) for clarifications,
but we'll leave the diff part intact (except for whitespace edits). So in case
there's a problem with the commit diff, we either commit another patch
thereafter or plainly ask you to rework it. We might eventually squash some of
your commits into one.

Please always rebase your pull requests on a released version tag, one of the
stable branches, or the default branch, ``master``.

If you request a pull against ``master``, your pull will be automatically closed
upon merge. If you request against one of the stable release branches, your pull will be
automatically closed upon the next release.

Information on developing Munin with GitHub, such as how branches are used
and the version numbering scheme, can be found in `Munin's GitHub Wiki`__.

.. __ : https://github.com/munin-monitoring/munin/wiki/_pages


Building status
---------------

stable-2.0 : |build-stable2.0|

master : |build-master|  |coverage-master|

docs : |docs-latest|

.. |build-stable2.0| image:: https://travis-ci.org/munin-monitoring/munin.svg?branch=stable-2.0
   :target: https://travis-ci.org/munin-monitoring/munin

.. |build-master| image:: https://travis-ci.org/munin-monitoring/munin.svg?branch=master
   :target: https://travis-ci.org/munin-monitoring/munin

.. |coverage-master| image:: https://coveralls.io/repos/github/munin-monitoring/munin/badge.svg?branch=master
   :target: https://coveralls.io/github/munin-monitoring/munin?branch=master


.. |docs-latest| image:: https://readthedocs.org/projects/munin/badge/?version=latest
   :target: http://guide.munin-monitoring.org/