I create a Host probe for the server, then create probes for each service on the server. Then I link the service probes to the server with manual links, such that the services depend on the server. Now I can see if a service goes down even if the server is up. And if the server goes down, the service probes get shadowed so I don't see alerts from them. Works out OK for me. Yes, it increases the number of devices you are monitoring, but I have an unlimited license and don't really care :)
-- Doug Weathers Information Technology Network Administrator Cascade Healthcare Community 2500 NE Neff Road Bend, OR 97701 http://www.scmc.org mailto:[EMAIL PROTECTED] Desk: 541-383-6846 Cell: 541-480-0919 >>> [EMAIL PROTECTED] 6/6/2005 2:24:41 PM >>> I second this one. I've created "Map Status" probes for maps with multiple probes for single servers as a way to implement this, but Don's suggestion would be more elegant. Thanks, Mark P. - Mark C. Persiko, Network Engineer - IT Division, Boulder Valley Public Schools ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Levinson, Don A. Sent: Thursday, June 02, 2005 12:33 PM To: InterMapper Discussion Subject: [IM-Talk] Wish list A composite probe that combines Host Resources with Windows Services so I don't need multiple instances to monitor my servers. Perhaps even some kind of generic monitor framework that lets me combine multiple probes on one host/endpoint (i.e. web + ftp + host resources). ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
