Re: [Nagios-users] Monitoring Exchange 2007?

[Anthony M. <amo...@gm...>]

Equaly NC_NEt, NSClient++ and NRPE all can also give access to Performance
counters, Processes and services.  SOme (like NC_NEt) also give access to
WMI and event logs  but none give direct interaction to Exchange itself.

Doesn't echange have its own internal performance monitoring and event
handlers on thresholds. If so, and if they allow scripts to be triggered or
if they send email reprots then you may be able to configure Exchange to
submit directly to Nagios via NSCA? (Maybe)

TOny (Author of NC_Net)

On Fri, May 30, 2008 at 3:38 PM, Aaron M. Segura <aar...@ca...>
wrote:

> Have you looked at using the opmon agent?
>
>
> http://www.opservices.com.br/index.php?option=com_content&task=view&id=54&Itemid=54
>
> It states you can get access to "every available performance counter",
> which should give you some insight into what exchange is doing.  YMMV,
> I've never used it, but the new version was announced on list yesterday,
> so it's fresh in my memory.
>
> On Fri, 2008-05-30 at 11:34 -0700, Mirza Dedic wrote:
> > I have been trying to get a working plug-in that does this as well;
> deeper than what I have setup right now.
> >
> > The way I am monitoring Exchange 2007 is with service & process checks,
> but this wouldn't give you a full monitoring covering as processes &
> services can be UP but no mail coming through/working.
> >
> > Let me know what you find out as I'd like to improve on this as well.
> >
> > Thanks.
> >
> > -----Original Message-----
> > From: nag...@li... [mailto:
> nag...@li...] On Behalf Of Andrew Cruse
> > Sent: May/30/2008 11:37 AM
> > To: 'nagios Users Mailinglist'
> > Subject: [Nagios-users] Monitoring Exchange 2007?
> >
> > I've recently been tasked with monitoring an Exchange 2007 single-copy
> > cluster so I've been perusing what's available at nagiosexchange.org as
> well
> > as poking around what Google turns up.  Most of what I've found is pretty
> > old (Exchange 5.5) with a few newer bits (Exchange 2003) but nothing
> > specifically on Exchange 2007.  I'm relatively confident the stuff for
> 2003
> > can probably be made to work but before I go reinventing the wheel I
> figured
> > I'd check in and see if anyone else was monitoring Exchange 2007 that
> might
> > have some suggestion, tips, tricks, or otherwise to share.
> >
> > Thanks!
> >
> > Andrew
> >
> >
> > -------------------------------------------------------------------------
> > 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
> > Nag...@li...
> > 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
> >
> >
> >
> > -------------------------------------------------------------------------
> > 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
> > Nag...@li...
> > 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
>
> -------------------------------------------------------------------------
> 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
> Nag...@li...
> 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
>