Welcome to the SNMAgent project page

Every environment needs good system maintenance, and the key is to have excellent tools for system monitoring, notification and trend analysis. In the open source marked the two tools I've found closest to the "excellent" mark is Nagios and Munin. Together they give all you need for the linux/unix servers. However win32 support is not natively supported by any of them. SNMAgent is an attempt to fill this gap.

About this document

This document is intended for developers of SNMAgent and the brave few who want to run it in production. Others may find the information useful.


We cannot guaranty any kind of support for the SNMAgent. However you will most likely get a response from the munin mailing list or svenna@efnet. System spec and scope of the project may change drastically. Please be careful if you decide to put the SNMAgent in any kind of production environment.


Project status


The project will likely stay in a state of internal testing and proof-of-concept for a long while. However I've used the SNMAgent on production sites since June 2006 and several other people have deployments of SNMAgent on their server farm.

Nagios part of SNMAgent is working, there is not yet found any problems with the source modifications from the NSClient. Munin part of SNMAgent is able to talk to the Munin server and give system status. Some "Munin plugins" are supported by hard coded integration in the service. Some plugins can be configured to some extent; some are only in proof-of-concept stage and only working on developer machine or identical hardware.


SNMAgent now support two types of "plugins", Internal and PerfData. SNMAgent enumers *.ini files in the plugins\ directory. Ini files specify the plugin to be internal or of type PerfData.

Plugins are detected at runtime. There is no need for restarting the nt service when changing or adding configuration files.


Internal plugins is hard-coded in the application, and now consists of two plugins.




PerfData uses the .ini file to read mappings to the Windows Performance Monitor. Users can create custom .ini files, and i theory graph all data by using the Windows Performance Data Helper API (PDH). Some PDH plugins come pre-configured, with both .ini and matching etc\*.cfg files.









note: The installer should take care of the above for you.


Debug mode is of by default, as of version 0.300.

You can set debug level with the registy key HKEY_LOCAL_MACHINE\SOFTWARE\SNMAgent\Params\DebugLevel:REG_DWORD.

Debug Levels

Under installation and configuration you should set level 4, and change to 0 or 1 when you've beeen running stable for a while. You will need to restart the service for the changes to take effect.


v 0.300

v 0.220

v 0.210

v 0.200

v 0.100


Please read above information to understand what you are downloading, no dedicated support will be given. Project is barely ready for production.