4.2.2 Performance Analysis

Reports	Analysis target and condition settings	Display item	Description
VMware (Cluster)	H Specify System Group and Host	CPU Usage Memory Usage	The CPU usage and memory usage for the cluster is displayed. This graph makes it easy to see which cluster is using the CPU or memory. Point It is possible to track CPU and memory usage by cluster. It is also possible to track CPU, memory, and disk by displaying "VMware (Virtual host)".
VMware (Resource pool)	H Specify System Group and Host	CPU Usage Memory Usage	The CPU usage and memory usage for the resource pool is displayed. This graph makes it easy to see which resource pool is using the CPU or memory. Point It is possible to track CPU and memory usage by resource pool. It is also possible to track CPU, memory, and disk by displaying "VMware (Virtual host)". When virtual resources are running low and physical resources are available, the manager can see which resource pools are using the resources in this report and reallocate resources if necessary.
VMware (Host)	G Specify System Group	CPU Usage Rate Free Memory Amount Disk I/O Count	Check the usage status of the physical CPU, memory, and disks.
VMware (Virtual machine)	H Specify System Group and Host	CPU Usage Rate	CPU usages by guest operating systems are stacked for display. This graph makes it easy to see which guests are using the CPU. CPU usage rate is calculated with each physical CPU having a value of 100%. This means that the cumulative CPU usage rate of the CPUs of guest operating systems will be shown exceeding 100%.
		Memory Usage	Memory usages by guest operating systems are stacked for display. This graph makes it easy to see which guest is using the memory.
		Disk I/O Count	Disk I/O by guest operating systems are stacked for display. This graph makes it easy to see which guest is using the disk.
		Point Monitoring guest operating systems with Agents enables the system manager to see what is happening with virtual CPUs, memories, and disks. It is also possible to track physical CPU, memory, and disk by displaying "VMware (Virtual host)". When virtual resources are running low and physical resources are available, the manager can see in this report which guests are using the resources and reallocate resources if necessary. Note With VMware ESX (ssh connection), the name of the Service console or kernel driver may be included as part of the virtual machine name.

4.2.2.1.2 Hyper-V

Reports	Analysis target and condition settings	Display item	Description
Windows server	G Specify System Group	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Track and compare trends and peaks in the usage status of CPU, disk, and memory.
HyperV (Host)	G Specify System Group	CPU Usage Rate	Track how much the physical CPU is being used and how much is available. It is possible to see information on the physical memory and disk by displaying the free memory and physical disk busy rate for "Windows Server".
HyperV (Virtual machine)	H Specify System Group and Host	CPU Usage Rate	CPU usages by guest operating systems are stacked for display. This graph makes it easy to see which guests are using the CPU. CPU usage rate is calculated with each physical CPU having a value of 100%. This means that the cumulative CPU usage rate of the CPUs of guest operating systems will be shown exceeding 100%.
		Memory Usage	Memory usages by guest operating systems are stacked for display. This graph makes it easy to see which guest is using the memory.
		Point Monitoring guest operating systems with Agents enables the system manager to see what is happening with virtual CPUs and memories. It is also possible to track physical CPU by displaying "HyperV (Virtual host)", and track the physical memory by displaying "Windows Server". When virtual resources are running low and physical resources are available, the manager can see in this report which guests are using the resources and reallocate resources if necessary.

4.2.2.1.3 Linux virtualization function (KVM)

Reports	Analysis target and condition settings	Display item	Description
UNIX server	G Specify System Group	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Track and compare trends and peaks in the use of the CPU, disk, and memory for the servers registered in the system group.
KVM (Virtual machine)	H Specify System Group and Host	CPU Usage Rate	CPU usages by guest operating systems are stacked for display. This graph makes it easy to see which guests are using the CPU. CPU usage rate is calculated with each physical CPU having a value of 100%. This means that the cumulative CPU usage rate of the CPUs of guest operating systems will be shown exceeding 100%.
		Memory Usage	Memory usages by guest operating systems are stacked for display. This graph makes it easy to see which guest is using the memory.
		Disk I/O Amount	Disk I/O by guest operating systems are stacked for display. This graph makes it easy to see which guest is using the disk.
		Point Monitoring guest operating systems with Agents enables the system manager to see what is happening with virtual CPUs, memories, and disks. It is also possible to track the physical CPU, memory, and disk by displaying "UNIX Server". When virtual resources are running low and physical resources are available, the manager can see in this report which guests are using the resources and reallocate resources if necessary.

4.2.2.1.4 Linux virtualization function (Xen)

Reports	Analysis target and condition settings	Display item	Description
UNIX server	G Specify System Group	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Track and compare trends and peaks in the use of the CPU, disk, and memory for the servers registered in the system group.
Xen (Virtual machine)	H Specify System Group and Host	CPU Usage Rate	CPU usages by guest operating systems are stacked for display. This graph makes it easy to see which guests are using the CPU. CPU usage rate is calculated with each physical CPU having a value of 100%. This means that the cumulative CPU usage rate of the CPUs of guest operating systems will be shown exceeding 100%.
		Memory Usage	Memory usages by guest operating systems are stacked for display. This graph makes it easy to see which guest is using the memory.
		Disk I/O Amount	Disk I/O by guest operating systems are stacked for display. This graph makes it easy to see which guest is using the disk.
		Point Monitoring guest operating systems with Agents enables the system manager to see what is happening with virtual CPUs, memories, and disks. It is also possible to track the physical CPU, memory, and disk by displaying "UNIX Server". When virtual resources are running low and physical resources are available, the manager can see in this report which guests are using the resources and reallocate resources if necessary.

4.2.2.1.5 Solaris Zone

Reports	Analysis target and condition settings	Display item	Description
UNIX server	G Specify System Group	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Track and compare trends and peaks in the use of the CPU, disk, and memory for the servers registered in the system group.
Solaris Zone (Virtual machine)	H Specify System Group and Host	CPU Usage Rate	CPU usage rates by zones are stacked for display. This graph makes it easy to see which zone is using the CPU.
		Memory Usage	Memory usage by zones are stacked for display. This graph makes it easy to see which zone is using the memory.
		Point It is possible to track CPU and memory usage by zone. It is also possible to track the Global Zone CPU, memory, and disk by displaying "UNIX Server". When zone resources are running low and physical resources are available, the manager can see in this report which zones are using the resources and reallocate resources if necessary.

4.2.2.1.6 Solaris Zone (Solaris 10)

This category is not displayed by default. Refer to the point in "4.1 Types of Categories" if displayed.

