File: writing.rst

package info (click to toggle)
munin 2.0.76-5
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 7,064 kB
  • sloc: perl: 11,684; java: 1,924; sh: 1,632; makefile: 636; javascript: 365; python: 267
file content (120 lines) | stat: -rw-r--r-- 2,982 bytes parent folder | download | duplicates (11)
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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
.. _plugin-writing:

========================
 Writing a munin plugin
========================

A munin plugin is a small executable. Usually, it is written in some
interpreted language.

In its simplest form, when the plugin is executed with the argument
"config", it outputs metadata needed for generating the graph. If it
is called with no arguments, it outputs the data which is to be
collected, and graphed later.

Plugin output
=============

The minimum plugin output when called with "config" it must output the
graph title.

It should also output a label for at least one datasource.

::

  graph_title Some title for our plugin
  something.label Foobar per second

When the plugin is executed with no arguments, it should output a
value for the datasource labelled in "config". It must not output
values for which there are no matching labels in the configuration
output.

::

  something.value 42

For a complete description of the available fields, see the
:ref:`plugin-reference`.

Example shell plugin
====================

The base of a plugin is a small option parser, ensuring the plugin is
called with the correct argument, if any.

Two main functions are defined: One for printing the configuration to
the standard output, and one for printing the data. In addition, we
have defined a function to generate the data itself, just to keep the
plugin readable.

The "output_usage" function is there just to be polite, it serves no
other function. :)

.. code-block:: bash

  #!/bin/sh

  output_config() {
      echo "graph_title Example graph"
      echo "plugins.label Number of plugins"
  }

  output_values() {
      printf "plugins.value %d\n" $(number_of_plugins)
  }

  number_of_plugins() {
      find /etc/munin/plugins -type l | wc -l
  }

  output_usage() {
      printf >&2 "%s - munin plugin to graph an example value\n" ${0##*/}
      printf >&2 "Usage: %s [config]\n" ${0##*/}
  }

  case $# in
      0)
          output_values
          ;;
      1)
          case $1 in
              config)
                  output_config
                  ;;
              *)
                  output_usage
                  exit 1
                  ;;
          esac
          ;;
      *)
          output_usage
          exit 1
          ;;
  esac

Activating the plugin
=====================

Place the plugin in the /etc/munin/plugins/ directory, and make it
executable.

Then, restart the munin-node.

Debugging the plugin
====================

To see how the plugin works, as the munin node would run it, you can
use the command "munin-run".

If the plugin is called "example", you can run "munin-run example
config" to see the plugin configuration, and "munin-run example" to
see the data.

If you do not get the output you expect, check if your munin plugin
needs more privileges. Normally, it is run as the "munin" user, but
gathering some data may need more access.

If the munin plugin emits errors, they will be visible in
/var/log/munin/munin-node.log