Hi there,
I am looking at implementing HostMonitor on our production system which is spread out over trans-tasman, i.e. Australia, NZ and Singapore.
My question is what sort network traffic does HM create if a test is set up to monitor a server or service by pinging it once every hour?
We currently have a 5 MB link set up.
A prompt reply would be highly appreciated!!
Query: Network traffic created by HostMonitor pings
1 server once an hour??
I think its very easy to calculate. E.g. if you setup Ping test to send 2 64bytes packets then traffic will be: 2 packets x packet size x 2 (because some packets will travel in both directions) = 2*64*2=256 bytes per hour.
If you plan to monitor many servers, its still very easy to calculate: packet size * number of packets * number of servers * 2.
(actually its a little more complicated because you should add IP packet header, add DNS request if you setup test using hostname then substract some data because HostMonitor may not send 2nd packet when server respond on 1st packet... many things depends on various settings)
If you worry about your network, lets calculate: 5*1024*1024*3600/256 = 73,728,000. Your network allows you to monitor 73 million servers (1 ping per hour). Truth to say HostMonitor will not allow you to setup so many test items.
On the other hand, is it good idea to ping server just once per hour?? I think its better to ping server every 5, 10 minutes. If you do not have thousands servers to monitor, you may ping them every minute.
If you are asking about "Service" test method, its more difficult to calculate. I think its around 600 bytes for each test probe.
Regards
Alex
I think its very easy to calculate. E.g. if you setup Ping test to send 2 64bytes packets then traffic will be: 2 packets x packet size x 2 (because some packets will travel in both directions) = 2*64*2=256 bytes per hour.
If you plan to monitor many servers, its still very easy to calculate: packet size * number of packets * number of servers * 2.
(actually its a little more complicated because you should add IP packet header, add DNS request if you setup test using hostname then substract some data because HostMonitor may not send 2nd packet when server respond on 1st packet... many things depends on various settings)
If you worry about your network, lets calculate: 5*1024*1024*3600/256 = 73,728,000. Your network allows you to monitor 73 million servers (1 ping per hour). Truth to say HostMonitor will not allow you to setup so many test items.
On the other hand, is it good idea to ping server just once per hour?? I think its better to ping server every 5, 10 minutes. If you do not have thousands servers to monitor, you may ping them every minute.
If you are asking about "Service" test method, its more difficult to calculate. I think its around 600 bytes for each test probe.
Regards
Alex
Not sure what to say, different people have different needs.What is your recommended architecture for deploying it within an enterprise?
What kind of recomendation?
E.g. we recommend to install HostMonitor on Windows Server 2003 SP2.
We recommend to use RMA (Remote Monitoring Agent) installed on remote system when you need to use "Compare files" test method to check some large files.
We recommend to use RMA when you need to check some remote networks/domains. Its much better then open ports on your firewall.
RMA: http://www.ks-soft.net/hostmon.eng/rma-win/index.htm
If you need to monitor some very important servers, we recommend to use WatchDog or 2nd instance of HostMonitor to check primary monitoring server. http://www.ks-soft.net/hostmon.eng/watchdog/index.htm
We do not recommend to use network/mapped drives for HostMonitor logs. Use local drive or ODBC logging.
If you need to monitor many similar systems (monitor similar services or many systems), we recommend to use Patterns. However you may use Replicator as well.
There are many other recomendations listed in the manual...
Regards
Alex