Reports	Analysis target and condition settings	Display item	Description
Solaris Zone(Solaris 10)	G Specify System Group	CPU Usage Rate Memory Usage	Check the status of Solaris Zone resources for the servers registered in the system group. Point If Solaris zones are bound to processor sets, the CPU usage rate will be 100% for each processor set.
Solaris Zone(Solaris 10) CPU	H Specify System Group and Host	CPU Usage Rate	Track trends and peaks for CPU usage rates in Solaris zones. Point If Solaris zones are bound to processor sets, the CPU usage rate will be 100% for each processor set.
Solaris Zone(Solaris 10) CPU	H Specify System Group and Host	CPU Usage Time	Track trends and peaks for CPU usage times in Solaris zones.
Solaris Zone(Solaris 10) memory	H Specify System Group and Host	Memory Usage Rate	Track trends and peaks for memory usage rates in Solaris zones.
		Virtual Memory Size	Track trends and peaks for virtual memory size in Solaris zones.
		Real Memory Size	Track trends and peaks for real memory size in Solaris zones.
Solaris Zone(Solaris 10) CPU (Contour)	H Specify System Group and Host	CPU Usage Rate	The rise and fall of CPU usage rates is represented by contour lines. Visually track and compare trends and peaks in CPU usage rates. This analysis is based on long-term data usage of approximately one month. Point If Solaris zones are bound to processor sets, the CPU usage rate will be 100% for each processor set.
Solaris Zone(Solaris 10) memory (Contour)	H Specify System Group and Host	Memory Usage Rate	The rise and fall of memory usage rates is represented by contour lines. Visually track and compare trends and peaks in memory usage rate. This analysis is based on long-term data usage of approximately one month.

4.2.2.2 Network

4.2.2.2.1 Systemwalker Centric Manager (Network)

Reports	Analysis target and condition settings	Display item	Description
Centric Manager traffic	H Specify System Group and Host	Line utilization rate	Track and compare trends and peaks in the line utilization rate.
Centric Manager traffic	H Specify System Group and Host	Number of octets	Track and compare trends and peaks in the number of octets.
Centric Manager packet	H Specify System Group and Host	Number of packets	Track and compare trends and peaks in the number of packets.
		Discard packet rate	It can be used to identify interfaces that have a large number of packets that cannot be sent for reasons other than data errors (insufficient buffer size, etc).
		Error packet rate	It can be used to identify interfaces that have a large number of packets that cannot be sent because of data errors.

4.2.2.2.2 Systemwalker Network Manager

Reports	Analysis target and condition settings	Display item	Description
Network Manager network traffic	H Specify System Group, Host, and Resource ID	Input network utilization rates Output network utilization rates	These items display the average and maximum network traffic values, and the time when the maximum traffic occurred. Use the displayed report to locate and correct problems.
Network Manager CPU load	H Specify System Group, Host, and Resource ID	CPU Usage rate	This item displays the average and maximum CPU usage rates, and the time when the maximum CPU usage occurred. Use the displayed report to locate and correct problems.
Network Manager collision	H Specify System Group, Host, and Resource ID	Collisions	This item displays the average and maximum numbers of collisions, and the time when the maximum number of collisions occurred. Use the displayed report to locate and correct problems.
Network Manager CRC error	H Specify System Group, Host, and Resource ID	CRC Errors	This item displays the average and maximum numbers of CRC errors, and the time when the maximum number of CRC errors occurred. Use the displayed report to locate and correct problems.
Network Manager drop packet	H Specify System Group, Host, and Resource ID	Input drop packets Output drop packets	These items display the average and maximum numbers of dropped packets, and the time when the maximum number of dropped packets occurred. Use the displayed report to locate and correct problems.
Network Manager transfer packet	H Specify System Group, Host, and Resource ID	Input packets Output packets	These items display the average and maximum numbers of sent and received packets, and the time when the maximum number of sent and received packets occurred. Use the displayed report to locate and correct problems.
Network Manager discard packet	H Specify System Group, Host, and Resource ID	Input discard packets Output discard packets	These items display the average and maximum numbers of discarded packets, and the time when the maximum number of discarded packets occurred. Use the displayed report to locate and correct problems.
Network Manager error packet	H Specify System Group, Host, and Resource ID	Input error packets Output error packets	These items display the average and maximum numbers of error packets, and the time when the maximum number of error packets occurred. Use the displayed report to locate and correct problems.
Network Manager IP operating rates	H Specify System Group, Host, and Resource ID	IP Operating rates	This item displays the average IP operating rate, the downtime length and the downtime frequency. Use the displayed report to locate and correct problems.
Network Manager RTT	H Specify System Group, Host, and Resource ID	RTT Ping	These items display the average and maximum RTT values, and the average and maximum ping loss rates. Use the displayed report to locate and correct problems.

4.2.2.2.3 TcpNetwork

This category is not displayed by default. Refer to the point in "4.1 Types of Categories" if displayed.

Reports	Analysis target and condition settings	Display item	Description
TcpNetwork	H Specify System Group, Host, and Resource ID	Number of TCP packets transferred	If application processing performance is slow even though there are no problems with server resources (CPU, memory, disk), network performance may be causing a bottleneck.
		Size of TCP packets transferred	Take the appropriate action with reference to the graph.
		Resend rate, duplicated reception rate, packet loss rate	Take the appropriate action with reference to the graph.
		Network problem situation	Take the appropriate action with reference to the graph.

4.2.2.3 Storage

4.2.2.3.1 ETERNUS SF Storage Cruiser (SAN Storage)

Reports	Analysis target and condition settings	Display item	Description
Storage CM CPU usage rate	H Specify System Group, Host, and Resource ID	CM CPU Usage Rate	Track and compare trends and peaks in the CM (Controller Module) CPU usage rate. When the CPU usage rate of one or more CMs is 85% or greater, and the CPU usage rates of the remaining CMs are 75% or greater, there is the possibility that all CMs are under a high load.
Storage CM (ROE) CPU usage rate	H Specify System Group, Host, and Resource ID	CM(ROE) CPU Usage Rate	Track and compare trends and peaks in the CM (Controller Module) ROE usage rate. When the ROE usage rate is high, it is likely that there have been a massive number of accesses to encrypted volumes or to RAID6. When the ROE usage rate is low, and the CM CPU usage rate is high, it is likely that there have been a massive number of accesses to unencrypted volumes or to RAIDGroups other than those at the RAID6 level.
Storage disk busy	H Specify System Group, Host, and Resource ID	Disk Busy	Track and compare trends and peaks in the disk usage rate. When the disk usage rate is 80% or greater, high-load applications may be concentrated in the same RAID group. Alternatively, the RAID configuration of the relevant RAID group may not be suitable.
Storage throughput	H Specify System Group, Host, and Resource ID	Throughput	Track and compare trends and peaks in the throughput.
Storage IOPS	H Specify System Group, Host, and Resource ID	IOPS	Track and compare trends and peaks in the IOPS.
Storage response time	H Specify System Group, Host, and Resource ID	Response time	Track and compare trends and peaks in response times.
Storage cache hit rate	H Specify System Group, Host, and Resource ID	Cache Hits	Track and compare trends and peaks in the cache hit rate.

4.2.2.3.2 ETERNUS SF Storage Cruiser (NAS)

