This section explains the operation logs of Resource Orchestrator.
Note
Operation logs should be used by only infrastructure administrators or administrators, as all user operations of Resource Orchestrator can be viewed.
Displaying resource names arranged in hierarchies is not supported.
Provides the functions to record user operations as operation logs in Resource Orchestrator.
Using this function, administrators can monitor the following information:
Time events were recorded in the operation logs
User ID
User group name
IP address
Status
Resource name
Operations
The operation logs are output in the following formats:
Date User Group IP Progress Resource Event ----- ----- ------ ----------- --------- --------- ------- |
Element Name | Description | Remarks |
|---|---|---|
Date | Time events were recorded in the operation logs | The time events recorded in the operation logs are output in the local time. If daylight savings time (a regulation of time in summer) is set on the operating system, the time events are output in daylight savings time. Time events are output in the following format: |
User | User ID | The user ID of the logged in user is output. |
Group | User group name | The name of the user group name the logged in user belongs to is output. When the logged in user does not belong to a user group, a hyphen ("-") is output. |
IP | IP address | The IP addresses of the connected clients are output. |
Progress | Status | Starting and stopping of operations, and errors are output. The following statuses are output:
|
Resource | Resource name | A resource name and a resource identifier are output in the following format:
|
Event | Operations | The parameters received by the manager are output. For the information that will be output, refer to "16.1.1.4 Scope of Operations Recorded in Operation Logs". |
Note
A hyphen ("-") may be output for an operation identifier.
For operations involving multiple resources, the same resource name as the one displayed in the Recent Operations on the ROR console and the event log is output in "Resource".
Example
Output the latest 1 day worth of data.
For details on operations for operation logs, refer to "5.13 rcxadm logctl" in the "Reference Guide (Command/XML) CE".
For the information that will be output, refer to "16.1.1.4 Scope of Operations Recorded in Operation Logs".
>rcxadm logctl list -latest -duration 1D <RETURN> Date User Group IP Progress Resource Event ----------------------- ----- ------ -------------- ---------------------- ----------------------- --------------------- 2011-03-10 21:15:00.390 - - 10.20.30.53 Starting(BX620-1_21) BX620-1_473(snap) l_servers create 2011-03-10 21:15:06.250 - - 10.20.30.53 Error(BX620-1_21) BX620-1_473(snap) l_servers create 2011-03-10 21:26:05.953 - - 10.20.30.73 Starting(BX620-1_25) BX620-1_510(snap) l_servers create 2011-03-10 21:29:21.150 - - 10.20.30.73 Completed(BX620-1_25) BX620-1_510(snap) l_servers create 2011-03-10 23:15:39.750 admin - 10.20.30.53 Starting(BX620-1_35) BX620-1_510(snap) server_images snapshot 2011-03-10 23:15:46.781 admin - 10.20.30.53 Completed(BX620-1_35) BX620-1_510(snap) server_images snapshot 2011-03-10 23:16:23.625 admin - 10.20.30.53 Starting(BX620-1_36) BX620-1_510(snap) server_images restore 2011-03-10 23:16:28.484 admin - 10.20.30.53 Completed(BX620-1_36) BX620-1_510(snap) server_images restore 2011-03-10 23:17:00.859 admin - 10.20.30.53 Starting(BX620-1_37) BX620-1_510(snap) server_images destroy 2011-03-10 23:17:04.718 admin - 10.20.30.53 Completed(BX620-1_37) BX620-1_510(snap) server_images destroy 2011-03-10 23:19:25.734 admin - 10.20.30.53 Starting(BX620-1_38) BX620-1_744(image_test) server_images create 2011-03-10 23:27:29.640 admin - 10.20.30.53 Completed(BX620-1_38) BX620-1_744(image_test) server_images create 2011-03-10 23:42:37.171 admin - 10.20.30.53 Starting(BX620-1_40) BX620-1_578(image_test) server_images destroy 2011-03-10 23:42:47.460 admin - 10.20.30.53 Completed(BX620-1_40) BX620-1_578(image_test) server_images destroy 2011-03-10 23:51:06.620 userA groupA 127.0.0.1 Starting(BX620-1_41) BX620-1_806(LS_RT_A001) l_servers create 2011-03-10 23:53:06.437 userA groupA 127.0.0.1 Completed(BX620-1_41) BX620-1_806(LS_RT_A001) l_servers create 2011-03-10 23:53:39.265 userA groupA 127.0.0.1 Starting(BX620-1_42) BX620-1_806(LS_RT_A001) l_servers start 2011-03-10 23:54:26.640 userA groupA 127.0.0.1 Completed(BX620-1_42) BX620-1_806(LS_RT_A001) l_servers start 2011-03-10 23:54:45.531 userA groupA 127.0.0.1 Starting(BX620-1_43) BX620-1_806(LS_RT_A001) l_servers restart 2011-03-10 23:55:26.859 userA groupA 127.0.0.1 Completed(BX620-1_43) BX620-1_806(LS_RT_A001) l_servers restart 2011-03-10 23:55:48.953 userA groupA 127.0.0.1 Starting(BX620-1_44) BX620-1_806(LS_RT_A001) l_servers stop 2011-03-10 23:56:26.390 userA groupA 127.0.0.1 Completed(BX620-1_44) BX620-1_806(LS_RT_A001) l_servers stop 2011-03-10 23:57:11.968 userA groupA 127.0.0.1 Starting(BX620-1_46) BX620-1_806(LS_RT_A001) l_servers attach 2011-03-10 23:58:21.359 userA groupA 127.0.0.1 Completed(BX620-1_46) BX620-1_806(LS_RT_A001) l_servers attach 2011-03-10 23:58:35.620 userA groupA 127.0.0.1 Starting(BX620-1_47) BX620-1_806(LS_RT_A001) l_servers detach 2011-03-10 23:59:23.343 userA groupA 127.0.0.1 Completed(BX620-1_47) BX620-1_806(LS_RT_A001) l_servers detach 2011-03-10 23:59:40.265 userA groupA 127.0.0.1 Starting(BX620-1_48) BX620-1_806(LS_RT_A001) l_servers migrate 2011-03-11 00:00:53.984 userA groupA 127.0.0.1 Completed(BX620-1_48) BX620-1_806(LS_RT_A001) l_servers migrate 2011-03-11 00:01:09.296 userA groupA 127.0.0.1 Starting(BX620-1_50) BX620-1_806(LS_RT_A001) l_servers update 2011-03-11 00:02:58.125 userA groupA 127.0.0.1 Completed(BX620-1_50) BX620-1_806(LS_RT_A001) l_servers update 2011-03-11 00:04:42.640 userA groupA 127.0.0.1 Starting(BX620-1_57) BX620-1_806(LS_RT_A001) l_servers destroy 2011-03-11 00:05:22.921 userA groupA 127.0.0.1 Completed(BX620-1_57) BX620-1_806(LS_RT_A001) l_servers destroy 2011-03-11 00:35:44.250 userA groupA 127.0.0.1 Starting(BX620-1_117) BX620-1_954(LS_RT_A001) folders move_resource 2011-03-11 00:35:44.625 userA groupA 127.0.0.1 Completed(BX620-1_117) BX620-1_954(LS_RT_A001) folders move_resource 2011-03-11 01:04:34.880 admin - 10.20.30.53 Starting(BX620-1_570) BX620-1_2193(master-52) l_servers convert 2011-03-11 01:04:36.650 admin - 10.20.30.53 Completed(BX620-1_570) BX620-1_2193(master-52) l_servers convert 2011-03-11 01:05:05.568 admin - 10.20.30.53 Starting(BX620-1_571) BX620-1_2193(master-52) l_servers revert 2011-03-11 01:05:06.451 admin - 10.20.30.53 Completed(BX620-1_571) BX620-1_2193(master-52) l_servers revert |
Note
The starting point (Starting) of recording for each operation is when the operation is displayed in the Recent Operations on the ROR console.
This section explains the methods for configuring and operating operation logs.
Perform the following procedure:
Disk space estimation
Infrastructure administrator (infra_admin) estimates the disk size to use for storing operation logs.
Estimate the amount of disk space using the following formula, and then decide the number of days to retain operation logs.
{(Number_of_operations_of_the_resource_in_1_day) * (Number_of_target_resources) * 1(KB)} * (retention_period) |
Example
Disk space when estimating that the retention period is 180 days (by default), the target resource is operated 4 times, and the number of target resources is 256
Retention period | Necessary Disk Space | Formula |
|---|---|---|
180 days worth | Approx. 185 MB | 4 * 256 * 1 * 180 = 184320 (KB) |
Check the settings in the [Date and Time properties] dialog of the operating system
Check whether the following tabs of the OS are configured correctly. If the settings are incorrect, set them correctly.
[Date and Time] tab
[Time Zone] tab
[Internet Time(or the Network Time Protocol)] tab
Configure the retention period of operation logs
Execute the rcxadm logctl set command, to configure the retention period for operation logs.
For details on the rcxadm logctl set command, refer to "5.13 rcxadm logctl" in the "Reference Guide (Command/XML) CE".
Start recording of the operation log
Execute the rcxadm logctl start command to start recording the operation log.
When the rcxadm logctl start command is executed, the operation logs will be recorded for the configured retention period from the date recording of operation logs is started.
Days when no events occur, or days when recording is not possible due to the manager being stopped are not counted as dates for recording.
Note
When the settings of the OS [Date and Time Properties] dialog have been changed after starting the recording of operation logs
It may not be possible to correctly display or delete the operation logs.
When changing the settings of the OS [Date and Time Properties] dialog after starting the recording of operation logs
Refer to "16.1.1.3 Retention".
When a Cloud Edition license has been registered
When starting the manager, recording of operation logs is started automatically.
This section explains the retention of operation logs.
Periodic deletion
Due to extended periods of operation or modification of retention periods, operation logs which have exceeded a certain retention period are periodically deleted.
The timing of deletion (based on retention period checks) is set to take place as the first operation after the date changes.
Note
The recording period is the retention period + 1. After periodic deletion is performed, the recording period will be equal to the retention period.
Periodic deletion is executed when the next recording is started (the first recording after the date changes), and operation logs will be deleted in chronological order.
Deletion
Users can delete unnecessary operation logs by defining a retention period.
Backup and Restore
Use the following procedure for backup and restoration of operation logs.
Backup
Confirm the "retention folder" for the operation logs.
Stop recording operation logs.
Back up the "retention folder" confirmed in step 1.
Start recording operation logs.
Restore
Confirm the "retention folder" for the operation logs.
Stop recording operation logs.
Restore the backed-up folder into the "retention folder" confirmed in step 1.
Start recording operation logs.
Modification of the settings in the [Date and Time properties] dialog after starting the recording of operation logs
Use the following procedure to make changes.
Stop recording operation logs.
Display the operation logs and back up the necessary portions from the records.
Confirm the "retention folder" for the operation logs.
Empty the "retention folder" by moving all files in the "retention folder" checked in step 3 to a new location.
Modify the settings in the [Date and Time properties] dialog.
Start recording operation logs.
For details on operations for operation logs, refer to "5.13 rcxadm logctl" in the "Reference Guide (Command/XML) CE".
Note
Once recording operations are stopped, user operations are not recorded until the recording of logs is started again.
Performing this procedure resets the recording period of operation logs to 0.
The scope of operations recorded in operation logs and the character strings displayed in the Event column are as indicated below.
Resource Type | Action | Strings Displayed in the Event Column |
|---|---|---|
L-Server | Creation | l_servers create |
Deletion | l_servers destroy | |
Modification | l_servers update | |
Powering on | l_servers start | |
Powering off | l_servers stop | |
Restarting | l_servers restart | |
Disk addition | l_servers attach | |
Disk detachment | l_servers detach | |
Folder migration | folders move resource | |
Migration | l_servers migrate | |
Physical L-Server configuration | l_servers set_attrs | |
Transmission of network information to physical L-Servers | l_servers setup | |
Conversion | l_servers convert | |
Reversion | l_servers revert | |
Image | Creation | server_images create |
Deletion | server_images destroy | |
Restore | server_images restore | |
Snapshot collection | server_images snapshot | |
L-Platform | Creation | l_platforms create |
Deletion | l_platforms destroy | |
Modification | l_platforms update | |
Tenant | Create | tenants create |
Deletion | tenants destroy | |
Modification | tenants update | |
Resource Folders | Creation | folders create |
Deletion | folders destroy | |
Modification | folders update | |
Role | Creation | roles create (*) |
Deletion | roles destroy | |
Modification | roles update (*) |
* Note: Detail informaition separated by commas is added to the end of the records if the -verbose option is specified when executing rcxadm logctl list command.
For details on the rcxadm logctl list command, refer to "5.13 rcxadm logctl" in the "Reference Guide (Command/XML) CE".
The output format and example are as follows.
roles create,BaseRole="Basic role name"[[,name="Operation group name",Authority="Operation name[,...]"]...]
roles update[,BaseRole="Basic role name"][[,name="Operation group name",Authority="Operation name[,...]"]...]
roles create,BaseRole="infra_admin",name="LPlatform",Authority="showlog",name="LServer", Authority="maintenance",name="Image",Authority="management",name="Console",Authority="home,dashboard,resource,template,lplatform,request,tenant,charge,account" roles update,name="LPlatform",Authority="showlog",name="LServer",Authority="maintenance", name="Console",Authority="home,dashboard,charge,account"
For details on the "Basic role name", "Operation group name", and "Operation name", refer to "15.9 Roles" in the "Reference Guide (Command/XML) CE".
