Users experience:

• I use moodss at work to monitor 22 remote computing sites. Each site is connected to the main site, where the management Linux server sits, by a WAN line, and each site contains a UNIX AIX server. Network traffic (in and out), CPU usage (system, user and input/output and usage for 5 specific families of applications), memory usage (total, swap input/output, and usage for each applications family) are periodically sampled (every minute or 5 minutes for the applications). All those data samples, collected 24 hours a day, 7 days a week, are stored in a MySQL database. All the data is processed and stored by the moomps daemon, using SNMP (snmp module) and AIX specific modules. So far, tens of millions of samples have been stored, with the history database table being split in several tables (1 per month). Finally, data is made available to the users via dynamic web pages (in PHP) with daily graphs. The Linux server is a bi-processor (2 x 1.25 GHz Pentium III, 1 GBytes of memory, with a fast SCSI disk and a big IDE disk for daily backups).
  
  
• I work for a group in the Z-series mainframe development organization and we use moodss to monitor our Linux benchmarking activities from a central point of control. In particular, we often run Linux in our Virtual Machine (VM) operating system which allows many copies of an OS (literally 100's) to be active in a single box. Moodss allows us to monitor the balance of workloads in a distributed deployment of a Web server farm across these instances, as an example. While we have yet to exploit some of the new data archiving capabilities, we look forward to doing so and are very pleased with some special extensions which were added to monitor the many (again, 100's) of disk devices which can be attached to the Z-series mainframe !!
  
  
• I use it simply as example code, to help me learn how to better use Tcl and Tk -- especially the Tk "table" widget. Because the code is open source, moodss can be helpful even without using it as an application.