Reports	Analysis target and condition settings	Display item	Description
NAS CPU usage rate	H Specify System Group, Host, and Resource ID	NAS CPU usage rate	Track and compare trends and peaks in CPU usage rates.
NAS NFS OPS	H Specify System Group, Host, and Resource ID	NAS NFS OPS	Track and compare trends and peaks in NFS handling performance.
NAS CIFS OPS	H Specify System Group, Host, and Resource ID	NAS CIFS OPS	Track and compare trends and peaks in CIFS processing performance.
NAS HTTP OPS	H Specify System Group, Host, and Resource ID	NAS HTTP OPS	Track and compare trends and peaks in HTTP processing performance.
NAS network traffic	H Specify System Group, Host, and Resource ID	Amount of network input data Amount of network output data	Track and compare trends and peaks in network traffic.
NAS Amount of DISK R/W data	H Specify System Group, Host, and Resource ID	Amount of reading data from disk Amount of writing data to disk	Track and compare trends and peaks in disk read and write data amounts.
NAS Amount of tape R/W data	H Specify System Group, Host, and Resource ID	Amount of reading data from tape Amount of writing data to tape	Track and compare trends and peaks in tape read and write data amounts.

4.2.2.4 OS

4.2.2.4.1 Windows

Reports	Analysis target and condition settings	Display item	Description
Windows server	G Specify System Group	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Check the status of resource usage for the servers registered in the system group.
Windows CPU	H Specify System Group and Host	CPU Usage Rate(User, System)	Track and compare trends and peaks in CPU usage rates. If the CPU usage rate consistently exceeds 80%, a CPU bottleneck may be degrading performance, or such a problem may be about to occur. It is necessary to consider taking actions such as increasing or upgrading the CPUs, adjusting the application execution schedule, or relocating some applications to a different server. Warning level: CPU usage rate > 80%
Windows CPU	H Specify System Group and Host	CPU Queue Length	If the number of CPU queue requests is consistently high, increasing the number of CPUs may be more effective than upgrading the CPU. Conversely, if the CPU usage rate is high when there are no queue requests, it indicates that the CPU performance is not enough to handle single processes, so a processor upgrade is recommended. Warning level: CPU queue length > 2
Windows physical disks	H Specify System Group and Host	Disk Busy	Track and compare trends and peaks in load for each disk. If the physical disk busy rate continuously exceeds 60%, the disk load is causing a bottleneck and performance problems are either occurring now or may occur in the future. Warning level: Physical disk busy >= 60%
Windows physical disks	H Specify System Group and Host	Disk Usage Rate	Track and compare trends and peaks of I/O requests for each disk. If the number of physical disk queue requests is two or more, the disk load is causing a bottleneck and performance problems are either occurring now or may occur in the future. It is necessary to take actions such as distributing the disk load or adding disks. Warning level: Number of physical disk queue requests >= 2
Windows disk space	H Specify System Group and Host	Free Memory	Track and compare trends and peaks usage of each disk.
Windows memory	H Specify System Group and Host	Page ins/Page outs	Track and compare trends and peaks in free memory amount. If the amount of available memory space approaches 4 MB intermittently, insufficient memory is causing a bottleneck, and performance problems are either occurring now or may occur in the future. Warning level: Available memory capacity < 4 MB
Windows memory	H Specify System Group and Host	Disk Usage Rate	Refer to the graph when responding to paging.
Windows process	H Specify System Group and Host	CPU Time	This graph makes it possible to identify processes that consume too much CPU time.
		Working set Size	A cumulative graph showing the size of the working set used by different processes. In the case of a computer that has a high rate of physical memory usage rate, this analysis makes it possible to identify which processes consume a large amount of physical memory.
		Pagefile Size	A cumulative graph of the pagefile required for different processes. In the case of a computer that has a high rate of virtual memory usage, this analysis makes it possible to identify which processes consume a large amount of virtual memory.
Windows CPU (Contour)	H Specify System Group and Host	CPU Usage Rate	The rise and fall of the CPU usage rate is represented by contour lines. Visually track and compare trends and peaks in CPU usage rates. This analysis is based on long-term data usage of approximately one month.
Windows physical disk (Contour)	H Specify System Group and Host	Physical Disk Busy	The rise and fall of the physical disk busy rate is represented by contour lines. Visually track and compare trends and peaks in the physical disk busy rate. This analysis is based on long-term data usage of approximately one month.
Windows memory (Contour)	H Specify System Group and Host	Free Memory	The rise and fall of available memory capacity is represented by contour lines. Visually track and compare trends and peaks available memory capacity. This analysis is based on long-term data usage of approximately one month.

4.2.2.4.2 UNIX

Reports	Analysis target and condition settings	Display item	Description
UNIX server	G Specify System Group	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Check the status of resource usage for the servers registered in the system group.
UNIX CPU	H Specify System Group and Host	CPU Usage Rate(User, System)	Track and compare trends and peaks in CPU usage rates. If the CPU usage rate consistently exceeds 80%, a CPU bottleneck may be degrading performance, or such a problem may be about to occur. It is necessary to consider taking actions such as increasing or upgrading the CPUs, adjusting the application execution schedule, or relocating some applications to a different server. Warning level: CPU usage rate > 80%
UNIX CPU	H Specify System Group and Host	CPU Queue Length	If CPU queue length > 10 or if CPU execution wait time rate > 90% or more, and (the number of queue requests) divided by (the number of processors) > 2, response may be being degraded because multiple processes are waiting for CPU allocation. If it is not possible to perform interactive job tuning or to restrict the number of concurrent processes, the user should consider increasing the number of CPUs. If CPU execution wait time rate > 90% and the number of queue requests < 1, a single program may be monopolizing the CPU. If there are no problems with the interactive job response, etc, there is no need to perform tuning. If there is a problem, lower the priority of the program that is monopolizing the CPU. Note that if there are any other resources that are experiencing a bottleneck, increasing the number of CPUs is unlikely to improve the situation. Warning level: CPU execution wait time rate > 90 and Requests count < 1 Note This information is displayed when a Solaris server is analyzed and reported.
UNIX physical disk	H Specify System Group and Host	Average Disk Busy	Track and compare trends and peaks in load for each disk. Disk access wait times start to become noticeable when the physical disk busy rate exceeds 60%. When this rate reaches 80%, wait times, including the average access times, may start to become two to three times longer than normal. When the trend is towards 80% or higher, there is more than likely a bottleneck being caused by disk load. Bottlenecks caused by disk load can be diagnosed from the following items. You will need to consider taking actions to reduce the load, such as increasing the number of disks, or moving files to disk devices that have a lower load rate (i.e., review the disposition of data): Disk busy Service times in disk access Disk Queue Warning level: Disk Busy rate >= 60% and Service Time >= 30(ms) and Number of disk queue requests >= 2
		Service Times	Service time is defined as the average time required to completely process a single I/O request. This time also includes the time spent waiting for the completion of processing of requests in the I/O queue. Warning level: Service Time >= 30(ms)
		Physical Disk Waiting Request Number	Track and compare trends and peaks of I/O requests for each disk. When the service time in disk access is equal to or greater than 30 ms, and there are a large number of requests waiting, it is likely that there is a concentration of access requests to the disk. Review the disposition of data. When the service time in disk access is equal to or greater than 30 ms, and there are not a large number of requests waiting, it is likely that there are disk devices with high loads connected within the same controller. Warning level: Service Time >= 30(ms) and Number of disk queue requests < 2
