Lab situation (blatant cry for help :) )

[Subhendu Ghosh]

On Tue, 15 Apr 2003, Greg Vickers wrote:

> Hi all,
> 
> We use Nagios to monitor our servers etc here.
> 
> I have been tasked with looking at how Nagios
> could be applied to monitor our Lab
> computers. We have ~900 PCs across four
> campuses. We would like to show our students
> where available computers are.
> 
> I'm thinking of compiling nsca so that the
> client will run on win32 (labs run XP) and
> submitting checks on startup (OK state, PC
> available), logon (CRITICAL state, PC not
> available) and reboot (UNKNOWN state, PC
> rebooting). So we would have our raw data in
> the nagios log files.
> 
> Then i'd write something to pull the data
> about Lab PCs in an OK/(CRITICAL|WARNING)
> state and show students something like this:
> 
> A block Lab:
> 10 PCs available
> 35 PCs unavailable
> 
> Can anyone comment on the feasibility/reality
> of this, since IANACP (I Am Not A C
> Programmer, I love learning curves), or
> has/would anyone approached this situation in
> a different manner?
> 
> Or am I barking mad?
> 
> Thanks,
> Greg
> 
> p.s. potential proposal in the project is to
> integrate with Sylabus+ so that we can show
> the students which labs are booked and
> when.... (cue maniac laughter)
> 


Depending out on your setup - other options might be to 

a) look a a centralized EventLog/syslog for events
b) if logon/logoff scripts are used, add a sub to log the event
c) not use C - nsca packet structure can be found in common/common.h



-- 

-sg



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null