[dc-ops] DC-OPS Monitoring Software...
Michael K. Smith - Adhost
mksmith at adhost.com
Thu Sep 8 13:50:42 EDT 2011
> -----Original Message-----
> From: dc-ops-bounces at puck.nether.net [mailto:dc-ops-
> bounces at puck.nether.net] On Behalf Of Network IP Dog
> Sent: Wednesday, September 07, 2011 4:44 PM
> To: DC-OPS Mailing Lists
> Subject: [dc-ops] DC-OPS Monitoring Software...
>
> First... I appreciate that there is a DC-OPS List now...
>
> Second... It's long overdue too...
>
> Third... Let the conversations/dialogs begin... ;^)
>
>
>
> Hi!
>
>
> We have used "The Dude"
>
> http://www.mikrotik.com/thedude.php
>
> and also "Servers Alive"
>
> http://www.woodstone.nu/salive/
>
>
> with APC monitoring attached on both via... SNMP
>
> They both have their pro's & con's...
>
>
> What do you use?
>
> What are the pro's & con's too?
>
> Was it based on limited budget or budget was not a factor?
>
>
> CHEERS!!!
>
We use an Alerton system that ties in monitoring on all of our environmental systems and uses BACNet for communications. This allows us to see all of our units on one common platform, regardless of whether they are SNMP-based, Contact-closure based, or some proprietary vendor goo. Since we have all three it's helpful to have a common system that can see them all.
Our decision was based on uptime and response rather than cost. It's not the most expensive system, but it's certainly more expensive than Nagios with add-ons for tying into various platforms. But, we also have a contract to manage the back end system, so I don't have to futz around with Nagios all the time either, so there's a cost savings there.
We use other systems for monitoring servers and network kit. Primary among them are Zabbix and OSSIM for servers, and MRTG with custom hooks for network, all laid on top of 15 years of custom coding.
Mike
More information about the dc-ops
mailing list