UNIX disk space	H Specify System Group and Host	Disk Usage Rate	Track and compare trends and peaks usage of each disk.
UNIX memory	H Specify System Group and Host	Free Memory	Track and compare trends and peaks in available memory capacity. If the amount of available memory space approaches the lotsfree kernel parameter (units: KB) intermittently, insufficient memory is causing a bottleneck, and performance problems are either occurring now or may occur in the future. Warning level: Available memory capacity < lotsfree
UNIX memory	H Specify System Group and Host	Swap ins/Swap outs	When swap-in is occurring: There is no problem because the memory insufficiency is temporary and swapped out processes are just being swapped in. When swap-out is occurring: There is no problem because the memory insufficiency is temporary and only unnecessary processes are swapped out. These phenomena occur due to a large amount of processes being generated temporarily. When both are occurring: Currently swapping should not normally occur with UNIX. There may be a severe memory insufficiency which requires an increase in memory. Note This information is displayed when a Solaris server is analyzed and reported.
UNIX process	H Specify System Group and Host	CPU Time	This graph makes it possible to identify processes that consume too much CPU time.
UNIX process	H Specify System Group and Host	Memory Usage Rate	A cumulative graph showing the memory usage rate of different processes. Determine which process is the cause of memory insufficiencies that occur. Note The graph showing the top ten processes using memory is not displayed in Linux.
UNIX CPU (Contour)	H Specify System Group and Host	CPU Usage Rate	The rise and fall of the CPU usage rate is represented by contour lines. Visually track and compare trends and peaks in CPU usage rates. This analysis is based on long-term data usage of approximately one month.
UNIX physical disk (Contour)	H Specify System Group and Host	Physical Disk Busy (Contour)	The rise and fall of the physical disk busy rate is represented by contour lines. Visually track and compare trends and peaks in the physical disk busy rate. This analysis is based on long-term data usage of approximately one month.
UNIX memory (Contour)	H Specify System Group and Host	Free Memory	The rise and fall of available memory capacity is represented by contour lines. Visually track and compare trends and peaks in memory usage. This analysis is based on long-term data usage of approximately one month.

4.2.2.4.3 Common to all operating systems

Reports	Analysis target and condition settings	Display item	Description
Disk space	G Specify System Group	Disk Usage Rate Disk Availability	Check the status of disk usage for the servers registered in the system group.

Reports

Analysis target and condition settings

Display item

Description

Disk space

Specify System Group

Disk Usage Rate
Disk Availability

Check the status of disk usage for the servers registered in the system group.

4.2.2.5 Web

4.2.2.5.1 Web transaction

Reports	Analysis target and condition settings	Display item	Description
Web transaction	G Specify System Group	Request count Traffic Error count	Track and compare trends and peaks in the number of requests for each service and the time used for the requests. If the number of requests in each service, or the time required by requests exceeds the expected value, the user can consider taking actions such as adding another Web server.
Web transaction request	H Specify System Group, Host, and Resource ID	Web transaction request(Request Count,Time Taken)	Track and compare trends and peaks in traffic volume for each service. If the volume of traffic exceeds the expected value, the user can consider taking actions such as adding another Web server.
Web transaction hitserver	H Specify System Group, Host, and Resource ID	Hit Server Count	Track the occurrence of server hits in each service.
Web transaction hitclient	H Specify System Group, Host, and Resource ID	Hit Client Count	Track the occurrence of client hits in each service.
Web transaction hitremote	H Specify System Group, Host, and Resource ID	Hit Remote Count	Track the occurrence of remote hits in each service.
Web transaction traffic	H Specify System Group, Host, and Resource ID	Traffic	Track and compare trends and peaks in traffic volume for each service. If the volume of traffic exceeds the expected value, the user can consider taking actions such as adding another Web server.
Web transaction error	H Specify System Group, Host, and Resource ID	Error count	Track the occurrence of errors in each service.

4.2.2.6 Application

4.2.2.6.1 Interstage Application Server (IJServer Cluster)

Reports	Analysis target and condition settings	Display item	Description
Interstage IJServer Cluster	G Specify System Group	Current Heap Size Current Perm Garbage Collection	Check the JavaVM heap and Perm area usage amount, and garbage collection occurrences for the servers registered in the system group.
Interstage IJServer Cluster JVM	H Specify System Group, Host, and Resource ID	Heap Size(avg/max/min)	Displays Java VM heap information. Track and compare trends and peaks in the heap information.
		Perm Size(avg/max/min)	Displays Java VM Perm area information. Track and compare trends and peaks in Perm area information.
		Garbage collections	Displays Java VM Garbage collection information. Track the occurrence of Garbage collections.
Interstage IJServer Cluster JTA	H Specify System Group, Host, and Resource ID	Transaction(avg/max/min)	Displays information about transactions used by applications. Track and compare trends and peaks in transaction counts.
Interstage IJServer Cluster JDBC	H Specify System Group, Host, and Resource ID	Connection Pool(avg/max/min)	Information about JDBC connections that are pooled by Interstage. Track and compare trends and peaks in connection counts.
Interstage IJServer Cluster JDBC	H Specify System Group, Host, and Resource ID	Connection Acquisition Wait Status(avg/max/min)	When an attempt is made to obtain a connection from the pool but the maximum number of connections has already been reached, the system will wait for the connection timeout period until a connection is returned. This information relates to waiting for the connection to be returned. Track and compare trends and peaks in the frequency of connection waiting and the number of threads that are waiting for a connection.
Interstage IJServer Cluster Thread Pool	H Specify System Group, Host, and Resource ID	Work items in queue	The number of work items in the queue. Track the number of work items in a queue.
		Total busy threads	This is the total number of busy threads in a thread pool. Track the total number of busy threads in a thread pool.
		Average completion time of work items	This is statistical information about the average completion time of work items. Track the average completion time of work items.
		Total usable threads	This is the total number of usable threads in a thread pool. Track the total number of usable threads in a thread pool.

4.2.2.6.2 Interstage Application Server (Work Unit)

