Robot
/
contrib-munin
mirror of https://github.com/munin-monitoring/contrib.git
2
0
Fork 0
Code Issues Releases Wiki Activity

Fixed NOTES comment to better explain the fetch munin/cron modes

This commit is contained in:
Neraud 2018-08-04 17:35:59 +02:00
parent 81b129dd81
commit 1027f5e57a
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
plugins/git/git_commit_behind
View File

@ -11,8 +11,11 @@ how many commits behind their remote they are
This plugin is similar to how apt_all works for apt packages.
To be able to check how behind a git repository is, we need to run git fetch.
To avoid fetching all repos every 5 minutes and slowing down the munin-node,
the fetch operation is triggered via a cron job.
To avoid fetching all repos every 5 minutes (for each munin period) and thus
slowing down the data collection, the git fetch operation is only randomly
triggered (based on env.update.probability).
In case of very time-consuming update operations, you can run them in a
separate cron job.
=head1 REQUIREMENTS