4.2.2 Performance analysis

Report	Analysis method of setting Element and condition	Item	Description
VMware (Cluster)	H System group and host specification	CPU Usage Memory Usage	The amount of CPU use and the memory utilization of the cluster are displayed. Which cluster uses CPU or the memory from this graph can be understood. Point CPU of each cluster and the status of the memory can be understood. Moreover, host's CPU, memory, and disk can be understood by displaying "VMware(Host)".
VMware (Resource pool)	H System group and host specification	CPU Usage Memory Usage	The amount of CPU use and the memory utilization of the resource pool are displayed. Which resource pool uses CPU or the memory from this graph can be understood. Point CPU at each resource pool and the status of the memory can be understood. Moreover, host's CPU, memory, and disk can be understood by displaying "VMware(Host)". When a virtual resource is insufficient and the resource of physics has become empty, the review of the allocation can be examined by seeing which resource pool whether to use the resource in this report.
VMware (Host)	G System group specification	CPU Usage Rate Free Memory Amount Disk I/O Count	The status of physics of CPU, the memory, and the disk is confirmed.
VMware (Virtual machine)	H System group and host specification	CPU Usage Rate	CPU usage rates by guest OSs are stacked for display. This graph makes it easy to see which guest is 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 usage by guest OSs 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 OSs 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 see information about the physical CPU, memory, and disk by displaying "VMware (Host)". When virtual resources are running low and physical resources are available, the manager can see which guests are using the resources in this report and reallocate resources if necessary. Note The name of the service console and the kernel driver, etc. might be included as a virtual machine name for VMware ESX (ssh connection).

4.2.2.1.2 Hyper-V

Report	Analysis method of setting Element and condition	Item	Description
Windows server	G System group specification	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Bias of the status of CPU, the disk, and the memory and the peak are understood.
HyperV (Host)	G System group specification	CPU Usage Rate	How much has become empty can be understood. how many CPU of physics used The memory and the disk of physics can be understood by displaying an empty memory capacity and a physical disk busy rate of "Windows server".
HyperV (Virtual machine)	H System group and host specification	CPU Usage Rate	CPU usage rates by guest OSs are stacked for display. This graph makes it easy to see which guest is 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 usage by guest OSs 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, memories, and disks. It is also possible to see information about the physical CPU, memory, and disk by displaying "Windows server". When virtual resources are running low and physical resources are available, the manager can see which guests are using the resources in this report and reallocate resources if necessary.

4.2.2.1.3 Linux Virtualization function (KVM)

Report	Analysis method of setting Element and condition	Item	Description
UNIX server	G System group specification	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Bias of the status of CPU, the disk, and the memory and the peak of the server registered in the system group are understood.
KVM (Virtual machine)	H System group and host specification	CPU Usage Rate	CPU usage rates by guest OSs are stacked for display. This graph makes it easy to see which guest is 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 usage by guest OSs 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 OSs 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 see information about 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 which guests are using the resources in this report and reallocate resources if necessary.

4.2.2.1.4 Linux Virtualization function (Xen)

Report	Analysis method of setting Element and condition	Item	Description
UNIX server	G System group specification	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Bias of the status of CPU, the disk, and the memory and the peak of the server registered in the system group are understood.
Xen (Virtual machine)	H System group and host specification	CPU Usage Rate	CPU usage rates by guest OSs are stacked for display. This graph makes it easy to see which guest is 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 usage by guest OSs 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 OSs 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 see information about 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 which guests are using the resources in this report and reallocate resources if necessary.

4.2.2.1.5 Solaris Zone

Report	Analysis method of setting Element and condition	Item	Description
UNIX server	G System group specification	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	Bias of the status of CPU, the disk, and the memory and the peak of the server registered in the system group are understood.
Solaris Zone (Virtual machine)	H System group and host specification	CPU Usage Rate	CPU utilization of the zone piles up and it is displayed. Which zone uses CPU from this graph can be understood.
		Memory Usage	The memory utilization of the zone piles up and it is displayed. Which zone uses the memory from this graph can be understood.
		Point CPU of each zone and the status of the memory can be understood. Moreover, CPU, the memory, and the disk of Global Zone can be understood by displaying "UNIX server". When the resource of the zone is insufficient, and the resource of physics has become empty, the review of the allocation can be examined by seeing which zone whether to use the resource in this report.

4.2.2.1.6 Solaris Zone(Solaris 10)

This category is not displayed in default. Please refer to the point of "4.1 Types of Categories" when you display it.