Reports	Analysis target and condition settings	Display item	Description
Interstage(EJB)	G Specify System Group	EJB Application Processing Time	Check the processing times for EJB applications of the servers registered in the system group.
Interstage(TD)	G Specify System Group	Object Processing Time	Check the processing times for transaction applications of the servers registered in the system group.
Interstage (CORBA)	G Specify System Group	Implementation Repository ID Processing Time	Check the processing times for CORBA applications of the servers registered in the system group.
Interstage(IJServer)	G Specify System Group	Current Heap Size Current Perm	Check the size used by the heap and Perm area of the JavaVM of the servers registered in the system group.
Interstage EJB application	H Specify System Group, Host, and Resource ID	EJB Application Processing Time(avg/max/min)	The maximum, minimum and average processing times for EJB applications. When the maximum processing time for an entire period (one day) is long and the average processing time is close to the maximum processing time. The following causes are possible: There is a performance-related problem with the server application. The load on the system is high. Review the server applications and the system, giving particular attention to the above factors. When the maximum, minimum and average processing times within a specific period are long. The load on the system may be high during a specific time period. Measure the performance of other server applications as well to confirm the load status. When the maximum processing time is long but the average processing time is short and close to the minimum processing time. The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors.
		Wait Time(avg/max/min)	The maximum, minimum and average times from when a client receives a request until a method commences processing. When the maximum, minimum and average wait times during a specific period are long. The load on the system may be high during a specific time period. Measure the performance of other server applications as well to confirm the load status. When the maximum wait time is long but the average wait time is short and close to the minimum wait time. The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors. When the maximum wait time and the average wait time are long throughout a performance monitoring period. The performance of a server application is not sufficient to handle the number of requests from a client. Take actions to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition.
		Requests / Wait Queues	The cumulative number of processes that have been handled by the object since performance monitoring began, and the maximum number of requests that had to await processing by the object. When there are many processes and process wait requests within a specific period. The number of requests to a server application within a specific period has increased. When the performance of a server application is not sufficient to handle the number of requests from a client, take actions to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. Measure the performance of other server applications as well to confirm the load status. When the number of process wait requests is large but the average wait time is short. Use the isinfobj command to regularly check the queue status, and also check the load status during the collection interval.
		VM memory used	Maximum and average values of the amount of VM memory used. If a large amount of VM memory is being used, there may be a memory leak. Review the server applications with a view to identifying objects that can be deleted.
		Sessions	The number of current EJB objects. If the number of EJB objects has become larger than the number of connected (deployed) clients, this means that EJB objects may not have been removed when each session was disconnected, for every EJB object created when the session was established. If this is the case, make sure that each EJB object is removed when the session is disconnected.
Interstage CORBA application	H Specify System Group, Host, and Resource ID	Processing Time(avg/max/min)	The maximum, minimum and average processing times for CORBA applications. When the maximum processing time for an entire period (one day) is long and the average processing time is close to the maximum processing time. The following causes are possible: There is a performance-related problem with the server application. The load on the system is high. When the maximum, minimum and average processing times within a specific period are long. The load on the system may be high during a specific time period. Measure the performance of other server applications as well to confirm the load status. When the maximum processing time is long but the average processing time is short and close to the minimum processing time. The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors.
		Wait Time(avg/max/min)	The maximum, minimum and average times from when a client receives a request until an operation commences processing. When the maximum, minimum and average wait times during a specific period are long. The load on the system may be high during a specific time period. Measure the performance of other server applications as well to confirm the load status. When the maximum wait time is long but the average wait time is short and close to the minimum wait time. The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors. When the maximum wait time and the average wait time are long throughout a performance monitoring period. The performance of a server application is not sufficient to handle the number of requests from a client. Take actions to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition.
		Requests / Wait Queues	The cumulative number of processes that have been handled by the object since performance monitoring began, and the maximum number of requests that had to await processing by the object. When there are many processes and process wait requests within a specific period. The number of requests to a server application within a specific period has increased. When the performance of a server application is not sufficient to handle the number of requests from a client, take actions to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. Measure the performance of other server applications as well to confirm the load status. When the number of process wait requests is large but the average wait time is short. Use the isinfobj command to regularly check the queue status, and also check the load status during the collection interval.
Interstage transaction application	H Specify System Group, Host, and Resource ID	Object Processing Time(avg/max/min)	The maximum, minimum, and average processing times for transaction applications. When the maximum processing time for an entire period (one day) is long and the average processing time is close to the maximum processing time. The following causes are possible: There is a performance-related problem with the server application. The load on the system is high. When the maximum, minimum and average processing times within a specific period are long. The load on the system may be high during a specific time period. Measure the performance of other server applications as well to confirm the load status. When the maximum processing time is long but the average processing time is short and close to the minimum processing time. The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors.
		Wait Time(avg/max/min)	The maximum, minimum and average times from when a client receives a request until an object commences processing. When the maximum, minimum and average wait times during a specific period are long. The load on the system may be high during a specific time period. Measure the performance of other server applications as well to confirm the load status. When the maximum wait time is long but the average wait time is short and close to the minimum wait time. The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors. When the maximum wait time and the average wait time are long throughout a performance monitoring period. The performance of a server application is not sufficient to handle the number of requests from a client. Take actions to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition.
		Requests/Wait queues	The cumulative number of processes that have been handled by the object since performance monitoring began, and the maximum number of requests that had to await processing by the object. When there are many processes and process wait requests within a specific period. The number of requests to a server application within a specific period has increased. When the performance of a server application is not sufficient to handle the number of requests from a client, take actions to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. Measure the performance of other server applications as well to confirm the load status.
Interstage IJServer JVM	H Specify System Group, Host, and Resource ID	Heap Size(avg/max/min)	Track and compare trends and peaks in Java VM heap information.
		Perm Size(avg/max/min)	Track and compare trends and peaks in Java VM Perm area information.
		Garbage collections(avg/max/min)	Track and compare trends and peaks in the number of occurrences of Garbage collection in Java VM.
Interstage IJServer JTA	H Specify System Group, Host, and Resource ID	Transaction(avg/max/min)	Displays information about transactions used by applications. Track and compare trends and peaks in transaction counts.
Interstage IJServer JDBC	H Specify System Group, Host, and Resource ID	Connection Pool(avg/max/min)	Information about JDBC connections that are pooled by Interstage. Track and compare trends and peaks in connection counts.
		Connection Acquisition Wait Status(avg/max/min)	When an attempt is made to obtain a connection from the pool but the maximum number of connections has already been reached, the system will wait for the connection timeout period until a connection is returned. This information relates to waiting for the connection to be returned. Track and compare trends and peaks in the frequency of connection waiting and the number of threads that are waiting for a connection.
		Establishment of Physical Connection(avg/max/min)	Information about established connections and discarded connections. Track and compare trends and peaks in the number of established connections.
		Acquisition of Connection from Application(avg/max/min)	Information about connections used by applications. Track and compare trends and peaks in the number of established connections, etc.
Interstate IJSserver SERVLET CONTAINER	H Specify System Group, Host, and Resource ID	Number sum total of Threads (avg/max/min)	Information about the total number of threads. Track and compare trends and peaks in thread counts.
Interstate IJSserver SERVLET CONTAINER	H Specify System Group, Host, and Resource ID	Number of Threads currently in progress (avg/max/min)	Information about the number of threads currently being processed. Track the number of threads currently being processed.
Interstate IJSserver SERVLET WEBMODULE	H Specify System Group, Host, and Resource ID	The effective number of Sessions (avg/max/min)	Check the number of valid sessions.
Interstage IJSserver EVENT SERVICE	H Specify System Group, Host, and Resource ID	Number of Connected consumers (avg/max/min)	Check the number of connected consumers.
		Number of Connected suppliers (avg/max/min)	Check the number of connected suppliers.
		Number of Accumulated event data items (avg/max/min)	Check the number of accumulated event data items.

