Metering logs are output to CSV format files or XML format files.
Use the options of the Output metering log command to specify the format in which metering logs are to be output. Refer to "11.2 ctchg_getmeterlog (Output Metering Logs)" in the "Reference Guide (Command/XML) CE" for information on the Output metering log command.
This section explains each of the file formats.
CSV format files
The format of CSV format files is as follows:
The item ID is output with a one-byte hash (#) sign added to the first character of the first row.
Items are output with commas used as delimiters between each item.
String data is output enclosed by double quotation marks and numeric data is output as it is.
If an item is not output using string data, "" is output.
If an item is not output using numeric data, nothing is output. (A comma is output immediately after the previous item.)
For a Reserved item, "" is output.
The order of the items that are output to a CSV format file is as follows:
No. | Item ID | Item name | Data type |
|---|---|---|---|
1 | version | Version | Numeric |
2 | event_time | Time of event | String |
3 | Reserved | ||
4 | vsys_id | L-Platform ID | String |
5 | org_id | Tenant name | String |
6 | event | Event | String |
7 | resource_type | Configured resource type | String |
8 | status | Status | String |
9 | user_id | User account | String |
10 | server_id | L-Server ID | String |
11 | disk_id | Disk ID | String |
12 | software_id | Software ID | String |
13 | system_name | L-Platform name | String |
14 | server_name | L-Server name | String |
15 | disk_name | Disk name | String |
16 | template_id | Template ID | String |
17 | image_id | Snapshot ID | String |
18 | base_template_id | Used template ID | String |
19 | image_name | Image name | String |
20 | storage_pool | Storage pool name | String |
21 | disk_size | Disk size | Numeric |
22 | vm_pool | VM pool name | String |
23 | cpu_num | Number of CPUs | Numeric |
24 | cpu_perf | CPU performance | Numeric |
25 | memory_size | Memory capacity | Numeric |
26 | cpu_reserve | Reserve value of CPU performance | Numeric |
27 | memory_reserve | Reserve value of memory capacity | Numeric |
28 | server_template_name | L-Server template name | String |
29 | server_pool | Server pool name | String |
30 | cpu_input_num | Value entered for number of CPUs | Numeric |
31 | cpu_input_perf | Value entered for CPU frequency | Numeric |
32 | memory_input_size | Value entered for memory capacity | Numeric |
33 | template_name | Template name | String |
34 | ip_address | IP address | String |
35 | nic_no | NIC number | Numeric |
36 | network_resource_id | Network resource ID | String |
An output example of a CSV format file is shown below:
#version,event_time,Reserved,vsys_id,org_id,event,resource_type,status,user_id,server_id,disk_id,software_id,system_name,server_name,disk_name,template_id, image_id,base_template_id,image_name,storage_pool,disk_size,vm_pool,cpu_num,cpu_perf,memory_size,cpu_reserve,memory_reserve,server_template_name,server_pool,cpu_input_num,cpu_input_perf,memory_input_size,template_name,ip_address,nic_no,network_resource_id 2.0,"2011-07-02T00:00:00.000+0900","","vsysId001","orgId001","ADD","pserver","","userId001","serverId001","","","systemName001","ServerName001","","","","","imageName001","/StoragePool001",100,"",1,3,6,,,serverTemplateName001,serverPool001,2,5,8,,,, 2.0,"2011-08-08T10:20:10.000+0900","","","orgId001","PERIOD","template","","userId001","","","","","","","id001","","","","",,"",,,,,,,,,,,name001,,, 2.0,"2011-07-03T00:00:00.000+0900","","vsysId001","orgId001","PERIOD","snapshot","","userId001","serverId001","","","systemName001","","","","imageId0001","","","/StoragePool002",100,"",,,,,,,,,,,,,, 2.0,"2011-07-03T00:00:00.000+0900","","vsysId001","orgId001","PERIOD","snapshot","","userId001","serverId001","diskId001","","systemName001","","","","imageId0001","","","/StoragePool002",200,"",,,,,,,,,,,,,, 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","ip_addr","","userId001","serverId001","","","systemName001","","","","","","","",,"",,,,,,,,,,,,192.168.10.1,1,net-resource_123 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","software","","userId001","serverId001","","softwareId001","systemName001","","","","","","","",,"",,,,,,,,,,,,,, 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","vserver","RUNNING","userId001","serverId001","","","systemName001","serverName002","","","","","imageName002","/StoragePool002",100,"/VMPool001",2,30,60,10,50,serverType001,,,,,,,, 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","vdisk","","userId001","serverId001","diskId001","","systemName001","","diskName001","","","","","/StoragePool002",200,"",,,,,,,,,,,,,, 2.0,"2011-08-08T10:20:10.000+0900","","vsysId001","orgId001","PERIOD","vsys","","userId001","","","","systemName001","","","","","baseTemplateId001","","",,"",,,,,,,,,,,,,,
XML format files
The format of XML format files is as follows:
<?xml version="1.0" encoding="UTF-8"?> <meterlog> <entry><Item ID>Value</Item ID>...</entry> <entry><Item ID>Value</Item ID>...</entry> ... </meterlog>
The first row of the CSV format corresponds to the <entry> element.
The first column of the CSV format corresponds to the <Item ID> element.
If an item is not output, the <Item ID> tag itself is not output.
An output example of an XML format file is shown below:
<?xml version="1.0" encoding="UTF-8"?>
<meterlog>
<entry>
<version>2.0</version>
<event_time>2011-07-02T00:00:00.000+0900</event_time>
<vsys_id>vsysId001</vsys_id>
<org_id>orgId001</org_id>
<event>ADD</event>
<resource_type>pserver</resource_type>
<user_id>userId001</user_id>
<server_id>serverId001</server_id>
<system_name>systemName001</system_name>
<server_name>serverName001</server_name>
<image_name>image001</image_name>
<storage_pool>storagePool001</storage_pool>
<disk_size>1</disk_size>
<cpu_num>1</cpu_num>
<cpu_perf>3</cpu_perf>
<memory_size>6</memory_size>
<server_template_name>serverTemplateName001</server_template_name>
<server_pool>serverPool001</server_pool>
<cpu_input_num>2</cpu_input_num>
<cpu_input_perf>5</cpu_input_perf>
<memory_input_size>8</memory_input_size>
</entry>
<entry>
...
</entry>
...
</meterlog>Point
If a change of tenant has been performed for an L-Platform, an event log with CHANGE as the event will be output.
If snapshot restore has been performed, an event log with CHANGE as the event will be output even if there was no change.
At execution of the Import L-Server command of the L-Platform management function, the following event log will be output:
If a stopped L-Server has been imported
Event log with ADD as the event
If an active L-Server has been imported
Event log with ADD and START as the events
Note
An event indicating a stop of an L-Server (STOP) occurs for a stop or a forced stop of an L-Server. The forced stop of an L-Server can be performed even if the L-Server has a stopped status (STOPPED). Therefore, take into account that even if an L-Server has a stopped status, an event indicating a stop of the L-Server (STOP) may exist.
When starting virtual L-Servers using RHEL-KVM as server virtualization software, the amount of memory used by L-Servers is set to the upper limit first, and then it is reduced to the value specified to L-Servers by the RHEL-KVM management application. Therefore metering logs will be output in the following order if an RHEL-KVM L-Server is started.
L-Server starting (START)
L-Server changing (CHANGE) : Memory capacity = The upper limit
L-Server changing (CHANGE) : The upper limit > Memory capacity > The value specified to the L-Server (*)
L-Server changing (CHANGE) : Memory capacity = The value specified to the L-Server
* Note: The changing log 3. may not be output sometimes.
Refer to "8.6.10 Overcommit" in the "Setup Guide CE" for information on the RHEL-KVM memory amount.