Latest News
Download Installation
Change Log

Project Page
How to Contribute
Coding Standards
The Code
JUnit Results
Checkstyle Results
To Do
Config Generator





  • Why should I use Spumoni when MRTG lets you harvest values from programs directly?

    Spumoni is not necessary IF you're only using MRTG as your front-end on the same box that you're monitoring. However, this isn't as desirable when monitoring many machines, particularly using enterprise-level network monitoring suites like OpenNMS, Tivoli, OpenView, Unicenter, etc. In these cases it is better to expose monitored statistics using the open and more networkable standard of SNMP. It really comes down to your scope and needs. In essence, if you have an application that you want to monitor via SNMP but it doesn't support that directly, then Spumoni is a perfect fit.

  • Why are the configuration files written in XML?
  • XML may not be terribly human-readable at first, but after you get used to it, it is very easy to work with. The main advantage of XML over INI/conf files is that they're self-validating when a document type descriptor (DTD) file is used, and that can really reduce problems introduced by messed up config files. There are also some really nice graphical XML document editors out there - take a browse through Freshmeat for some good tools.

  • How does Spumoni relate to JMX, JIRO and FMA?
  • Right now, Spumoni doesn't directly relate to any of those, but turning Spumoni into a JMX component is being considered after Spumoni reaches critical mass - if you can offer analysis, please contact Scott.

  • Why the name Spumoni?
  • Spumoni is a loose anagram for SNMP, and is also the name of a fruity flavored ice cream.