4.2.2.6.3 Oracle WebLogic Server

Reports	Analysis target and condition settings	Display item	Description
WebLogic Server	G Specify System Group	Current heap size Garbage collection	Check the JavaVM heap information for the servers registered in the system group and number of occurrences of Garbage collections.

Reports

Analysis target and condition settings

Display item

Description

WebLogic Server

Specify System Group

Current heap size
Garbage collection

Check the JavaVM heap information for the servers registered in the system group and number of occurrences of Garbage collections.

4.2.2.6.4 Microsoft .NET

Reports	Analysis target and condition settings	Display item	Description
MS-.NET	G Specify System Group	Requests Count Wait Queues	Check the number of requests and the request queue status for the servers registered in the system group.
MS-.NET ASP.NET	H Specify System Group, Host, and Resource ID	Waiting Demands for Processing Count	Track the number of MS-.NET requests waiting to be processed. When the maximum processing time for an entire period (one day) is long and the average processing time is close to the maximum processing time. The following causes are possible: There is a performance-related problem with the server application. The load on the system is high. Review the server applications and the system, giving particular attention to the above factors. When the maximum, minimum and average processing times within a specific period are long. The load on the system may be high during a specific time period. Measure the performance of other server applications as well to confirm the load status. When the maximum processing time is long but the average processing time is short and close to the minimum processing time. The following causes are possible: The system load became high temporarily. There is a performance-related problem with a server application under specific conditions. Review the system and server applications, giving particular attention to the above factors.
		Application Reboot Count	Track the number of MS-.NET application reboots. Take the appropriate action with reference to the graph.
		Worker Process Reboot Count	Track the MS-.NET worker process reboot count. Take the appropriate action with reference to the graph.
MS-.NET Applications	H Specify System Group, Host, and Resource ID	Transaction Count	Track the number of MS-.NET transactions. Take the appropriate action with reference to the graph.
		Number of Execution Requests	Track the number of MS-.NET execution requests. Take the appropriate action with reference to the graph.
		Session Count	Track the number of active MS-.NET sessions. Take the appropriate action with reference to the graph.
		Error Count	Track the total number of MS-.NET errors. Take the appropriate action with reference to the graph.
MS-.NET Remote procedure	H Specify System Group, Host, and Resource ID	Total Number of Remote Procedure Calls	Track the total number of remote procedure calls for MS-.NET. Take the appropriate action with reference to the graph.

4.2.2.6.5 SAP NetWeaver

Reports	Analysis target and condition settings	Display item	Description
SAP	G Specify System Group	Dialog Response Time Enqueue Enqueue Requests/Queue Length Background Utilization Execution Waiting RFC Total Calls	Check the Dialog response time, number of Enqueue requests and queue length, background usage rate, and number of RFC calls waiting for execution on SAP on the servers registered in the system group.
SAP Enqueue(Request)	H Specify System Group, Host, and Resource ID	Enqueue Requests	Track and compare trends and peaks in the number of enqueue requests.
		Enqueue Requests Errors	Track and compare trends and peaks in the number of enqueue request errors.
		Dequeue Requests	Track and compare trends and peaks in the number of dequeue requests.
		Dequeue Requests Errors	Track and compare trends and peaks in the number of dequeue request errors.
		Exclusion lock wait time	Track and compare trends and peaks in the time that parallel processes spend waiting to access lock tables.
		Server time	Track and compare trends and peaks in the time spent in the enqueue server.
		Runtime of data collector	Track and compare trends and peaks in the time that the data collector (the RSCOLL00 program) spends executing.
SAP Enqueue(QueLength)	H Specify System Group, Host, and Resource ID	Queue Length	Enqueue server monitoring object: Track and compare trends and peaks in queue length.
		Utilization (Lock owner)	Track and compare trends and peaks in the usage rates for lock owners within lock tables.
		Utilization (Lock arguments)	Track and compare trends and peaks in the usage rates for lock arguments within lock tables.
		Utilization (Elementary Locks)	Track and compare trends and peaks in the usage rates for elementary locks within lock tables.
		Errors	Track and compare trends and peaks in the number of errors that occur with enqueue work processes.
SAP Dialog	H Specify System Group, Host, and Resource ID	Response Time	Track and compare trends and peaks in the response times for the Dialog Service.
		Front End Wait Time	Track and compare trends and peaks in front-end standby times.
		Dispatcher Wait Time	Track and compare trends and peaks in the dispatcher standby times for each dialog step.
		Load /Generation Time	Track and compare trends and peaks in the load/generation times for GUI objects.
		Roll Time	Track and compare trends and peaks in roll times.
		DB Request Time	Track and compare trends and peaks in the processing times for logical database requests.
		Load Factor	Track and compare trends and peaks in the rate of load that Dialog processes place on the application server.
		Dispatcher wait time	Track and compare trends and peaks in the number of Dialog steps.
SAP Spool	H Specify System Group, Host, and Resource ID	Load Factor	Track and compare trends and peaks in the load rate for spool work processes.
SAP Spool	H Specify System Group, Host, and Resource ID	Errors	Track and compare trends and peaks in the number of errors that occur with spool work processes.
SAP Background	H Specify System Group, Host, and Resource ID	Load Factor	Track and compare trends and peaks in the load rate for background work processes.
SAP Background	H Specify System Group, Host, and Resource ID	Errors	Track and compare trends and peaks in the number of errors that occur with background work processes.
SAP Update	H Specify System Group, Host, and Resource ID	Response Time	SAP Update task V1: Track and compare trends and peaks in the response times for each Dialog Step.
		Dispatcher wait time	SAP Update task V1: Track and compare trends and peaks in the dispatcher standby times in dispatcher queues.
		Load factor (V1)	SAP Update task V1: Track and compare trends and peaks in the load for update task work processes.
		Errors (V1)	Track and compare trends and peaks in the number of errors that have occurred for Update 1 work processes.
		Load factor (V2)	SAP Update task V2: Track and compare trends and peaks in the load for update 2 task work processes.
		Errors (V2)	Track and compare trends and peaks in the number of errors that have occurred for Update 2 work processes.
SAP Roll Paging	H Specify System Group, Host, and Resource ID	Paging area utilization	Track and compare trends and peaks in the paging area usage rate.
SAP Roll Paging	H Specify System Group, Host, and Resource ID	Roll area utilization	Track and compare trends and peaks in the roll area usage rate.
SAP Memory	H Specify System Group, Host, and Resource ID	Extended Memory Utilization	Track and compare trends and peaks in the extended memory usage rate.
		Heap Memory Utilization	Track and compare trends and peaks in the heap memory usage rate.
		Management Slots Utilization	Track and compare trends and peaks in the usage rate for EM management slots.
		Work Processes	Track and compare trends and peaks in the number of work processes in PRIV mode.
