A pilot can view all important statistics in his cockpit, so why not a network administrator? Hostmeter is a NINO utility to display the router or host status in one dashboard. All important statistics are shown as meters and bars in a cockpit dashboard style. This contains CPU, memory, processes, storage and system information.
The Hostmeter main sreen is divided into three areas. On the left the CPU, load and memory statistics are displayed. Also the status of monitored processes (hosts only) can be displayed. In the middle the system info, such as Operating System, BIOS, hardware info and other information is shown. The info button will show the device info screen to set hostname, contact en location. The processes button will show the top processes list. The network button will show the network status. The storage statistics are displayed in the right area of the hostmeter dashboard. This is an example of a windows server running on Dell hardware.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The processes are displayed sorted by CPU usage. For each process the CPU tics and memory usage is shown.
It is possible to view detail process info by clicking on the process name.
It is also possible to navigate in time by clicking First, Prev, Next or Last.
Exit will go back to the Hostmater main screen. To view a graph of process resources, click on the button.
First | Prev | Next | Last | Tue Apr 27 08:24:21 2004 | Exit |
CentiSecs/S | Memory | | PID | Name | Long name | Type | Status | ||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
| ![]() | 1924 | sqlservr.exe | Application | running | |||||
|
| ![]() | 928 | svchost.exe | C:\WINDOWS\System32\ -k netsvcs | Application | running | ||||
|
| ![]() | 500 | lsass.exe | C:\WINDOWS\system32\ | Application | running | ||||
|
| ![]() | 4 | System | Operating System | running | |||||
|
| ![]() | 1396 | dfssvc.exe | C:\WINDOWS\system32\ | Application | running | ||||
|
| ![]() | 856 | wmiprvse.exe | Application | running | |||||
|
| ![]() | 488 | services.exe | C:\WINDOWS\system32\ | Application | running | ||||
|
| ![]() | 2908 | snmp.exe | C:\WINDOWS\System32\ | Application | running | ||||
|
| ![]() | 444 | winlogon.exe | Application | running | |||||
|
| ![]() | 708 | svchost.exe | C:\WINDOWS\System32\ -k termsvcs | Application | running |
This screen will show a graph of process CPU and memory usage. This makes it very easy to troubleshoot applications, find memory leaks and more. This is an example of a squid proxy process running on a Unix server.
|
This screen will show detailed process information. Set the severity in process monitor alarm to monitor the status of the process. The status is displayed in the Hostmeter main screen. It is also possible to send alarms into the eventlog if a process is not running anymore. The status events will be displayed in the eventlog. This can be done by checking the status checkbox in the monitoring configuration.
The device discovery process will use a default process list to detect what processes should be monitored. This can be changed by checking the Update discovery process list checkbox. This way it is possible to create a customized process list that can be used for a discovery of new servers.
Process | Severity | |
---|---|---|
xfs |
| |
lpd |
| |
ypbind |
| |
ypserv |
| |
automount |
| |
syslogd |
| |
portmap |
| |
smbd |
| |
mysqld |
| |
ftpd |
| |
httpd |
| |
apache |
| |
tnslsnr |
| |
TNSListener |
| |
sqlservr |
| |
sqlexec |
| |
db2serv |
| |
mad |
| |
msdtc |
| |
emsmta |
| |
store |
| |
mqsvc |
| |
lsass |
| |
services |
| |
wins |
| |
dns |
| |
named |
| |
sshd |
| |
inetd |
| |
xinetd |
| |
nfsd |
| |
nmbd |
| |
cron |
| |
rpc.statd |
|
Hostmeter will show the network status if the network is monitored. This is an example of a Sun Solaris web server with multiple interfaces.
Network | Network traffic | Errors | ||||
---|---|---|---|---|---|---|
1-lo0 |
|
| ||||
2-eri0 |
|
| ||||
3-qfe0 |
|
| ||||
4-qfe0:1 |
|
| ||||
5-qfe0:2 |
|
| ||||
6-qfe0:3 |
|
| ||||
7-qfe4 |
|
| ||||
8-qfe4:1 |
|
| ||||
9-qfe4:2 |
|
| ||||
10-qfe4:3 |
|
|
Hostmeter depends on monitoring presets that monitor CPU, memory, storage and processes. Using the default discovery process NINO will detect the device monitoring capabilities and for servers it will detect the most important processes to monitor. If the auto-discovery is disabled, the device monitoring should be configured. Preset groups or individual monitoring presets must be activated for devices to view status meters. A special HostProcs preset is responsible for monitoring host processes. This preset is member of the Windows and Linux preset group. In the preset group or HostProcs preset the status checkbox must be checked to get status alarms in the eventlog