Yow! After months of mentioning Rebol, sending Rebol news around the office, etc., I'm happy to say that I have been given the go-ahead to build a Rebol-based server monitoring/management tool! The 1-line script I showed off last week tries to connect to a webserver, and if the server is down, an email is sent to the appropriate party. Jaws dropped. ;-) Easy to astonish them M$-drones ;-) Now we are actually speccing a more full-featured set of monitoring services to run 24/7, checking multiple webservers, ftpservers, fileservers, mailservers, etc., Responses could include emails, email-->pagers, modifying server-pool lists, etc. For example, we have a load-balancer connected to three webservers. If one of the webservers stops running (but the machine is still up, determined using ping? hey? how to do this in Rebol?), 1-n persons need to know this is the case. The load-balancer also needs to know that it should remove the offending webserver from it's list of servers. This is going to be trickier, but it's basically a telnet session and a bunch of load-balancer-specific commands. In either case, we would also like to gather some performance info from the machines which would be formatted into an XML report for web-viewing or database-import. Anyone able to shere info on this type of thing please respond! This is an excellent opportunity to create a highly visible, best-of-breed (we got da $) Rebol solution! TIA! -- Pete Wason|"LWATPLOTG"|[EMAIL PROTECTED]|[EMAIL PROTECTED]|CUCUG|TA|PHX
