Spotlight alerts you to problems with your system by issuing an alarm.
|Blocked processes are processes that are waiting on information to become available in memory, or that are waiting for a shared resource, or for the completion of disk I/O or network I/O. A high level of blocked processes may indicate an under-configured machine.|
|The Input Error flow represents the number of erroneous network packets coming into the machine per second. The Input Error Packets Flow alarm may warrant investigation as even a low error rate can indicate network problems.|
|The Output Error flow represents the number of erroneous network packets sent by the machine per second. The Output Error Packets Flow alarm may warrant investigation as even a low error rate can indicate network problems.|
|A large number of page-ins may be a symptom of a large number of recent page-outs (see Page Out alarm below). To find out what process is reading these pages in, check the resident size of the processes you are running, and see which ones are increasing in size. Alternatively, a large number of page-ins may occur when a large process has just stopped, and the kernel decides to fill that space with memory pages owned by other processes. Check if an important process has ended unexpectedly.|
|If an active process asks the kernel for more memory than there is immediately available, the kernel will write old memory pages out to swap space. This is known as paging. To stop paging, make sure that there is enough RAM available to support the size of the processes you want to run.|
|The Most Active Disk gauge shows the disk with the highest read/write rates. The Percentage Busy alarm is triggered when the read/write rate of the most active disk exceeds a specified threshold. The type of alarm that is activated is determined by the percentage of read/write activity experienced by the disk.|
|The Disk I/O wait time alarm is triggered when one of the disks' I/O wait time exceeds a specified threshold.|
If the total amount of swap space allocated to a Unix host becomes full, the machine may halt all processes, or critical actions may be prevented from occurring. The Swap Space alarm may indicate a runaway process or an under-configured machine.
|The Swap In flow represents the number of processes swapped from disk per second. The Swap In Flow alarm may indicate a machine that is under-configured for its workload.|
|The Swap Out flow represents the number of processes swapped to disk per second. The Swap Out Flow alarm may indicate a machine that is under-configured for its workload.|
Spotlight is re-establishing its connection to the Unix system.
|The Least Space / Disk Space container displays the percentage of used disk space for a specified filesystem. The Used Percentage alarm indicates that the specified filesystem is full or filling up. If the filesystem fills up completely, no more data can be written to it.|
|The Zombie button in the CPU panel shows the number of terminated child processes that have not been acknowledged by their parent process. The Zombie Processes alarm may indicate the presence of an inferior program, or an entry in /etc/inittab (or equivalent) that prevents init from completing its startup sequence.|
Once a problem is isolated you can display a drilldown page with charts and tables that provide a detailed breakdown of the underlying statistics.
|Drilldown||Click to open||Keyboard Shortcut||Drilldown Pages||Description|
|Processes and Services||CTRL+P||
The Processes and Services drilldown lists all the processes running on the Unix machine (including "zombie" processes), and all the services found in the /etc/services file (running or not).
Use the Activity Summary drilldown to show details of the activity on the Unix system.
|Filesystems||CTRL+S||Filesystems And Disk Information||
Use the Filesystems drilldown to show disk usage for each filesystem on the Unix system, and the proportion of disk space used by each filesystem.
The Alarm Log drilldown displays information on the alarms associated with the Windows system, including the name of the component that issued the alarm, the date and time the alarm was logged, and the severity of the alarm.
Note: The Alarm Log drilldown is common to all Spotlight applications. The alarms are specific to the current Spotlight connection. Spotlight on Unix Alarms
Use Spotlight on Windows to monitor Windows operating systems, detect and resolve problems.
|Connect to Windows Systems||Create / Modify / Delete connections to Windows systems.|
|Spotlight on Windows Home Page||The Spotlight home page shows the flow of information and commands between various sub-components and the size and status of internal resources such as processes, disk files and memory structures.|
|Spotlight on Windows Alarms||
Spotlight alerts you to problems with your system by issuing an alarm. You can configure Spotlight in the level of severity that constitutes an alarm, to disable an alarm, and the actions Spotlight takes on raising the alarm.
|Spotlight on Windows Drilldowns||When you have isolated a problem, you can display a drilldown page, whose charts and tables provide a detailed breakdown of the underlying statistics.|
|Troubleshooting Spotlight on Windows||
This section identifies general problems that you may encounter when using Spotlight on Windows, and details how to address those problems.
Select the Windows system.
|You will need||Description|
Ensure your login to the Windows machine has Administrator access privileges.
To add a new connection to the Windows machine you are currently using, ensure you are logged in to the machine with Administrator access privileges. If necessary, logout and login again.
Spotlight on Windows retrieves its data from Windows performance counters and the windows registry of the monitored system. An administrator login to the Windows machine has such access.
To add a new connection to a Windows machine other than the one you are currently using, ensure the machine is accessible to the Spotlight client. Spotlight uses NetBIOS traffic to retrieve perfmon and registry information, so any firewalls between the Spotlight on Windows client and the machine being monitored must allow this traffic to pass through. Troubleshooting Spotlight on Windows
Click File | Connect
Select Spotlight on Windows on the Connections menu.
Double-click Add new connection.
Fill in the connection Properties | Details page. Windows Connection Details