OpMonAgent vs NSClient++ (was Nagios 3.0 SLA Reporting)

[Phil Costelloe]

> -----Original Message-----
> From: Hari Sekhon [mailto:hpsekhon at googlemail.com]
>
> Phil Costelloe wrote:
> >> I'm also looking forward to this. I'm a big fan of OpmonAgent as a
> >> replacement
> >> for Nsclient on Windows systems, it installs and runs without any
> fuss
> >> at
> >> all. I like things that Just Work. :)
> >>
> On this note, do you mean NSClient or the newer NSClient++?

I mean NSClient. I still have that happily running on some of the longer
lived servers and others have the TSMG rewrite that seemed to be
abandoned. But neither supports 64 bit windows. So I tried NSclient++, found
it to be a royal PITA to configure with unhelpful documentation [1], tried
OpmonAgent which just worked so I kept using it.

> I'm not sure if I considered OpMonAgent but I'd really like to know if
> it can beat NSClient++ which to my knowledge (or perhaps just
> perception) seems to be the more popular Windows agent.

I think NSClient++ is probably hugely more popular, which is why I mention
OpmonAgent at every opportunity so that people know it's out there. It seems
to be solidly written and actively supported, so if it does what you need
(a drop in replacement for NSClient with the option of running NRPE checks)
then it's a candidate worth considering.

[1] Apologies to the author of NSClient++, but that was my experience. I wasn't
in a persevering mood, I'm sure if I had persevered then there are great benefits.

--
Phil Costelloe
Foundation IT, Hermitage Berkshire RG18 9SE



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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