SAP Buffers	H Specify System Group, Host, and Resource ID	Buffer Utilization	Track and compare trends and peaks in the buffer usage rate.

4.2.2.6.6 Workload

This category is not displayed by default. Refer to the point in "4.1 Types of Categories" if displayed.

Reports	Analysis target and condition settings	Display item	Description
Workload	H Specify System Group, Host, and Resource ID	Allocated CPU Used CPU	Track and compare the amount of allocated CPU resources and the amount of used CPU resources for resource modules. Take the appropriate action with reference to the graph.

Reports

Analysis target and condition settings

Display item

Description

Workload

Specify System Group, Host, and Resource ID

Allocated CPU
Used CPU

Track and compare the amount of allocated CPU resources and the amount of used CPU resources for resource modules.

Take the appropriate action with reference to the graph.

4.2.2.7 Database

4.2.2.7.1 Symfoware server

Reports	Analysis target and condition settings	Display item	Description
Symfoware	G Specify System Group	Buffer hit ratio Buffer Dry up SQL executions Deadlocks	Check the buffer cache hit rate, number of deadlocks, and number of SQL executions in Symfoware on the servers registered in the system group.
Symfoware shared buffer	H Specify System Group, Host, and Resource ID	Buffer Hit Ratio	The rate at which the shared buffer was hit (%). Fine-tune the shared buffer. Note that when application programs that mainly access a wide area of the table are executed without the addition of indexes, the on-buffer hit rate will become 0% or something similar, but this does not indicate a problem.
Symfoware shared buffer	H Specify System Group, Host, and Resource ID	Buffer Dry Up	The number of times that no unused buffers were available. Fine-tune the shared buffer.
Symfoware log area	H Specify System Group, Host, and Resource ID	Recovery Log Over Count	The number of times that the recovery log overflowed and a checkpoint occurred. Check the size of the recovery log, and increase it as necessary.
		Transaction Entry Dry Up Count	Indicates if the transaction entries have been used up. Increase the number of transaction entries.
		BI Log Dry Up Count	Indicates if the BI log area has been used up. Increase the size of the BI log area.
Symfoware disk I/O	H Specify System Group, Host, and Resource ID	DB Space I/O	The number of I/O operations for each database space. Take the appropriate action with reference to the graph.
Symfoware database space usage rate	H Specify System Group, Host, and Resource ID	Database Space Usage Rate	Track and compare usage trends and peaks for each database space.

4.2.2.7.2 Oracle database

Reports	Analysis target and condition settings	Display item	Description
Oracle	G Specify System Group	Buffer cache hit ratio Deadlocks	Check the buffer cache hit rate and number of deadlocks on the Oracle servers registered in the system group.
Oracle SGA	H Specify System Group, Host, and Resource ID	Buffer Cache Hit Ratio	The role of buffer caches is to reduce the number of accesses to the disk (data files). Increase the value of the initialization parameter "DB_BLOCK_BUFFERS" or "DB_CACHE_SIZE" that specifies the size of the buffer cache. * "DB_CACHE_SIZE" is a new initialization parameter that was added in Oracle9i. * Pay attention to the remaining physical memory capacity.
		REDO log buffer cache	The REDO log buffer cache stores the information that is written to the online REDO log. If processing to write to the REDO log buffer cache enters a wait state, increase the value of the initialization parameter "LOG_BUFFERS". If I/O processing performed from the REDO log buffer cache to a disk enters a wait state, move the REDO log file to a dedicated disk or a high-speed RAID device. If the REDO log file is located on the file system, consider using direct I/O or moving to a raw device.
		Library Cache Hit Ratio	The library cache stores the SQL statements that have been parsed and can be executed. Increase the value of the initialization parameter "SHARED_POOL_SIZE". Pay attention to the remaining physical memory capacity.
		Data Dictionary Cache Hit Ratio	The dictionary cache stores data dictionary information such as the status of file space for database segments (indexes, sequence, tables, etc) and object permissions. Increase the value of the initialization parameter "SHARED_POOL_SIZE". Pay attention to the remaining physical memory capacity.
Oracle PGA	H Specify System Group, Host, and Resource ID	Memory sort hit rate	Sorts should be performed in memory whenever possible. Sorting in memory is far quicker than using the disk. Increase the value of the initialization parameter "SORT_AREA_SIZE" or "PGA_AGGREGATE_TARGET". * "PGA_AGGREGATE_TARGET" is a new initialization parameter that was added in Oracle9i. * Pay attention to the remaining memory capacity. * Because changes to the above initialization parameter can change the execution plans for optimizing all SQL statements, be wary of changing the value, unless the memory sort hit rate has become a major problem.
Oracle disk I/O	H Specify System Group, Host, and Resource ID	Amount of free table space area	Displays the minimum value for the available tablespace capacity. Expand or add data files.
Oracle disk I/O	H Specify System Group, Host, and Resource ID	Volume of database I/O	Displays the volume of database I/O. Take the appropriate action with reference to the graph.
Oracle resource conflict	H Specify System Group, Host, and Resource ID	Ratio of zero rollback segment wait time	Ideally, rollback segment header waiting should be kept to zero or a very small amount. When rollback segments are being used, there are an insufficient number of rollback segments and some need to be added. * If the UNDO table space is being used in Oracle9i or later, tuning will take place automatically.
Oracle table space usage rate	H Specify System Group, Host, and Resource ID	Oracle tablespace	Track and compare trends and peaks in usage for each tablespace.

4.2.2.7.3 Microsoft SQL Server

Reports	Analysis target and condition settings	Display item	Description
MS-SQL	G Specify System Group	Buffer cache hit ratio Deadlocks Count Transaction Count	Check the buffer cache hit rate and number of deadlocks on SQL Servers on the servers registered in the system group.
MS-SQL ACCESS METHOD	H Specify System Group, Host, and Resource ID	Full Scan Count Index Count	Track and compare MS-SQL access methods. Take the appropriate action with reference to the graph.
MS-SQL Server BUFFER	H Specify System Group, Host, and Resource ID	Buffer Cache Hit Count	Track the number of MS-SQL buffer cache hits. Take the appropriate action with reference to the graph.
MS-SQL Server BUFFER	H Specify System Group, Host, and Resource ID	Access Count	Track the number of MS-SQL accesses. Take the appropriate action with reference to the graph.
MS-SQL Server CMGR	H Specify System Group, Host, and Resource ID	Cache hit rate	Track MS-SQL cache hit rates. Take the appropriate action with reference to the graph.
MS-SQL Server CMGR	H Specify System Group, Host, and Resource ID	Hits Count	Track the number of MS-SQL hits. Take the appropriate action with reference to the graph.
MS-SQL Server DATABASES	H Specify System Group, Host, and Resource ID	Transaction Count	Track the number of MS-SQL transactions. Take the appropriate action with reference to the graph.
		Active Transaction Count	Track the number of MS-SQL active transactions. Take the appropriate action with reference to the graph.
		Log Area Ratio	Track the MS-SQL log area ratio. Take the appropriate action with reference to the graph.
