
	Click a topic for more information:

		Thank you

		What you need to know about AppManager

		About the AppManager WMI Agent

		Installing the AppManager WMI Agent

		Starting and stopping Knowledge Script jobs

		Browsing AppManager jobs, events, and data

		A closer look at the WMI Knowledge Scripts

		Learning more about the AppManager Suite

		Disclaimer

A closer look at the WMI Knowledge Scripts

Each Knowledge Script represents one or more business or system management rules. Knowledge Scripts can monitor the health and performance of a managed computer by comparing real-time conditions (such as memory usage) against thresholds specified by the Knowledge Scipt. Knowledge Scripts also watch for specified events (such as a service going down) and can take corrective action (such as restarting the stopped service). Knowledge Scripts can also collect data for graphs and reports.

The Knowledge Scripts for the AppManager WMI Agent are configured with preset parameters, as described in the following tables. The table also lists the preset schedule for each Knowledge Script. In the full NetIQ AppManager Suite, you can set the parameters and schedule yourself, and perform many other forms of customization.

The AppManager WMI Agent includes Knowledge Scripts in two categories:

Knowledge Scripts that monitor basic Windows NT/2000 resources
Knowledge Scripts that monitor WMI resources

Knowledge Scripts that monitor basic Windows NT/2000 resources

Knowledge Script	What it does
NT_CpuLoaded	Monitors the overall CPU load for a single-processor system (CPU processor instance 0) against the following thresholds: CPU usage: 90% CPU queue length (the maximum number of processes waiting in the queue to run): 2 If both thresholds are exceeded, the Knowledge Script generates an event. Schedule: Every 30 minutes.

NT_MemUtil	Monitors the amount of memory usage against these thresholds: Physical memory used: 80% Virtual memory used: 80% Paging file used: 90% If any threshold is exceeded, the Knowledge Script generates an event. Schedule: Every 30 minutes.

NT_ServerBusy	Monitors Windows NT server activity against these thresholds: Number of active sessions: 50 Number of files open: 200 If either threshold is exceeded, the Knowledge Script generates an event. Schedule: Every 10 minutes.

NT_ServiceDown	Checks the status of all services that are configured to start automatically. If any service is not running, the Knowledge Script generates an event and restarts the service. The Graphing Data class returns a value of 100 when a service is running and a value of 0 when a service is down. Schedule: Every 1 hour.

NT_TopCpuProcs	Monitors the percentage of CPU usage for all processes and identifies the top five processes consuming the most CPU. When the percentage of the total CPU usage exceeds 90%, the Knowledge Script generates an event. Schedule: Every 30 minutes.

NT_TopMemoryProcs	Monitors the memory usage for all processes and identifies the top five processes consuming the most memory. When the total memory usage for all processes exceeds 10 MB, the Knowledge Script generates an event. Schedule: Every 30 minutes.

Knowledge Scripts that monitor WMI resources

Knowledge Script	What it does
WMI_EventConsumer	Queries the WMI event log and forwards any events that it finds to the AppManager event table. The events generated by this Knowledge Script depend on the type of WMI services installed on the managed computer. Schedule: Every 5 minutes.

WMI_LogSizes	Monitors the size of these WMI log files: winmgmt.log, mofcomp.log, wbemcore.log, wbemprox.log, and wmiprov.log. This Knowledge Script sets a maximum size of 10 KB for any individual log file and a maximum size of 30 KB for the sum of all log files. If either threshold is exceeded, the Knowledge Script generates an event. Schedule: Every 1 hour.

WMI_ResourceHigh	Monitors the CPU and memory consumption for WMI processes. If CPU usage exceeds 30%, or if memory usage exceeds 1 MB, the Knowledge Script generates an event. Schedule: Every 10 minutes.

WMI_ServiceDown	Monitors the Windows Management (WinMgmt) service. If the service is not running, the Knowledge Script generates an event and restarts the service. The Graphing Data class returns a value of 100 when a service is running and a value of 0 when a service is down. Schedule: Every 5 minutes.