On Friday 12 August 2005 08:42 pm, Ivo Perich wrote: > Well, the fact is that our monitoring server has no problem doing the > pings, because we are doing about 15 ping every 5 minutes to each machine. > The server is ok, the network is ok. The point is that we think the > monitoring system is ok and our counterpart says that the pings must be > done from the remote hosts, where there are no machines to dedicate to do > this job. We want to do the monitoring the way we are doing it now, because > we only need to monitor the response time and the percent of succeed pings, > and this can be done from our server without need to acquire about 130 PCs > that would be doing pings to our server. The other solution is so much > complicated, and we think that is no reason to do the monitoring that way. > If there's a reason, we would like to know it. That's all. What do you > think?
It really depends on what you're looking to discover with the pings. If the point is to make sure that the network path is still accessable and the host is mostly up, then your solution would be the preferred one. If the point is to make sure that the network is up and the remote host is still running cron() and such then running from the remote system might be required. I'd try and cover both bases by writing a small server or cgi process that would give me process information, and 'ping' by calling it on the remote machine to get that information. Combining that with ping data would tell you more than either single solution. But really, you need to know what problem you're solving before you can choose any solution.
____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