MS-SQL Server GENERALSTATISTICS	H Specify System Group, Host, and Resource ID	Number of Connected Users	Track the number of connected users for MS-SQL. Take the appropriate action with reference to the graph.
MS-SQL Server LOCKS	H Specify System Group, Host, and Resource ID	Deadlocks Count	Track the number of MS-SQL deadlocks. Take the appropriate action with reference to the graph.
MS-SQL Server LOCKS	H Specify System Group, Host, and Resource ID	Number of standby waiting lock requests	Track the number of MS-SQL standby waiting lock requests. Take the appropriate action with reference to the graph.
MS-SQL Server MEMORY	H Specify System Group, Host, and Resource ID	Total Amount of Memory	Track the memory capacity for MS-SQL. Take the appropriate action with reference to the graph.
MS-SQL Server STATISTICS	H Specify System Group, Host, and Resource ID	Number of SQLS Batch Requests	Track the number of requests for MS-SQL batches. Take the appropriate action with reference to the graph.

4.2.2.8 Job

4.2.2.8.1 Systemwalker Operation Manager

Reports	Analysis target and condition settings	Display item	Description
Operation Manager	G Specify System Group	Job multiplicity Number of execution waiting jobs Number of jobs that have exceeded the predicted time Number of jobs that end Number of Error Jobs	Check the multiplicity and jobs waiting for execution on the Systemwalker Operation Manager in the servers registered in the system group.
Operation Manager subsystem	H Specify System Group, Host, and Resource ID	Job multiplicity of each Subsystem (Job multiplicity, Network/Distributed execution job multiplicity)	Track and compare trends and peaks in job multiplicity of each subsystem (Job multiplicity, Network/Distributed execution job multiplicity). If the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, review job schedules and reduce the level of concurrency.
		Job net multiplicity of each Subsystem	Check deviations and peaks in the job net concurrency of different subsystems.
		Number of execution waiting jobs of each Subsystem	Track and compare trends and peaks in the number of pending jobs in different subsystems. If the number of pending jobs is large, review the job execution schedule.
		Execution waiting time of each Subsystem	Track and compare trends and peaks in the job execution wait times of different subsystems. If the execution wait time is long and the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, take actions to reduce the level of job concurrency.
		Number of jobs that have exceeded the predicted time of each Subsystem	Track and compare trends and peaks in the number of jobs with execution time overruns in different subsystems. If the number of jobs with execution time overruns is large and the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, take actions to reduce the level of job concurrency.
		Number of completed jobs by subsystem	Track and compare trends and peaks in the number of completed jobs in different subsystems. The number of completed jobs by subsystem also includes the following number of error jobs by subsystem.
		Number of error jobs by subsystem	Track the number of error jobs in different subsystems.
Operation Manager queue	H Specify System Group, Host, and Resource ID	Job multiplicity of each Queue (Job multiplicity, Network/Distributed execution job multiplicity)	Track and compare trends and peaks in job multiplicity of each Queue (Job multiplicity, Network/Distributed execution job multiplicity). If the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, review job schedules and reduce the level of concurrency.
		Job net multiplicity of each Queue	Track and compare trends and peaks in the job net multiplicity of different queues.
		Number of execution waiting jobs of each Queue	Track and compare trends and peaks in the number of pending jobs in different queues. If the number of pending jobs is large, review the job execution schedule.
		Execution waiting time of each Queue	Track and compare trends and peaks in the job execution wait times of different queues. If the execution wait time is long and the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, take actions to reduce the level of job concurrency.
		Number of jobs that have exceeded the predicted time of each Queue	Track and compare trends and peaks in the number of jobs with execution time overruns in different queues. If the number of jobs with execution time overruns is large and the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, take actions to reduce the level of job concurrency.
Operation Manager project	H Specify System Group, Host, and Resource ID	Job multiplicity of each Project	Track and compare trends and peaks in the job multiplicity of different projects. If the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, review job schedules and reduce the level of concurrency.
		Job net multiplicity of each Project	Track and compare trends and peaks in the job net multiplicity of different projects.
		Number of execution waiting jobs of each Project	Track and compare trends and peaks in the number of pending jobs in different projects. If the number of pending jobs is large, review the job execution schedule.
		Execution waiting time of each Project	Track and compare trends and peaks in the job execution wait times of different projects. If the execution wait time is long and the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, take actions to reduce the level of job concurrency.
		Number of jobs that have exceeded the predicted time of each Project	Track and compare trends and peaks in the number of jobs with execution time overruns in different projects. If the number of jobs with execution time overruns is large and the CPU usage rate, available memory capacity, disk usage rate, or some other item exceeds a warning level, take actions to reduce the level of job concurrency.
		Number of completed jobs by project	Track and compare trends and peaks in the number of completed jobs in different projects. The number of completed jobs by project also includes the following number of error jobs by project.
		Number of error jobs by project	Track the number of completed error jobs in different projects.

Reports	Analysis target and condition settings	Display item	Description
ISI Sequence	G Specify System Group	Number of transactions	Check the ISI sequence information of the servers registered in the system group.
ISI Queue	G Specify System Group	Number of retention	Check the ISI queue information of the servers registered in the system group.
ISI Sequence	H Specify System Group, Host, and Resource ID	Number of transactions	Track and compare trends and peaks in the number of process in each sequence.
ISI Queue	H Specify System Group, Host, and Resource ID	Number of retention	Track and compare trends and peaks in the number of remaining items in each queue.

Reports	Analysis target and condition settings	Display item	Description
HTTP service	G Specifications for displays that include service operational information	HTTP Operating rate	Check the status of the HTTP service to be monitored that is registered in the system group.
SMTP service	G Specifications for displays that include service operational information	STMP Operating rate	Check the status of the SMTP service to be monitored that is registered in the system group.
DNS service	G Specifications for displays that include service operational information	DNS Operating rate	Check the status of the DNS service to be monitored that is registered in the system group.
PORT service	G Specifications for displays that include service operational information	PORT Operating rate	Check the status of the PORT to be monitored that is registered in the system group.

Reports	Analysis target and condition settings	Display item	Description
Time-series	H Specify detailed items	-	Displays specified field values as chronological graphs and tables.
Summary data time series display	H Specify detailed items	-	Display the summary data as a time-series graph or table.
Correlation display	H Specifications for displays that include correlations/compositions	-	Displays two specified field values as correlation graphs and regression line graphs.
Contour display	H Specifications for displays that include contours	-	Displays specified fields as contour graphs. This analysis is based on long-term data usage of approximately one month.
Comparison display of the past	H Specifications for displays that include past comparisons	-	Displays a graph that allows hourly data from the past month and the past week to be compared side-by-side with the data for the base day
Transition comparison display according to day	H Specifications for displays that include daily transition comparisons	-	Displays a graph that compares data trends for the specified date and time period.
Composite display	H Specifications for displays that include correlations/compositions	-	Displays a graph that allows two different items (such as response time and CPU usage rate) to be compared side-by-side.