Report	Analysis method of setting Element and condition	Item	Description
Solaris Zone(Solaris 10)	G System group specification	CPU Usage Rate Memory Usage	The situation of the resource of Solaris Zone is confirmed about the server registered in the system group. Point CPU utilization becomes the unit of the processor set with 100% when the Solaris zone is in the processor set and it uses it.
Solaris Zone(Solaris 10) CPU	H System group and host specification	CPU Usage Rate	The tendency to CPU utilization of the Solaris zone and the peak are understood. Point CPU utilization becomes the unit of the processor set with 100% when the Solaris zone is in the processor set and it uses it.
Solaris Zone(Solaris 10) CPU	H System group and host specification	CPU Usage Time	The tendency to the Solaris zone at CPU used hours and peaks are understood.
Solaris Zone(Solaris 10) memory	H System group and host specification	Memory Usage	The tendency to the memory percentage utilisation of the Solaris zone and the peak are understood.
		Virtual Memory Size	The virtual memory size of Solaris zone tendency and the peak are understood.
		Real Memory Size	The real memory size of Solaris zone tendency and the peak are understood.
Solaris Zone(Solaris 10) CPU(Contour)	H System group and host specification	CPU Usage Rate	The tendency and the peak of CPU utilization where the height of CPU utilization is expressed by the contour line can visually be caught. The use of a long series of data of about one month is required. Point CPU utilization becomes the unit of the processor set with 100% when the Solaris zone is in the processor set and it uses it.
Solaris Zone(Solaris 10) memory(Contour)	H System group and host specification	Memory Usage	The tendency and the peak of the memory percentage utilisation where the height of the memory percentage utilisation is expressed by the contour line can visually be caught. The use of a long series of data of about one month is required.

4.2.2.2 Network

4.2.2.2.1 Systemwalker Centric Manager (Network)

Report	Analysis method of setting Element and condition	Item	Description
Centric Manager traffic	H System group and host specification	Line utilization rate	Check deviations and peaks in the line utilization rate.
Centric Manager traffic	H System group and host specification	Number of octets	Check deviations and peaks in the number of octets.
Centric Manager packet	H System group and host specification	Number of packets	Check deviations 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

Report	Analysis method of setting Element and condition	Item	Description
Network Manager network traffic	H System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	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 System group, host and resource ID specification	RTT Ping	This item displays 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 in default. Please refer to the point of "4.1 Types of Categories" when you display it.

Report	Analysis method of setting Element and condition	Item	Description
TcpNetwork	H System group, host and resource ID specification	Number of TCP packets transferred	If application processing performance is poor 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 measures with reference to the graph.
		Resend rate, duplicated reception rate, packet loss rate	Take measures with reference to the graph.
		Network problem situation	Take measures with reference to the graph.

4.2.2.3 Storage

4.2.2.3.1 ETERNUS SF Storage Cruiser(SAN Storage)

Report	Analysis method of setting Element and condition	Item	Description
Storage CM CPU usage rate	H System group, host and resource ID specification	CM CPU Usage Rate	Check deviations 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 System group, host and resource ID specification	CM(ROE) CPU Usage Rate	Check deviations and peaks in the CM(Controller Module) CPU usage rate. There is a possibility that a large amount of accesses to the encryption volume and the accesses to RAID6 are generated when the ROE Usage Rate is high. There is a possibility that a large amount of accesses to the volume not encrypted and the accesses of the RAID Level to RAIDGroup except RAID6 are generated when the ROE Usage Rate is low, and CM CPU Usage Rate is high.
Storage disk busy	H System group, host and resource ID specification	Disk Busy	Check deviations and peaks in the disk usage rate. When the disk usage rate is 80% or greater, highload 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 System group, host and resource ID specification	Throughput	Check deviations and peaks in the throughput.
Storage IOPS	H System group, host and resource ID specification	IOPS	Check deviations and peaks in the IOPS.
Storage response time	H System group, host and resource ID specification	Response time	Check deviations and peaks in the response time.
Storage cache hit rate	H System group, host and resource ID specification	Cache Hits	Check deviations and peaks in the cache hit rate.

4.2.2.3.2 ETERNUS SF Storage Cruiser(NAS)

Report	Analysis method of setting Element and condition	Item	Description
NAS CPU usage rate	H System group, host and resource ID specification	NAS CPU usage rate	Used to grasp CPU usage rate bias and peaks.
NAS NFS OPS	H System group, host and resource ID specification	NAS NFS OPS	Used to grasp NFS handling performance bias and peaks.
NAS CIFS OPS	H System group, host and resource ID specification	NAS CIFS OPS	Used to grasp CIFS handling performance bias and peaks.
NAS HTTP OPS	H System group, host and resource ID specification	NAS HTTP OPS	Used to grasp HTTP handling performance bias and peaks.
NAS network traffic	H System group, host and resource ID specification	Amount of network input data Amount of network output data	Used to grasp network traffic bias and peaks.
NAS Amount of DISK R/W data	H System group, host and resource ID specification	Amount of reading data from disk Amount of writing data to disk	Used to grasp disk read and write data amount bias and peaks.
NAS Amount of tape R/W data	H System group, host and resource ID specification	Amount of reading data from tape Amount of writing data to tape	Used to grasp tape read and write data amount bias and peaks.

