wiki:PluginGallery

Plugin Gallery

In the gallery you can browse description and graph images for our Munin Plugins. It is not ready and complete yet. Example graph images are still missing and many plugins have empty documentation pages (due to missing perldoc sections in the plugin script).

Here some examples pages with graph images:

The HTML-Presentation is auto-generated in a daily cronjob at our project server. It views the plugins documentation page, that is viewed by munindoc otherwise. Example graphs for the plugins have to be placed in our github repositories.

Help from contributors is welcome :-) Have a look at our instructions in the next section on this page.

The gallery has two showrooms. One called Core Collection for the plugins that we deliver with the distribution of Munin-Node and one called 3rd-Party Collection for the plugins from the wild, that were uploaded to our Contrib-Repository. Especially the later needs a lot of documentation work and we are happy if you add info in perldoc format and representative example graph images to the contrib repo. The more descriptive content is there, the more helpful the Plugin Gallery will be ~

Categories

The plugins category is the main navigation criterion of the galley. So the first step of the build procedure is the search for the keyword graph_category within the plugin scripts and parse the string, that follows in the same line. It makes things easier if you don't use spaces within in the cagetories name. Please use character underscore instead if a separator is needed.

The following wiki pages contain info and recommendations concerning categories:

Rules for plugin contributors

To make sure that we can auto-generate the portrait pages for each plugin please pay attention to the following instructions.

  1. Add documentation about your plugin in perldoc style (information about perldoc: http://juerd.nl/site.plp/perlpodtut) to show with munindoc and in the Plugin Gallery on the web. (See Best Current Practices).
    1. Add these sections at the start or end of your plugins script file.
  2. Upload the plugins files to Github contrib directory.
    1. Put the plugins script in a subdirectory that matches its nature / purpose. When you wrote a plugin to monitor a special product or for a special operating system, place it in a directory with that name, e.g. apache (product) or debian (operating system).
    2. There are also directories named with a generic term like "mail", but as we use this term as well-known category name, you can set a 2nd level heading in the gallery with the name of the directory to where you put your plugin.
  3. Choose and upload a Munin generated graph of your plugin for demonstration purpose.
    1. Take one in original size of the Munin website plugin page. Please no the zoomed image! It should be a file in PNG-Format.
    2. Place it in the subdirectory example-graphs of your plugins directory, so one level deeper in the file hierarchy.
    3. Its name should begin with the name of your plugins script file followed by -day.png for a daily graph, -week.png for a weekly graph, -month.png for a monthly graph, -year.png for a yearly graph,e.g. cpu-day.png or smart_-month.png.
  4. Upload more image files to the subdirectory example-graphs in PNG-Format if you want to illustrate the documentation section Interpretation
    1. The filename of such an additional image should match the following format <plugins_name>-n.png with n standing for a digit between 1 and 9, e.g. cpu-1.png

Current state of the project

We have scripts to auto-generate the HTML presentation called "Munin Plugin Gallery" per daily cronjob.

ToDo?

Whenever the scripts fails to find this relationship between plugins and categories, we put these into category 'other' (Core Collection) (3rd-Party Collection). It would be good to improve the plugins data concerning the category or to improve the parse method to decrease the number of these unrelated plugins.

Last modified at 2017-08-14T13:12:11+02:00 Last modified on 2017-08-14T13:12:11+02:00