Fork of munin-monitoring/munin for bleeding edge features. I'm using this as a sandbox, so expect many rebases (ie: fork from it at your own risk)
Perl Shell CSS JavaScript Java Python Other
Pull request Compare This branch is 39 commits behind munin-monitoring:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.github/ISSUE_TEMPLATE
contrib
dev_scripts
dists
doc
etc
lib
plugins
script
t
web
xt
.dockerignore
.flake8
.gitattributes
.gitignore
.perlcriticrc
.travis.yml
Announce-2.0
Build.PL
CONTRIBUTING.md
COPYING
ChangeLog
Checklist
Dockerfile
HACKING.pod
INSTALL.rst
MANIFEST.SKIP
Makefile
Makefile.config
Makefile.config-maint
Makefile.javaplugin
README.HP-UX
README.OSX
README.build-refactoring
README.rst
authors
cpanfile
getversion
logo-horizontal-neg.svg
logo-horizontal.svg
logo.eps
logo.png
logo.svg
perltidyrc

README.rst

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 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

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.

Building status

stable-2.0 : build-stable2.0

master : build-master coverage-master

docs : docs-latest