That's what I meant by "test as you operate", ping was just an example. If you have an FTP server, make sure those services are up and those ports are reachable. In the Windows world, I check for RPC being available and Server services being available (as well as DHCP client, DNS client, etc) before trying other test on said host. If the necessary services aren't reachable, no need to test for items that are DEPENDANT on that functionality (well, there are times you might want to parallel test as previously covered).
Dave -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Tuesday, June 01, 2010 1:52 PM To: NT System Admin Issues Subject: Re: Now: monitoring; (was RE: Veering even more OT ...) > I'm of the "test as you operate" ... I generally agree. However, I expect your operations do not consist of pinging the host. The users are actually connecting to HTTP or SMB or SMTP or whatever. Ping is a synthetic test, and very different from the real thing. I've had boxes which were responding to ping be otherwise crashed to the point of needing a hardware reset. So I would be less inclined to worry about that aspect for a ping test (provided you are testing name resolution as well). Certainly, pinging by IP address without also monitoring name resolution means you will miss name resolution problems. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
