After a great deal of inspection, Nagios won’t work for what I need but I’m taking specific design ideas from it. Not that the design of Nagios is all that novel, but some parts of it are well thought out while other parts you just want to take the CLUE BAT (TM) to the developers. One of the big problems with Nagios, and similarily Big Brother, is that they don’t scale very well at all without significant customization.
I’m in the design phase of monitoring only about 100 Sybase ASE and Replication servers so while we aren’t talking about a lot of servers, the amount of information we are going to gather relating to performance, space utilization, diagnostics, and maintenance is considerable. Since this is a project for work, it is unlikely to see the light of the outside world 🙁 Maybe I’ll be able to convince the Powers that Be that releasing would be good PR. maybe..
Maybe on my spare time, I’ll create a lightweight Nagios plugin for the Sybase ASE and Sybase Replication server.
Oh, found out the ieee1394 driver in 2.6.17 doesn’t like a flakey external ieee1394 (firewire) harddrive too well. It causes my machine to restart. The enclosure also has a usb2 connection so I’ll try that this weekend. My other external harddrive (same model enclosure and hd model) works fine using ieee1394. I prefer ieee1394, because it is:
- faster than usb2
- less load on my box
- I use my firewire card for something other than the Dazzle Hollywood Bridge
One of my biggest gripes about Nagios is that it doesn’t really have a repository (back end database) where the data can be mined. I’m sure I can add a repository for all the data but I’m unsure whether it is worth the effort if I’m not able to release the code back to the Nagios people.