It explains each Category about the report used by the Planning.
Note, forecast and simulation results displayed in each report are calculated in the fujitsu's own way based on past performance. The results are only as a guide under your computing environment. It is no guarantee of operation under the real environment. Please be forewarned.
Report | Analysis method of setting Element and condition | Item | Description |
|---|---|---|---|
Server distribution by rsc. usage cond.(Summary) | G |
| The resource of a physical server of the entire System has been effectively used or the Confirmation of the resource situation can be done. Only information after the change is displayed about the server of the correspondence when there is a change in the resource of the memory increase etc. in the specified period.
Point
|
List of rsc. usage cond. (Detail) | G |
| The Confirmation of the resource status and the amount of the installing resource (CPU and memory) of a physical server of the entire System can be done.
In the installed CPU 1 core, displayed CPU performance (MHz) is performance data. Point
|
P2V simulation | - |
| The amount of the resource use when the selected server is consolidated in one virtual environment can be simulated. The combination of consolidated servers is considered when there is bias by the value too large, and time zone and day of the week through the period. When a permissible threshold is set, whether the value is greatly exceeded is confirmed. It is not possible to use it in a regular report. |
Note
Neither the above-mentioned nor the report type of the server observed with Agent or Agent for Agentless Monitoring before Systemwalker Service Quality Coordinator V13.5.0 are displayed.
Note
The report of this Category cannot be used for VMware ESX (ssh connection) because there is itemses that cannot be collected.
Report | Analysis method of setting Element and condition | Item | Description |
|---|---|---|---|
VMware rsc. usage cond.(List of host) | G |
| The resource status of the VMware virtual host registered in the System group is understood. A virtual host that there is becoming empty in the resource is detected as a virtual host who consolidates it. Displayed Total CPU performance (MHz) is a performance data of the total of all cores of installed CPU. |
VMware rsc. usage cond.(Virtual machine stack) | H |
| The virtual machine being arranged by a virtual host and the amount of the resource use are confirmed to a virtual host in the movement origin examined with "VMware rsc. usage cond.(List of host)" in the piling graph. The amount of the resource use of each virtual machine in the movement origin is confirmed, and which virtual machine is moved to which moving destination candidate's host is examined. |
VMware virtual machine relocation simulation | - |
| The amount of the resource use when the virtual machine examined as a movement origin is relocated in a virtual host who examines it as a moving destination is simulated. The result is good at the graph of the time series according to time zone and a day of the week at the Confirmation. It is not possible to use it in a regular report. |
Note
The report of this Category cannot be used for VMware ESX (ssh connection) because there is itemses that cannot be collected.
Report | Analysis method of setting Element and condition | Item | Description |
|---|---|---|---|
VMware rsc. usage cond.(List of virtual machine) | H |
| The resource status of the virtual machine on a virtual host who selects it is displayed by the list. It sorts by CPU utilization and the memory usage rate, the virtual machine that there is becoming empty in the resource is detected, and whether the resource allocation can be reduced to the virtual machine with low usage rate is examined. 100% of CPU utilization is one physical CPU. Therefore, it is likely to be displayed exceeding 100%. |
Note
The report of this Category cannot be used for VMware ESX (ssh connection) and VMware ESX 3.5 because there is itemses that cannot be collected.
Report | Analysis method of setting Element and condition | Item | Description |
|---|---|---|---|
VMware CPU tuning guidance | H |
| There is no problem in CPU status of the host and the virtual machine or the Confirmation can be done. It refers when the guidance is displayed. |
|
[Attention Level] CPU Usage Rate >= 90 % | ||
|
[Attention Level] Average CPU Usage Rate (1CPU) >= 90 % CPU Wait Rate >= 20 % | ||
VMware Memory(Host) tuning guidance | H |
| There is no problem in virtual host's memory usage or the Confirmation can be done. It refers when the guidance is displayed. |
|
| ||
|
| ||
|
| ||
VMware Memory(Virtual machine) tuning guidance | H |
| There is no problem in the memory usage of the virtual machine or the Confirmation can be done. It refers when the guidance is displayed. |
|
[Attention Level] Swap Occurrence Status(Reads) > 0 MB Swap Occurrence Status(Writes) > 0 MB | ||
|
[Attention Level] Swap Wait Rate > 0 % | ||
|
[Attention Level] Swap Amount > 0 MB/sec | ||
|
[Attention Level] Memory Compression Amount > 0 MB/sec | ||
|
[Attention Level] Memory Extension Amount > 0 MB/sec | ||
|
[Attention Level] Balloon Occurrence Amount > 0 MB/sec | ||
VMware Physical Disk | H |
| The throughput and the input-output frequency of virtual host's disk can be understood.
|
| The driver access performance of virtual host's disk is good at the Confirmation.
[Attention Level] Physical Disk Driver Access Performance(Reads) >=4 ms #Always Physical Disk Driver Access Performance(Writes) >=4 ms #Always | ||
| The kernel access performance of virtual host's disk is good at the Confirmation.
[Attention Level] Physical Disk Kernel Access Performance(Reads) >=20 ms #Always | ||
VMware Virtual Disk | H |
| The throughput and the input-output frequency of the disk of the virtual machine can be understood.
|
| The disk access performance of the virtual machine is good at the Confirmation. Please confirm the disk access performance. | ||
VMware Physical NIC | H |
| The Network percentage utilisation of physical NIC can be understood.
[Attention Level] Network Usage Rate >= Threshold #Always Line: Threshold |
| The packet drop rate of physical NIC can be understood.
[Attention Level] Packet Drop Rate(Transmission) > 0 % | ||
VMware Virtual NIC | H |
| The Confirmation of the amount of the Network use of virtual NIC can be done. |
| The Confirmation of the packet drop rate of virtual NIC can be done. Note The following are not displayed for VMware ESX 3.5, VMware ESX 4.0, and VMware ESX/ESXi 4.1.
|
Report | Analysis method of setting Element and condition | Item | Description |
|---|---|---|---|
Resource pool (CPU) (demand forecast) | H |
| VMware is CPU utilization of the manage resource pool, and the regression analysis is done from historical earnings, and how many resources is used is forecast. |
Resource pool (Memory) (demand forecast) | H |
| VMware is a memory percentage utilisation of the manage resource pool, and the regression analysis is done from historical earnings, and how many resources is used is forecast. |
Report | Analysis method of setting Element and condition | Item | Description |
|---|---|---|---|
VM pool (CPU) (demand forecast) | H |
| ServerView Resource Orchestrator does the regression analysis from historical earnings, and forecasts how many resources to use CPU utilization of manage VM pool. |
VM pool (Memory) (demand forecast) | H |
| ServerView Resource Orchestrator does the regression analysis from historical earnings, and forecasts how many resources to use the memory percentage utilisation of manage VM pool. |
Storage pool (demand forecast) | H |
| ServerView Resource Orchestrator is a percentage utilisation of the manage storage pool, and the regression analysis is done from historical earnings, and how many resources is used is forecast. |
Network pool (demand forecast) | H |
| ServerView Resource Orchestrator does the regression analysis from a past performance of the percentage utilisation of the manage Network pool, and how many resources is used is forecast. |
Server pool (demand forecast) | H |
| ServerView Resource Orchestrator is a percentage utilisation of the manage server pool, and the regression analysis is done from historical earnings, and how many resources is used is forecast. |
Address pool (demand forecast) | H |
| ServerView Resource Orchestrator is a percentage utilisation of the manage address pool, and the regression analysis is done from historical earnings, and how many resources is used is forecast. |
Report | Analysis method of setting Element and condition | Item | Description |
|---|---|---|---|
Request count (Future prediction) | H |
| Performance information on the Web transaction is forecast and the number of requests in the future is forecast from historical earnings by the regression analysis. Whether how much number of requests in the future increases compared with present can be understood. |
Response simulation (Request count) | - |
| Performance information on OS of the server that composes performance information and the system of the Web transaction can be simulated and the tendency in the response time of a day when the correlation is analyzed from historical earnings, and the number of requests (times the present number of requests how many) increases be simulated. The judgment can be done whether the improvement to be necessary at the response time. It is not possible to use it in a regular report. Point The response simulation analyzes the relationship with performance information (OS) on a past number of service requests and each server, simulates the response time, and the accuracy of the simulation improves if the time zone that becomes a noise without the request processing and the direct relationship like the batch processing etc. at nighttime is not included. The accuracy of the simulation can be confirmed by the reliability of "High","Medium"and"Low" displayed after the time of the response of the table. It is shown for "High" to be able to simulate the noise few, and to be able to simulate it by high accuracy. Moreover, it is not possible to simulate when performance information does not exist and the correlation with performance information on number of requests and OS is hardly obtained, and 'N/A' is displayed in the table. Reliability can be improved by lengthening the analysis period by setting the analytical condition, and setting to exclude the time zone that becomes a noise like the batch processing etc. at nighttime from the analysis Element. Please refer to "How to Change the Analysis/Planning Window" for the setting method of the analytical condition. |
Response simulation (Adding servers) | - |
| Performance information on OS of the server that composes performance information and the system of the Web transaction can be simulated and the tendency in the response time of a day when the correlation is analyzed from historical earnings, and the server is added be simulated. It is not possible to use it in a regular report. Point The accuracy at the simulated response time improves to the response simulation when an enough correlation is obtained because the number of requests and the correlation with performance information on OS are analyzed and simulated. Strength of the above-mentioned correlation is displayed in the table as reliability by three stageds ("High","Medium" and "Low"). An enough correlation is obtained, and it is shown to be able to simulate the response time comparatively by high accuracy for "High". It is shown that an enough correlation is not obtained, and the accuracy at the response time has decreased for "Medium" and "Low". There is a possibility that processing without the number of requests and the direct relationship like the batch etc. at the performance information necessary for calculation shortage, and nighttime influences as a noise. For this case, the setting of the analytical condition is changed as follows, and there is a possibility that reliability can be improved. - The analysis period is lengthened. - Time zone that the service such as nighttimes and holidays does not operate is set at time outside the service. Please refer to "4.3 How to Operate the Analysis/Planning Window" for the setting method of the analytical condition. Note It becomes impossible to analyze when performance information does not exist, and quite a lot of processing without the number of requests and the direct relationship operates, and the correlation with performance information on number of requests and OS is hardly obtained, and 'N/A' is displayed in the value of the table. In this case, it is possible to analyze by changing the setting of the analytical condition as follows and there is a possibility of becoming it. - The analysis period is lengthened. - Time zone that the service such as nighttimes and holidays does not operate is set at time outside the service. Please refer to "4.3 How to Operate the Analysis/Planning Window" for the setting method of the analytical condition. |
Report | Analysis method of setting Element and condition | Item | Description | |
|---|---|---|---|---|
Future forecast display | H | - | The value of the specified field is displayed in the regression line graph. | |