4.2.2.4 OS

4.2.2.4.1 Windows

Report	Analysis method of setting Element and condition	Item	Description
Windows server	G System group specification	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	The status of the resource of the server registered in the system group is confirmed.
Windows CPU	H System group and host specification	CPU Usage Rate(User, System)	Check deviations 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 measures such as increasing or upgrading the CPUs, adjusting the application execution schedule, or relocating some applications to a different server. [Attention Level] CPU usage rate > 80 %
Windows CPU	H System group and host specification	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. [Attention Level] CPU queue length > 2
Windows physical disk	H System group and host specification	Disk Busy	It can be used to ascertain the load deviation and load peaks of each disk. If the physical disk busy rate exceeds 60 % intermittently, the disk load is causing a bottleneck and performance problems are either occurring now or may occur in the future. [Attention Level] Physical disk busy >= 60 %
Windows physical disk	H System group and host specification	Disk Queues	It can be used to ascertain the deviation 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 measures such as distributing the disk load or adding disks. [Attention Level] Number of physical disk queue requests >= 2
Windows disk space	H System group and host specification	Disk Usage Rate	It can be used to ascertain the usage deviation and load peaks of each disk.
Windows memory	H System group and host specification	Free Memory	It can be used to ascertain the deviation and peaks of available memory capacity. 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. [Attention Level] Available memory capacity < 4 MB
Windows memory	H System group and host specification	Page ins/Page outs	Take measures with reference to the graph.
Windows process	H System group and host specification	CPU Time	This graph makes it possible to identify processes that consume much CPU time.
		Working set Size	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	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 System group and host specification	CPU Usage Rate	The rise and fall of the CPU usage rate is represented by contour lines. These enable the user to visually grasp peaks and deviations in the usage rate. This analysis is premised on long-term data usage of approximately one month.
Windows physical disk(Countour)	H System group and host specification	Physical Disk Busy	The rise and fall of the physical disk busy rate is represented by contour lines. These enable the user to visually grasp peaks and deviations in the physical disk busy rate. This analysis is premised on long-term data usage of approximately one month.
Windows memory(Contour)	H System group and host specification	Free Memory	The rise and fall of available memory capacity is represented by contour lines. These enable the user to visually grasp peaks and deviations in memory usage. This analysis is premised on long-term data usage of approximately one month.

4.2.2.4.2 UNIX

