[Xymon] Why Xymon?

[Galen Johnson]

I'd ask "why not Xymon"?  It obviously has a proven track record in your company.  It can be a significant task to replace an existing monitoring solution with some thing new and integrate it into your processes.  If they want to use offshore resources, why not let them help manage the existing system?  I've used many different monitoring solutions and I always come back to Xymon.  Once I show it's simplicity and ease of extensibility, others want to use it.

How easy will it be to add new monitors to the in-house application?  Add new servers to monitor?  What support level can you expect?   Many of these you already have stated.  There used to be a PPT out there about using Hobbit/Xymon.  Not sure what happened to that or how current it is.

=G=

________________________________
From: Xymon <xymon-bounces at xymon.com> on behalf of Gore, David W (David) <david.gore at verizon.com>
Sent: Wednesday, June 4, 2014 8:20 AM
To: xymon at xymon.com
Subject: [Xymon] Why Xymon?

Hi All,

We are being asked "Why Xymon?".  We have some answers but I was hoping someone else may have been more eloquent and articulate than myself in defending the use of Xymon.  Perhaps you could share your wisdom?

We started using Xymon when we lost our first level 24x7 monitoring group and have not looked back since.   Now we are being asked to use an in-house application and offshore assets.

Some of the Xymon features we like are:

*big picture of all our apps via the nonongreen page, application, OS, network and databases monitored
*graphing and historical trending
*ease of use
*light weight/low resource
*multiple scripting languages support (any)
*redundant (warm standby)
*cost (free) thanks Henrik and everyone else
*support via the mailing list,

We have been using Xymon from the beginning back in 2005.  Before using Xymon/Hobbit we used Big Brother.

Thanks in advance for any advice.

~David W Gore

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20140604/f45ecd3d/attachment.html>