I’ve released Glovebox Version 0.2.1 on Sourceforge. It has a few bug fixes as well as the correct database schema included. Other changes include:
- Modified JavaScript so it would load & function in IE
- Changed “class” to “clas” within JS, Perl, and the database. IE didn’t like using the word “class” as a variable name, changed else where for consistency.
- Stopped opening of “right-click” menu when pressed on an interface folder
- Fixed DB Schema to include basic information for default OIDs and Interfaces.
- Modified Apache configuration so SSIs would work correctly in Apache 2, changed the SSIs to only execute on .shtml files
- Renamed index.html to index.shtml
There is a database change, so you must run the sql file located in the upgrade folder!
You can download it here.
On the request of my Manager, I have released Glovebox under a GPL license on Sourceforge. I have yet to update the site with instructions but hope to soon. I’ve included a tar ball of the current version as well as imported the full source code in Sourceforge’s SVN repo.
The SourceForge project page is located here.
The project home page is located here.
Over the years I’ve had to write plenty of Hobbit / Xymon scripts to monitor various different things within my employers systems. Since most all of our applications are custom there are not always built in tests that will work for us. For example, we use Xen for our development virtual machines and being able to track what was going on with those virtual machines is important and being able to identify a VM within Xymon at a moments glance is important to us, so we created a test that does just that. We have created in house scripts for MySQL Status, MySQL Running Queries, our in house distributed services, Lighttpd (as discussed earlier on this blog), Apache, Memcached, etc. This doesnt include the hundreds of different snmp tests we’ve added to Devmon for monitoring our network equiptment.
Read more…
When I started in the “Technology” department at my current employer, I found myself apart of a team that was tasked with taking care of hundreds of IBM blade servers, and tens of other IBM system x servers. For the most part we could keep up with our servers by where they were in our monitoring software, but if we needed to know exactly where they were in either a blade center, by remote console name, or what Domain-0 they lived on for our Xen based virtual machines – we had to relate back to a usually out of date spreadsheet that showed where to go.
Read more…
