| View previous topic :: View next topic |
| Author |
Message |
m0n
Joined: 20 Oct 2004
Posts: 28
|
 Posted: Wed Oct 20, 2004 3:17 am Post subject: Many desktops |
 |
|
Hello,
is it possible to use AHM to check if 15000 desktops are up & running ?
If so, how ?
Thx,
m0n |
|
| Back to top |
|
 |
KS-Soft
Joined: 03 Apr 2002
Posts: 12795
Location: USA
|
| Posted: Wed Oct 20, 2004 10:59 am Post subject: |
|
|
What about simple Ping test method?
Regards
Alex |
|
| Back to top |
|
|
m0n
Joined: 20 Oct 2004
Posts: 28
|
| Posted: Thu Oct 21, 2004 2:11 am Post subject: |
|
|
| but ping test is not enough really to see if they are up & working for the users |
|
| Back to top |
|
|
hamoja
Joined: 18 Jun 2003
Posts: 34
|
| Posted: Thu Oct 21, 2004 5:24 am Post subject: |
|
|
| You really need to be more specific as to what want monitored or define "working". Ping test is the only test that checks up/down status for PC comminucation to the network. |
|
| Back to top |
|
|
FLynch
Joined: 18 Jun 2002
Posts: 75
Location: London UK
|
| Posted: Fri Oct 22, 2004 9:15 pm Post subject: |
|
|
How about basic monitors on;
Ping test
CPU
Memory
Disk space
.....for each workstation? However 15,000 * 4 monitors would be a hell of a lot for any system to poll, collate and report on. |
|
| Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002
Posts: 12795
Location: USA
|
| Posted: Sat Oct 23, 2004 2:26 pm Post subject: |
|
|
Yeah. If m0n wants to check 4 parameters of each system every 5 min, 15000*4/60/5 = 200 checks per second. HostMonitor will not start so many threads. But it will be possible to check each system every 10 min... if network is good.
Anyway, I agree with hamoja - m0n should be more specific. We don't know what exactly he wants to monitor. May be all systems located in the same network, or may be he wants to monitor hundreds of networks all over the world...
Regards
Alex |
|
| Back to top |
|
|
Marcus
Joined: 18 Nov 2002
Posts: 367
|
| Posted: Mon Oct 25, 2004 1:27 am Post subject: |
|
|
My checks would be:
Ping and "lanmanworkstation" service with the ping test as the master. 
The biggest performance problems are dependent on your reporting. We see that when a lot of tests change status, sometimes reporting will boost cpu usage to 100% |
|
| Back to top |
|
|
m0n
Joined: 20 Oct 2004
Posts: 28
|
| Posted: Mon Oct 25, 2004 7:29 am Post subject: |
|
|
Oki thx, ill just monitor the servers instead of all desktops
m0n |
|
| Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002
Posts: 12795
Location: USA
|
| Posted: Mon Oct 25, 2004 10:33 am Post subject: |
|
|
| Quote: | | The biggest performance problems are dependent on your reporting. We see that when a lot of tests change status, sometimes reporting will boost cpu usage to 100% |
You are generating reports using "Generate reports" action? Probably you can setup HostMonitor to create reports by timer (e.g. every 3 min)?
Regards
Alex |
|
| Back to top |
|
|
Marcus
Joined: 18 Nov 2002
Posts: 367
|
| Posted: Tue Oct 26, 2004 1:30 am Post subject: |
|
|
| Quote: | | Probably you can setup HostMonitor to create reports by timer |
Which we do, but also for every status change. Which will generate a lot of reports with (for example) network failures |
|
| Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002
Posts: 12795
Location: USA
|
| Posted: Tue Oct 26, 2004 1:42 pm Post subject: |
|
|
H'm... don't see good solution that can resolve this problem.
On the one hand we can implement some reports pool and create report after 1-3 sec delay - create single report for all requests that come within this time interval.
On the other hand it can effect action profiles behavior... E.g. when action profile should create report and then send report by mail
Regards
Alex |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in
