Hello all...

just trying to fathom on what I should have support monitor for me on our w2k3 ded server here at SM.

Here's what I've picked....can anyone comment here on my comments re: did I do this right?

========================
--Services--------------
PING (This is the included default host check for monitored services that have failed.)

HTTP (this will check that a domain is up and being served, right?)

SMTP (this will check that my MailEnable SMTP is running?)

Memory (Windows-Only):
Warning: 80%
Critical: 90%

CPU (Windows-Only):
Warning: 80%
Critical: 90%

Service 1:
Name: MailEnable SMTP Connector (again, will check to see that this is running?)

Process 1:
Name: w3wp.exe (here, I want to know if my asp is running okay..is this the process to list here?)

===========================

Jim

That's look pretty good, but I'm not too sure about W3WP.exe as this represent application pools. There's a good chance - and I stand to be corrected - that these are created and destroyed as necessary by IIS.

If you use the http check and point it to an asp script, then you will not only be checking that the domain is up and running, but that ASP is working ok aswell - two birds with one stone

the reports are starting to come in for those listed items to be monitored...
and I guess I've made at least 2 mistakes...

Notification Type: PROBLEM

Date/Time: Tue Jan 18 15:10:15 CST 2005

Additional Info: MailEnable: Unknown

Additional Info: w3wp: Unknown


???

How do I then list my MailEnable SMTP connector? And how do I show my ASP to be running too?

???

Jim

Since you already have SMTP checked, having another option at the services is redundant. Mail Enable is one software, if SMTP fails, chances are everything else might have failed too.

Besides as for the process and services, I just ignore them. Some services might be only listening on specific ports and chances are the IP monitoring could not ping them at those points and consider as failed.

You're semi-correct. As long as IIS is running in application-isolation mode, then yes, each application pool will get its own w3wp.exe process. However, they are not created nor destroyed on a whim. Each w3wp.exe runs for the duration of the web server's uptime. Also, something to keep in mind, if the application pool is running as a web garden, then there will be multiple w3wp.exe proccesses for that application pool.

can someone then tell me, what do I list as a 'service' that can be monitored to show me when ASP pages are failing?

???

Jim

ASP isn't a service. It's an ISAPI extension of IIS's Web Publishing Service (W3SVC). The best you can do is monitor that service.