Disk Writes Alarm
The Disk Writes alarm is activated when the level of traffic being transmitted to this disk exceeds a threshold. Sustained high disk activity can cause an overall degradation of system responsiveness.
When this alarm is current you should look at:
- The Page File Transfers chart on the Paging Activity page of the Memory drilldown. High paging out suggests that the high number of disk writes could be due to system paging. Adding more memory may alleviate the problem.
- The NBT page of the Network drilldown and see if any systems are transferring a large amount of data.
- The Disk Queue chart on the Physical Disks Activity tab of the Disks drilldown. If the disk queue length is high on a single physical disk you can look at:
- Spreading frequently accessed data over multiple physical disks.
- Spreading page files over multiple physical disks.
- Implementing a faster disk subsystem.
- Implementing RAID striping technology.
If the high number of writes is causing an overall degradation of the system, consider upgrading the disk subsystem (controller and/or disks).
Event Log Alarm
This alarm becomes active when an Event Log entry is found which matches an active Event Log rule.
You can enable event logs and set event log rules. Windows Event Log Metrics
Event Log Panel
Windows Event Log Metrics
Logical Disk Statistics Alarm
This alarm is activated when disk-based performance counters are not enabled or not updated.
Not all disk-based performance counters are enabled by default on Windows 2000 systems. If this is the case, Spotlight on Windows cannot retrieve the data in these counters, and the disk activity flows (to the left of the Disks panel) are disabled for this machine.
To rectify this situation:
Go to the machine's command prompt and type:
- For this change to take effect, you then need to reboot the system under diagnosis.
Dynamic disks and Windows 2000
Windows 2000 systems now have additional support for dynamic disks, but the disk performance counters under Windows 2000 have not been updated to report this information correctly. Because of this, Spotlight on Windows cannot retrieve the data in these counters, and the disk activity flows (to the left of the Disks panel) are disabled for this machine.
To rectify this situation:
- Remove all dynamic disks from the machine, or
- Upgrade the machine to the Windows XP operating system.
Low Memory Alarm
This Low Memory alarm is activated when the available memory drops below a threshold. This can result in:
- Applications being unable to secure additional memory.
- New programs being unable to open successfully.
- General performance degradation due to excessive paging.
When this alarm is current you should:
- Look at the Processes page in the Processes drilldown. Check the Mem Usage (MB) column for processes using excessive amounts of memory. You can:
- Close those applications using excessive memory.
- Change the maximum memory usage setting for those applications using excessive memory. Refer to the relevant documentation to find out if this setting is supported by the application.
- Purchase more physical memory for your system.
- Determine if any programs have a memory leak. To do this:
- Restart your machine to ensure fresh memory usage by all applications.
- Use the Microsoft Performance Monitor tool and set the update interval to 10 minutes.
- Add the Working Set Peak counter for all applications from the Process object.
- Leave the application running on the system overnight.
- If there is a memory leak that can be viewed in a day, it will show up with the Working Set Peak graph for one of the applications rising smoothly. If the results are inconclusive after a day, some system applications that have a memory leak may exhibit the behavior over a week or more. Adjust the update interval to accommodate the extended period (update once per hour or more).