Difference between revisions of "MonAMI filesystem plugin"
Paul millar (Talk | contribs) |
(No difference)
|
Latest revision as of 11:54, 2 March 2007
Monitoring free space
You may have various partitions that need to be monitored. For example, the free space available for backups.
Sample configuration
The following configuration gives an illustration of how you can monitor free disk space with MonAMI. Two things to note:
- The limits must be defined as absolute values. One cannot express this a "10%" yet.
- The reported values are in terms of blocks. (The block-size is also reported by the filesystem plugin.) So, for the Nagios configuration, the required limits (in Bytes) should be divided by the block-size (in Bytes).
The following configuration gives a starting point for monitoring a DPM service. The file should be saved in the /etc/monami.d directory and MonAMI restarted.
Please note that this example defines a Ganglia target called "ganglia". This might conflict with another Ganglia definition (i.e. within some other /etc/monami.d file). If so, MonAMI will complain about the conflict, but carry on working (and probably work correctly). To remove the conflict, simply remove the "[ganglia]" below: the "[sample]" section will then send data to the exiting ganglia target.
[filesystem] name = backup-part1 location = /disk/disk1 [filesystem] name = backup-part2 location = /disk/disk2 [sample] interval = 1m read = backup-part1.blocks.available, backup-part2.blocks.available write = ganga, nagios [nagios] host = nagios.example.ac.uk password = ADeepAndDarkSecret # # WARN if 1GiB free or less (4096 byte block-size) # CRITICAL if 100MiB free or less (4096 byte block-size) CHECK_BACKUP1 = backup-part1.blocks.available, -, 262144, 25600 CHECK_BACKUP2 = backup-part2.blocks.available, -, 262144, 25600 [ganglia]