Host CPU Status (PI_HCI)
- Organization of this page
Function
This record stores performance data on a physical server's physical CPU over a unit of time. This record is a multi-instance record.
In this record, you can collect performance data such as CPU usage for each CPU core. The CPU frequency can be divided into the part of the CPU that is being used and the part of the CPU that is not being used. The following figure shows an example of data that can be collected in this record.
|
|
![[Figure]](GRAPHICS/ZU050002.GIF)
- Note:
-
Information cannot be collected if an attempt to connect to the monitored physical server fails.
Default values and values that can be changed
|
Item |
Default value |
Can it be changed? |
|---|---|---|
|
Collection Interval |
300 |
Yes |
|
Collection Offset |
0 |
Yes |
|
Log |
No |
Yes |
|
LOGIF |
Blank |
Yes |
|
Over 10 Sec Collection Time |
No |
No |
ODBC key field
PI_HCI_CPU_ID
Lifetime
None
Record size
-
Fixed portion: 937 bytes
-
Variable portion: 473 bytes
Fields
|
PFM - View name (PFM - Manager name) |
Explanation |
Summary |
Grouping |
Format |
Delta |
When not collected |
Unsup-ported |
|---|---|---|---|---|---|---|---|
|
Record Type (INPUT_RECORD_TYPE) |
The record name. This is always "HCI". |
COPY |
COPY |
char (8) |
No |
-- |
Docker environment |
|
Record Time (RECORD_TIME) |
The time when the record was created. |
COPY |
COPY |
time_t |
No |
-- |
Docker environment |
|
Interval (INTERVAL) |
Interval during which the information is collected. [Units: seconds] |
COPY |
FIXED |
ulong |
No |
-- |
Docker environment |
|
VA DeviceID (VADEVICEID) |
The device ID of a monitored host. |
COPY |
COPY |
string(256) |
No |
-- |
Docker environment |
|
CPU ID (CPU_ID) |
ID of the physical CPU. |
COPY |
FIXED |
string (32) |
No |
No |
Docker environment |
|
CPU Name (CPU_NAME) |
Name of the physical CPU. |
COPY |
FIXED |
string (257) |
No |
Blank |
Docker environment |
|
Sampling Time (SAMPLING_TIME) |
Sampling time. The time when the performance information is collected on the host machine. Displayed in the following format: yyyy-mm-ddThh:mm[±hh:mm]#1 |
COPY |
FIXED |
string (32) |
No |
Blank |
Docker environment |
|
Clocks (CLOCKS) |
Clock frequency of the physical CPU. [Units: MHz] |
COPY |
ADD |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Podman environment: 0 |
Docker environment |
|
Used (USED)#2 |
Amount of used physical CPUs. The frequency used by the physical CPUs. [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Podman environment: 0 |
Docker environment |
|
Unused (UNUSED) |
Amount of unused physical CPUs. Unused frequency of the physical CPU. [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Podman environment: 0 |
Docker environment |
|
Used % (USED_PERCENT)#2 |
Usage rate of physical CPUs. Percentage of physical CPUs that are being used. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Podman environment: 0 |
Docker environment |
|
Unused % (UNUSED_PERCENT) |
Non-usage rate of physical CPUs. Percentage of physical CPUs that are not being used. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Podman environment: 0 |
Docker environment |
- #1
-
The value used in [±hh:mm] varies depending on the time zone of the monitored host. For example, if the monitored virtual environment is operating according to JST, +09:00 is displayed. If the monitored virtual environment is operating according to UTC, Z is displayed.
- #2
-
For Hyper-V, KVM, or Podman environment this field requires performance data to be collected at least twice.