If all Observium could do was check to make sure it could SSH a box (either with a password or public key) and check a HTTP/HTTPS to make sure a specific HTTP code was returned, and the SSL cert was valid, we could completely dump Nagios.

*fingers crossed* but mark us down for another customer who would love the functionality.


Spencer Ryan | Senior Systems Administrator | sryan@arbor.net
Arbor Networks
+1.734.794.5033 (d) | +1.734.846.2053 (m)

On Wed, Dec 2, 2015 at 11:29 PM, Adam Armstrong <adama@memetic.org> wrote:
We're thinking about bringing this functionality back.

As with everything, the trick is working out how to structure it so that it doesn't become a liability in future!

adam.

On 03/12/2015 04:27:33, Rhian Resnick <rresnick@fau.edu> wrote:

Good Evening,


We at  FAU are very new to Observium but our Network Team, Security Team, and HPC Team are amazed and love the product. 


How would you recommend checking the following items and sending alerts when they fail:

 Checking one or more TCP/UDP port is listening?

 Checking if the TCP/UDP port is responding correctly? 

 

If these are directions you do not plan on investigating we completely understand. It would however be wonderful to drop our dependence on Nagios.


Thanks!



Rhian Resnick

Assistant Director Middleware and HPC

Office of Information Technology


Florida Atlantic University

777 Glades Road, CM22, Rm 218

Boca Raton, FL 33431

Phone 561.297.2647

Fax 561.297.0222

 image


    

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium