Creating custom service checks

[Kevin Keane]

What do you want to monitor about these services?

I am monitoring Exchange in two separate ways. First, I am using the 
check_services_stopped plugin from the NagiosPluginsNT collection. It 
monitors whatever services are configured with Automatic startup, so it 
normally would include the Exchange services.

The second thing I am doing is use the check_nt_win.exe plugin to get 
the values of Exchange-related performance counters (this requires 
NSClient++ to be installed and running). check_nt_win.exe is my own 
plugin, but it really is simply a Windows port of the check_nt plugin 
that comes with NSClient++.

Kevin Mitnikc wrote:
> I am looking to monitor the Microsoft Exchange Server services such as: 
>  
> Microsoft Exchange Management
> "C:\Program Files\Exchsrvr\bin\exmgmt.exe"
>  
> These services will be monitored on the exchsrv01 server.  How do I go 
> about creating this service to be monitored?  All the services I'm 
> currently monitoring have already been predefined for me.
>  
>  
> Thanks,
>  
> Kevin M.
>
> 2009/6/29 Allan Clark <allanc at chickenandporn.com 
> <mailto:allanc at chickenandporn.com>>
>
>     Hi Kevin;
>
>     On Mon, Jun 29, 2009 at 23:14, Kevin Mitnikc <teckadmin at gmail.com
>     <mailto:teckadmin at gmail.com>> wrote:
>
>         I am looking for some assistance in setting up custom service
>         monitors.  I am looking to monitor the Microsoft Exchange
>         services, along with a couple other services.  How do I go
>         about setting this up in Nagios. 
>          
>         I have browsed over some direction, but I seem to only be
>         finding sections of setting this up.
>          
>         Can somebody please give me some direction and instruction on
>         creating these custom service monitors.
>
>
>     Can you go into more detail?  Nagios is configured by editing the
>     config files, and running a "nagios -v" to check them; if you have
>     examples of what you're trying, including the "couple other
>     services", we might be able to offer concrete suggestions.
>      ...even if it means you give us a rundown of a part of your
>     network, with IP address replaced to 192.168.x.y IPs and host
>     FQDNs replaced to names such as exch01.example.com
>     <http://exch01.example.com/>.
>
>     It might help to get such an initial example setup to get you going.
>
>     Allan
>     -- 
>     allanc at chickenandporn.com <mailto:allanc at chickenandporn.com>  "金
>     鱼" http://linkedin.com/in/goldfish
>     please, no proprietary attachments (http://tinyurl.com/cbgq)
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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


-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof.


------------------------------------------------------------------------------
_______________________________________________
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