Report	Analysis method of setting Element and condition	Item	Description
UNIX server	G System group specification	CPU Usage Rate Free Memory Physical Disk Busy Disk Usage Rate	The status of the resource of the server registered in the system group is confirmed.
UNIX CPU	H System group and host specification	CPU Usage Rate(User, System)	Check deviations 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 measures such as increasing or upgrading the CPUs, adjusting the application execution schedule, or relocating some applications to a different server. [Attention Level] CPU usage rate > 80 %
UNIX CPU	H System group and host specification	CPU Queue Length	If CPU queue length > 10 or if CPU execution wait time rate > 90% and (the number of queue requests) / (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. [Attention Level] CPU execution wait time rate > 90% and the number of queue requests < 1 Note This information is displayed when a Solaris server is analysis and reported.
UNIX physical disk	H System group and host specification	Average Disk Busy	Check deviations and peaks in workload per disk. If the average disk busy exceeds 60%, the access waiting time will be easy to notice, and it is said that the average access time including waiting time be doubled or tripled if the average disk busy exceeds 80%. If the average disk busy consistently exceeds 80%, a bottleneck may be degrading performance, or such a problem may be about to occur. The bottleneck by disk busy is determined by the following items. It is necessary to consider taking measures such as increasing disks or moving files to disks of which the workload is low (review the data layout). Physical disk busy Service time in disk access Number of disk waiting request [Attention Level] Physical disk busy >= 60% and Service time >= 30(ms) and Number of disk waiting request >= 2
		Service Times	Service time refers to the average time that is required to process a single I/O request completely. It includes the time to wait for the completion of processing for existing requests in an I/O queue. [Attention Level] Service time >= 30(ms)
		Physical Disk Waiting Request Number	Check deviations and peaks in I/O request per disk. If the service time of disk access >= 30(ms) and the number of waiting request is a lot, access requests to the disk may concentrate. It is necessary to review the data layout. If the service time of disk access >= 30(ms) and the number of waiting request is not a lot, a disk device which is workload is high may be connected to the same controller. [Attention Level] Service time >= 30(ms) and Disk waiting request number < 2
UNIX disk space	H System group and host specification	Disk Usage Rate	It can be used to ascertain the usage deviation and load peaks of each disk.
UNIX memory	H System group and host specification	Free Memory	It can be used to ascertain the deviation and peaks of available memory capacity. If the amount of available memory intermittently approaches the value of the kernel parameter "lotsfree" (unit: KB), insufficient memory may be causing a bottleneck and performance problems are either occurring now or they may occur in the future. [Attention Level] Available memory capacity < lotsfree
UNIX memory	H System group and host specification	Swap ins/Swap outs	When only swap-in operations are occurring A temporary shortage of memory has caused swapped-out processes to be swapped in. This does not indicate a problem. When only swap-out operations are occurring A temporary shortage of memory has caused an unnecessary process to be swapped out. This does not indicate a problem. This kind of problem occurs when a large number of processes are created temporarily. When both swap-in and swap-out operations occur In current versions of UNIX, it is normal for no swapping to occur. If both swap-in and swap-out operations occur, it is likely that the system is suffering from a serious memory shortage and it will be necessary to install more memory. Note This information is displayed when a Solaris server is analyzed and reported.
UNIX process	H System group and host specification	CPU Time	This graph makes it possible to identify processes that consume a large amount of CPU time.
UNIX process	H System group and host specification	Memory Usage	In computers that are suffering from insufficient memory, this graph can be used to identify which processes are causing the problem. Note The graph of a memory use rate according to the process top 10 is not displayed in Linux.
UNIX CPU(Contour)	H System group and host specification	CPU Usage Rate	The rise and fall of the CPU usage rate is represented by contour lines. These enable the user to visually grasp peaks and deviations in the usage rate. This analysis is premised on long-term data usage of approximately one month.
UNIX physical disk(Contour)	H System group and host specification	Physical Disk Busy	The rise and fall of the physical disk busy rate is represented by contour lines. These enable the user to visually grasp peaks and deviations in the physical disk busy rate. This analysis is premised on long-term data usage of approximately one month.
UNIX memory(Contour)	H System group and host specification	Free Memory	The rise and fall of available memory capacity is represented by contour lines. These enable the user to visually grasp peaks and deviations in memory usage. This analysis is premised on long-term data usage of approximately one month.

4.2.2.4.3 OS common

Report	Analysis method of setting Element and condition	Item	Description
Disk space	G System group specification	Disk Usage Rate Disk Availability	The status of the disk of the server registered in the system group is confirmed.

Report

Analysis method of setting Element and condition

Item

Description

Disk space

System group specification

Disk Usage Rate
Disk Availability

The status of the disk of the server registered in the system group is confirmed.

4.2.2.5 Web

4.2.2.5.1 Web transaction

Report	Analysis method of setting Element and condition	Item	Description
Web transaction	G System group specification	Request count Traffic Error count	Check deviations and peaks in the number of requests in each service and the time required by requests. If the number of requests in each service or the time required by requests exceeds the expected value, the user can consider measures such as adding another Web server.
Web transaction request	H System group, host and resource ID specification	Web transaction request(Request Count,Time Taken)	Check deviations and peaks in the volume of traffic in each service. If the volume of traffic exceeds the expected value, the user can consider measures such as adding another Web server.
Web transaction hitserver	H System group, host and resource ID specification	Hit Server Count	Check how often server hits are occurring in each service.
Web transaction hitclient	H System group, host and resource ID specification	Hit Client Count	Check how often client hits are occurring in each service.
Web transaction hitremote	H System group, host and resource ID specification	Hit Remote Count	Check how often remote hits are occurring in each service.
Web transaction traffic	H System group, host and resource ID specification	Traffic	Check deviations and peaks in the volume of traffic in each service. If the volume of traffic exceeds the expected value, the user can consider measures such as adding another Web server.
Web transaction error	H System group, host and resource ID specification	Error count	Check how often errors are occurring in each service.

4.2.2.6 Application

4.2.2.6.1 Interstage Application Server(IJServer Cluster)

Report	Analysis method of setting Element and condition	Item	Description
Interstage IJServer Cluster	G System group specification	Current Heap Size Current Perm Garbage Collection	The heap of Java VM of the server registered in the system group, the quantity consumed in the Perm area, and the generation frequency of the garbage collection are confirmed.
Interstage IJServer Cluster JVM	H System group, host and resource ID specification	Heap Size(avg/max/min)	Check deviations and peaks in the heap information.
		Perm Size(avg/max/min)	Check deviations and peaks in the Perm area information.
		Garbage collections	Check deviations and peaks in the frequency of garbage collection.
Interstage IJServer Cluster JTA	H System group, host and resource ID specification	Transaction(avg/max/min)	Check deviations and peaks in transaction counts.
Interstage IJServer Cluster JDBC	H System group, host and resource ID specification	Connection Pool(avg/max/min)	Information about JDBC connections that are pooled by Interstage. Check deviations and peaks in connection counts.
Interstage IJServer Cluster JDBC	H System group, host and resource ID specification	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. Check deviations and peaks in the frequency of connection waiting and the number of threads that are waiting for a connection.
Interstage IJServer Cluster THREADPOOL	H System group, host and resource ID specification	Work items in queue	Information about the number of work items in the queue. Check the number of work items in the queue.
		Total busy threads	Information about the total number of busy threads in the thread pool. Check the number of busy threads in the thread pool.
		Average completion time of work items	Statistical information about the average completion time of work items. Check the average completion time of work items.
		Total usable threads	Information about the total number of usable threads in the thread pool. Check the number of usable threads in the thread pool.

4.2.2.6.2 Interstage Application Server(Work Unit)

Report	Analysis method of setting Element and condition	Item	Description
Interstage(EJB)	G System group specification	EJB Application Processing Time	The processing time of the EJB application of the server registered in the system group is confirmed.
Interstage(TD)	G System group specification	Object Processing Time	The processing time of the transaction application of the server registered in the system group is confirmed.
Interstage(CORBA)	G System group specification	Implementation Repository ID Processing Time	The processing time of the CORBA application of the server registered in the system group is confirmed.
Interstage(IJServer)	G System group specification	Current Heap Size Current Perm	The heap of JavaVM of the server registered in the system group and the quantity consumed in the Perm area are confirmed.
Interstage EJB application	H System group, host and resource ID specification	EJB Application Processing Time(avg/max/min)	The maximum, minimum and mean processing times for EJB applications. When the maximum processing time for an entire period (one day) is long and the mean 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 mean processing times within a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum processing time is long but the mean 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 mean times from when a client receives a request until a method commences processing. When the maximum, minimum and mean wait times during a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum wait time is long but the mean 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 mean 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 measures 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. If the performance of a server application is not sufficient to handle the number of requests from a client, take measures to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. Measure the performance information of other server applications as well to confirm the load status. When the number of process wait requests is large but the mean 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 mean 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 becomes larger than the number of connected clients, the "remove" method may not have been issued to the "create" method. Review the client applications.
Interstage CORBA application	H System group, host and resource ID specification	Processing Time(avg/max/min)	The maximum, minimum and mean processing times for CORBA applications. When the maximum processing time for an entire period (one day) is long and the mean processing time is close to the maximum processing time The following causes are possible: There is a performance-related problem with theserver application. The load on the system is high. When the maximum, minimum and mean processing times within a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum processing time is long but the mean 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 mean times from when a client receives a request until an operation commences processing. When the maximum, minimum and mean wait times during a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum wait time is long but the mean 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 mean 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 measures 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 measures to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. Measure the performance information of other server applications as well to confirm the load status. When the number of process wait requests is large but the mean 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 System group, host and resource ID specification	Object Processing Time(avg/max/min)	The maximum, minimum and mean processing times for transaction applications. When the maximum processing time for an entire period (one day) is long and the mean 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 mean processing times within a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum processing time is long but the mean 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 mean times from when a client receives a request until an object commences processing. When the maximum, minimum and mean wait times during a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum wait time is long but the mean 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 mean 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 measures 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 measures to raise the performance of server applications, such as increasing the number of concurrent processes in the Work Unit definition. Measure the performance information of other server applications as well to confirm the load status.
Interstage IJServer JVM	H System group, host and resource ID specification	Heap Size(avg/max/min)	Check deviations and peaks in the heap information.
		Perm Size(avg/max/min)	Check deviations and peaks in the Perm area information.
		Garbage collections(avg/max/min)	Check deviations and peaks in the frequency of garbage collection.
Interstage IJServer JTA	H System group, host and resource ID specification	Transaction(avg/max/min)	Displays information about transactions used by applications. Check deviations and peaks in transaction counts.
Interstage IJServer JDBC	H System group, host and resource ID specification	Connection Pool(avg/max/min)	Information about JDBC connections that are pooled by Interstage. Check deviations 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. Check deviations 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. Check deviations and peaks in the number of established connections.
		Acquisition of Connection from Application(avg/max/min)	Information about connections used by applications. Check deviations and peaks in the number of allocated connections, etc.
Interstate IJSserver SERVLET CONTAINER	H System group, host and resource ID specification	Number sum total of Threads(avg/max/min)	Information about the total number of threads. Check deviations and peaks in thread counts.
Interstate IJSserver SERVLET CONTAINER	H System group, host and resource ID specification	Number of Threads currently in progress(avg/max/min)	Information about the number of threads currently being processed. Check the number of threads currently being processed.
Interstate IJSserver SERVLET WEBMODULE	H System group, host and resource ID specification	Session(avg/max/min)	Check the number of valid sessions.
Interstate IJSserver EVENT SERVICE	H System group, host and resource ID specification	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

Report	Analysis method of setting Element and condition	Item	Description
WebLogic Server	G System group specification	Current heap size Garbage collection	The generation frequency of JavaVM heap information and the garbage collection of the server registered in the system group is confirmed.

Report

Analysis method of setting Element and condition

Item

Description

WebLogic Server

System group specification

Current heap size
Garbage collection

The generation frequency of JavaVM heap information and the garbage collection of the server registered in the system group is confirmed.

4.2.2.6.4 Microsoft .NET

Report	Analysis method of setting Element and condition	Item	Description
MS-.NET	G System group specification	Requests Count Wait Queues	Requests Count and Wait Queues of the server registered in the system group are confirmed.
MS-.NET ASP.NET	H System group, host and resource ID specification	Waiting Demands for Processing Count	Allows the number of requests waiting to be processed for MS-SQL to be ascertained. When the maximum processing time for an entire period (one day) is long and the mean 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 mean processing times within a specific period are long The load on the system may be high during a specific time period. Measure the performance information of other server applications as well to confirm the load status. When the maximum processing time is long but the mean 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	Allows Application Reboot Count to be ascertained. Take measures with reference to the graph.
		Worker Process Reboot Count	Allows Worker Process Reboot Count to be ascertained. Take measures with reference to the graph.
MS-.NET Applications	H System group, host and resource ID specification	Transaction Count	The number of MS-.NET transactions can be checked. Take measures with reference to the graph.
		Number of Execution Requests	The number of MS-.NET execution requests can be checked. Take measures with reference to the graph.
		Sessions Count	The number of active MS-.NET sessions can be checked. Take measures with reference to the graph.
		Error Count	The total number of MS-.NET errors can be checked. Take measures with reference to the graph.
MS-.NET Remote procedure	H System group, host and resource ID specification	Total Number of Remote Procedure Calls	Allows the total number of remote procedure calls for MS-SQL to be ascertained. Take measures with reference to the graph.

4.2.2.6.5 SAP NetWeaver

Report	Analysis method of setting Element and condition	Item	Description
SAP	G System group specification	Dialog Response Time Enqueue Enqueue Requests/Queue Length Background Utilization Execution Waiting RFC Total Calls	Dialog Response Time of SAP of the server registered in the system group, Enqueue Enqueue Requests/Queue Length, Background Utilization, and Execution Waiting RFC Total Calls are confirmed.
SAP Enqueue(Request)	H System group, host and resource ID specification	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 the time that parallel processes spend waiting to access lock table.
		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 System group, host and resource ID specification	Queue Length	Track and compare trends and peaks in the queue length for enqueue server monitoring objects.
		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 System group, host and resource ID specification	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 frontend 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.
		Dialog steps	Track and compare trends and peaks in the number of Dialog steps.
SAP Spool	H System group, host and resource ID specification	Load Factor	Track and compare trends and peaks in the load for spool work processes.
SAP Spool	H System group, host and resource ID specification	Errors	Track and compare trends and peaks in the number of errors that occur with spool work processes.
SAP Background	H System group, host and resource ID specification	Load Factor	Track and compare trends and peaks in the load rate for background work processes.
SAP Background	H System group, host and resource ID specification	Errors	Track and compare trends and peaks in the number of errors that occur with background work processes.
SAP Update	H System group, host and resource ID specification	Response Time	Track and compare trends and peaks in the response times for each Dialog step for SAP Update Tasks (V1).
		Dispatcher wait time	Track and compare trends and peaks in the dispatcher standby times in dispatcher queues for SAP Update Tasks (V1).
		Load factor(V1)	Track and compare trends and peaks in the load rate for update task work processes for SAP Update Tasks (V1).
		Errors(V1)	Track and compare trends and peaks in the number of errors that have occurred for Update 1 work process.
		Load factor(V2)	Track and compare trends and peaks in the load rate for Update 2 task work processes for SAP Update Tasks (V2).
		Errors(V2)	Track and compare trends and peaks in the number of errors that have occurred for Update 2 work process.
SAP Roll Paging	H System group, host and resource ID specification	Paging area utilization	Track and compare trends and peaks in the paging area usage rate.
SAP Roll Paging	H System group, host and resource ID specification	Roll area utilization	Track and compare trends and peaks in the roll area usage rate.
SAP Memory	H System group, host and resource ID specification	Extended Memory Utilization	Track and compare trends and peaks in the usage rate for extended memory.
		Heap Memory Utilization	Track and compare trends and peaks in the usage rate for heap memory.
		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 System group, host and resource ID specification	Buffer Utilization	Track and compare trends and peaks in the buffer usage rate.

4.2.2.6.6 Workload

This category is not displayed in default. Please refer to the point of "4.1 Types of Categories" when you display it.

Report	Analysis method of setting Element and condition	Item	Description
Workload	H System group, host and resource ID specification	Allocated CPU Used CPU	Allows the amount of allocated CPU resources and the amount of used CPU resources for a single resource module to be ascertained and compared. Take measures with reference to the graph.

Report

Analysis method of setting Element and condition

Item

Description

Workload

System group, host and resource ID specification

Allocated CPU
Used CPU

Allows the amount of allocated CPU resources and the amount of used CPU resources for a single resource module to be ascertained and compared.

Take measures with reference to the graph.

4.2.2.7 Database

4.2.2.7.1 Symfoware Server

Report	Analysis method of setting Element and condition	Item	Description
Symfoware	G System group specification	Buffer hit ratio Buffer Dry up SQL executions Deadlocks	Buffer cache hit ratio, Deadlocks Count, and SQL executions etc. of Symfoware of the server registered in the system group are confirmed.
Symfoware shared buffer	H System group, host and resource ID specification	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 System group, host and resource ID specification	Buffer Dry Up	The number of times that no unused buffers were available. Fine-tune the shared buffer.
Symfoware log area	H System group, host and resource ID specification	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 System group, host and resource ID specification	DB Space I/O	The number of I/O operations for each database space during a specified period of time. Take measures with reference to the graph.
Symfoware database space usage rate	H System group, host and resource ID specification	Database Space Usage Rate	It can be used to ascertain the usage deviation and load peaks of each database space.

4.2.2.7.2 Oracle Database

Report	Analysis method of setting Element and condition	Item	Description
Oracle	G System group specification	Buffer cache hit ratio Deadlocks	Buffer cache hit ratio and Deadlocks Count etc. of Oracle of the server registered in the system group are confirmed.
Oracle SGA	H System group, host and resource ID specification	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. Note: - "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. If Oracle8 or earlier is being used and latch waiting occurs to the REDO log buffer cache, decrease the value of the initialization parameter "LOG_SMALL_ENTRY_MAX_SIZE". If the above tuning is not effective, increase the value of the initialization parameter "LOG_SIMULTANEOUS_COPIES".
		Library Cache Hit Ratio	The library cache stores the SQL statements that have been analyzed 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 System group, host and resource ID specification	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". Note: - "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 System group, host and resource ID specification	Amount of free table space area	Displays the minimum value for the available table space capacity. Expand or add data files.
Oracle disk I/O	H System group, host and resource ID specification	Volume of database I/O	Displays the volume of database I/O. Take measures with reference to the graph.
Oracle resource conflict	H System group, host and resource ID specification	Ratio of zero rollback segment wait time	Ideally, rollback segment header waiting should be kept to zero or a very small amount. If rollback segments are being used, more should be added as the number is insufficient. Note: If the UNDO table space is being used in Oracle9i or later, tuning will take place automatically.
Oracle table space usage rate	H System group, host and resource ID specification	Oracle tablespace	It can be used to ascertain the usage deviation and load peaks of each tablespace.

4.2.2.7.3 Microsoft SQL Server

Report	Analysis method of setting Element and condition	Item	Description
MS-SQL	G System group specification	Buffer cache hit ratio Deadlocks Count Transaction Count	Buffer cache hit ratio and Deadlocks Count etc. of SQL Server of the server registered in the system group are confirmed.
MS-SQL ACCESS METHOD	H System group, host and resource ID specification	Full Scan Count Index Count	Allows the access method for MS-SQL to be ascertained and compared. Take measures with reference to the graph.
MS-SQL Server BUFFER	H System group, host and resource ID specification	Buffer Cache Hit Count	Enables the number of MS-SQL buffer cache hits to be determined. Take measures with reference to the graph.
MS-SQL Server BUFFER	H System group, host and resource ID specification	Access Count	Enables the number of MS-SQL accesses to be determined. Take measures with reference to the graph.
MS-SQL Server CMGR	H System group, host and resource ID specification	Cache hit rate	Enables the MS-SQL cache hit rate to be determined. Take measures with reference to the graph.
MS-SQL Server CMGR	H System group, host and resource ID specification	Hits Count	Enables the number of MS-SQL hits to be determined. Take measures with reference to the graph.
MS-SQL Server DATABASES	H System group, host and resource ID specification	Transaction Count	Enables the number of MSSQL transactions to be determined. Take measures with reference to the graph.
		Active Transaction Count	Enables the number of MSSQL active transactions to be determined. Take measures with reference to the graph.
		Log Area Ratio	Enables the MS-SQL log area ratio to be determined. Take measures with reference to the graph.
MS-SQL Server GENERALSTATISTICS	H System group, host and resource ID specification	Number of Connected Users	Allows the number of connected users for MS-SQL to be ascertained. Take measures with reference to the graph.
MS-SQL Server LOCKS	H System group, host and resource ID specification	Deadlocks Count	Allows the number of deadlocks for MS-SQL to be ascertained. Take measures with reference to the graph.
MS-SQL Server LOCKS	H System group, host and resource ID specification	Number of standby waiting lock requests	The number of MS-SQL standby waiting lock requests can be understood. Take measures with reference to the graph.
MS-SQL Server MEMORY	H System group, host and resource ID specification	Total Amount of Memory	Allows the memory capacity for MS-SQL to be ascertained. Take measures with reference to the graph.
MS-SQL Server STATISTICS	H System group, host and resource ID specification	Number of SQLS Batch Requests	Allows the number of requests for MS-SQL to be ascertained. Take measures with reference to the graph.

4.2.2.8 Job

4.2.2.8.1 Systemwalker Operation Manager

Report	Analysis method of setting Element and condition	Item	Description
Operation Manager	G System group specification	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	The job multiplicity and the number etc. of Executing waiting jobs of Systemwalker Operation Manager of the server registered in the system group are confirmed.
Operation Manager subsystem	H System group, host and resource ID specification	Job multiplicity of each Subsystem(Job multiplicity,Network/Distributed execution job multiplicity)	Check deviations and peaks in the job concurrency of different subsystems. 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	Check deviations 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	Check deviations 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 measures to reduce the level of job concurrency.
		Number of jobs that have exceeded the predicted time of each Subsystem	Check deviations 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 measures to reduce the level of job concurrency.
		Number of completed jobs by subsystem	Check deviations 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	Check the number of error jobs in different subsystems.
Operation Manager queue	H System group, host and resource ID specification	Job multiplicity of each Queue (Job multiplicity,Network/Distributed execution job multiplicity)	Check deviations and peaks in the job concurrency of different queues. 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	Check deviations and peaks in the job net concurrency of different queues.
		Number of execution waiting jobs of each Queue	Check deviations 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	Check deviations 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 measures to reduce the level of job concurrency.
		Number of jobs that have exceeded the predicted time of each Queue	Check deviations 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 measures to reduce the level of job concurrency.
Operation Manager project	H System group, host and resource ID specification	Job multiplicity of each Project	Check deviations and peaks in the job concurrency 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	Check deviations and peaks in the job net concurrency of different projects.
		Number of execution waiting jobs of each Project	Check deviations 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	Check deviations 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 measures to reduce the level of job concurrency.
		Number of jobs that have exceeded the predicted time of each Project	Check deviations 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 measures to reduce the level of job concurrency.
		Number of completed jobs by project	Check deviations 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	Check the number of error jobs in different projects.

Report	Analysis method of setting Element and condition	Item	Description
ISI Sequence	G System group specification	Number of transactions	Sequence information on ISI of the server registered in the system group is confirmed.
ISI Queue	G System group specification	Number of retention	Queue information on ISI of the server registered in the system group is confirmed.
ISI Sequence	H System group, host and resource ID specification	Number of transactions	Bias of the processing number of each sequences and the peak are understood.
ISI Queue	H System group, host and resource ID specification	Number of retention	Bias of the number of stays and the peak of each queue are understood.

Report	Analysis method of setting Element and condition	Item	Description
HTTP service	G For service operational information only	HTTP Operating rate	The situation of the HTTP service of the watch Element registered in the system group is confirmed.
SMTP service	G For service operational information only	SMTP Operating rate	The situation of the SMTP service of the watch Element registered in the system group is confirmed.
DNS service	G For service operational information only	DNS Operating rate	The situation of the DNS service of the watch Element registered in the system group is confirmed.
PORT service	G For service operational information only	PORT Operating rate	The situation of PORT of the watch Element registered in the system group is confirmed.

Report	Analysis method of setting Element and condition	Item	Description
Time-series	H Detailed specification	-	The following are included in Performance analysis subordinate's category. Displays specified field values as chronological graphs and tables.
Summary data time series display	H Detailed specification	-	Display the summary data as a time-series graph or table.
Correlation display	H For correlation/composition only	-	Displays two specified field values as correlation graphs and regression line graphs.
Contour display	H For contour display only	-	Displays specified field values as contour graphs. This assumes that data will be used over a long period of time(about one month)
Comparison display of the past	H For comparison display of the past only	-	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 For transition comparison display according to day display only	-	Displays a graph that compares data trends for the specified date and time period.
Composite display	H For correlation/composition only	-	Displays a graph that allows two different items (such as response times and CPU usage) to be compared side-by-side.