1.10 Description of compound report settings
The table below describes the items in the compound report mentioned in 1.4.4 Monitoring the memory resource and 1.9.3 Monitoring the CPU resource. For details about how to create a compound report, see the chapter that explains the creation of reports for operation analysis in the JP1/Performance Management User's Guide.
- Points
-
-
A compound report is created for each monitored physical server.
-
If you create a compound report without specifying any field display conditions, all virtual machines running on the physical server are displayed. To monitor the information of each virtual machine separately, specify a virtual machine name as a field display condition.
Table 1‒1: Compound report setting details Compound report name
Monitoring template report name
Field display condition
Compound bookmark and group setting
Group
Graph type
Group name
Max
Min
Monitoring of virtual machine CPU allocation upper limit
VM CPU Allocation Value
Change the asterisks (*) to the target virtual machine name.
Group 1
Line
VM CPU Allocation Value [MHz]
CPU resource (PI.Clocks value)
0
VM CPU Used
Change the asterisks (*) to the target virtual machine name.
Group 2
Stacked area
CPU [MHz]
CPU resource (PI.Clocks value)
0
Monitoring of virtual machine memory allocation upper limit
VM Memory Allocation Value
Change the asterisks (*) to the target virtual machine name.
Group 1
Line
VM Memory Allocation Value [MB]
Memory size (PI_VMI.Size value)
0
VM Swap Used
Change the asterisks (*) to the target virtual machine name.
Group 2
Stacked area
Used [MB]
Memory size (PI_VMI.Size value)
0
Monitoring of working set size of all virtual machines
Host Memory Size
--
Group 1
Line
Memory Size [MB]
Memory size (PI_VMI.Size value)
0
VM Working Size - Total
--
Group 2
Stacked area
Working Size [MB]
Memory size (PI_VMI.Size value)
0
- Legend:
-
--: Do not specify.
Max: Maximum value
Min: Minimum value
-