Hi, can you please tell me how much servers HostMonitor can test simultaneously if I want for example made a ping test, 2 services tests and a CPU test on each computer every 10 minutes.
In fact, for example if 50 computers crached at the same time would HM be able to log all the events and send an email for each test which failed.
HostMonitor Performance
Everything depends on settings, your system, and your network. If you have system based on 486 processor (it was before Pentuim I
), 8Mb RAM, Windows 95, and network based on dial-up connection, I will not recommend monitor a lot of servers.
But if you have normal up-to-date system, you can monitor hundreds servers. Some customers use HostMonitor to check more than 4,000 parameters. Anyway 50*4=200 test items (which you want to setup) will not be a problem even on Pentium.
Regards
Alex

But if you have normal up-to-date system, you can monitor hundreds servers. Some customers use HostMonitor to check more than 4,000 parameters. Anyway 50*4=200 test items (which you want to setup) will not be a problem even on Pentium.
Regards
Alex
Currently we have 1481 test every 10 minutes = 8886 tests an hour at peaks (not all schedules are 24x7); 64 tests a seconds max; logging all information to sql (135119 entries yesterday=an average of 5629 an hour) AND disk.
We are running UNC, PING, HTTP, URL, IMAP, SERVICE and MSSQL tests.
No problem for HM, it's waiting for more....
<font size=-1>[ This Message was edited by: Marcus on 2003-01-17 09:25 ]</font>
We are running UNC, PING, HTTP, URL, IMAP, SERVICE and MSSQL tests.
No problem for HM, it's waiting for more....
<font size=-1>[ This Message was edited by: Marcus on 2003-01-17 09:25 ]</font>
Marcus, does the hostmonitor service crash on you at all? We still crash about 2-3 times a day at least. We have 2 hostmonitor servers, one with 2800 tests, and one with 550 tests. Each one is set to do no more than 15 a second, and range from every 3-10 minutes a check, 24x7 for everything. I've exhausted my troubleshooting (I've turned off SQL logging, ODBC tests, and UNC tests) and it still crashes. Multiple machines crash with all different hardware. I've disabled all 3rd party services (management software/antivirus etc) yet still it will crash.
Oh btw, if you fill up the DBF file (2GB max) hostmonitor will crash right away, and will crash almost instantly after re-launching. I wish it could get over the 2gb limitation or split off the log weekly. I've since turned it off.
Oh btw, if you fill up the DBF file (2GB max) hostmonitor will crash right away, and will crash almost instantly after re-launching. I wish it could get over the 2gb limitation or split off the log weekly. I've since turned it off.
We have the following software running on the server:
W2K SP3, including IIS and TS
Hardware Agents (compaq)
Software Agents (HP Openview / ITO)
Performance Logging software (Measureware)
SQL 2000 SP2 (This is where we log, so we don't face a 2Gb limit).
BackupExec 8.6
About half the test have a 24x7 schedule.
Just checked and HM is still running (as a service). So it survived the weekend. On weekdays I don't know, since every configuration change I do is done by stopping the service and starting HM as an application (but this is not on a daily basis and I have not seen HM crash).
I suggest you set up a performance monitor, to see what causes the crash.....
If it is realy a crash, you should have drwatson logs. Perhaps Alex can see in those logs what happened.......
W2K SP3, including IIS and TS
Hardware Agents (compaq)
Software Agents (HP Openview / ITO)
Performance Logging software (Measureware)
SQL 2000 SP2 (This is where we log, so we don't face a 2Gb limit).
BackupExec 8.6
About half the test have a 24x7 schedule.
Just checked and HM is still running (as a service). So it survived the weekend. On weekdays I don't know, since every configuration change I do is done by stopping the service and starting HM as an application (but this is not on a daily basis and I have not seen HM crash).
I suggest you set up a performance monitor, to see what causes the crash.....
If it is realy a crash, you should have drwatson logs. Perhaps Alex can see in those logs what happened.......