A couple days ago I had the crazy idea of creating a Nagios filesystem for FUSE.
As you might probably know, FUSE allows easy creation of filesystems, like a Wikipedia filesystem, an SFTP filesystem, or real filesystems like ntfs-3g! So, as I’ve always wanted to have some sort of programmatic access to Nagios from my beloved shell, I decided to implement a Nagios FUSE, which I’ve called Nagus (the star trek reference is quite obvious, I guess).
I got it to Proof-of-Concept quality this morning (Monday March 15 2010), and I’ll be releasing it soon. In a snapshot, you use it like this:
MOUNT IT: ./nagus.py /mnt/nagus
It has this structure:
Inside ‘hosts’ appears a list of directories which match your Nagios list of hosts. The same happens in services, but that’s the final stage so I might change that, I don’t know yet (feedback is welcome).
In by-status you get 3 subfolders: ok, warning and critical, which if you use Nagios should be fairly obvious what means. Below that you’ll find proper categorization of ok/warning/critical hosts and services.
So, well, this is a new idea, so I will definitely need lots of feedback. I’ll twitter this and try to get many RTs.