This section explains the configuration management audit log.
The file name, file size, and number of generations of the audit log are shown below:
Log name | Description | File size | Number of generations |
---|---|---|---|
vsys_audit_log | Audit logs are output to this log. | 10 MB | 10 generations (*1) |
*1: If the number of saved generations exceeds 10 generations, old generations will be deleted, starting with the oldest generation.
The file size and the number of generations to be saved can be changed. Refer to "Procedure for changing the size of the file" and "Procedure for changing the number of generations to be saved" for details.
With default settings, audit logs will be held for approximately 50 days if 10 people use this product for approximately one hour per day per person. If necessary, back up audit logs at appropriate intervals according to the usage frequency. The names of the files to be backed up are shown below:
vsys_audit_log.[n] (where "n" is the generation number) Example: To back up three generations' worth of files, the names of the files to be backed up are as follows: - vsys_audit_log.1 - vsys_audit_log.2 - vsys_audit_log.3
Output Destination
The log output destinations are shown below:
[Windows]
Output folder | Output destination file |
---|---|
<Installation directory for this product>\RCXCFMG\logs | vsys_audit_log.[n] (n is the number of generations) |
[Linux]
Output folder | Output destination file |
---|---|
/var/opt/FJSVcfmg/logs | vsys_audit_log.[n] (n is the number of generations) |
Output format
Audit logs are CSV files where the following items are output in the following order:
Output format |
---|
<date/time when the operation was performed>,<user ID>,<organization ID>,<operation ID>,<parameters>,<operation result> |
Item | Description |
---|---|
date/time when the operation was performed | YYYY-MM-DD HH:MM:SS.sss (local time). |
user ID | The user ID of the user that executed the operation. |
organization ID | The organization ID of the user that executed the operation. |
operation type | A string indicating the content of the operation. (*1) |
parameters | The parameters specified by the request. |
operation result | "SUCCESS" if the operation was successful and "FAILURE" if the operation failed. |
*1: The operation types are as follows:
Operation type | Description |
---|---|
VSYS#deploy | Deploying a L-Platform. |
VSYS#update | Reconfiguring a L-Platform. |
VSYS#getList | Obtaining a list of L-Platforms. |
VSYS#getDetail | Obtaining detailed information for a L-Platform. |
VSYS#release | Returning all L-Platforms as a batch. |
VSYS#lock | Locking a L-Platform. |
VSYS#unlock | Unlocking a L-Platform. |
VServer#create | Adding a server. |
VServer#search | Obtaining server information. |
VServer#stop | Stopping a server. |
VServer#start | Starting a server. |
VServer#release | Returning a server. |
VServer#attach | Adding an expansion disk. |
VServer#detach | Deleting an expansion disk. |
VServer#changeSpec | Changing server performance. |
VServer#backup | Creating a snapshot. |
VServer#restore | Restoring a server. |
VServer#removeBackup | Deleting a snapshot. |
VServer#getBackupList | Obtaining a list of snapshots. |
VServer#cancelError | Releasing the error status of snapshots or restorations. |
VServer#addPatch | Registering patch information. |
VServer#deletePatch | Deleting patch information. |
VServer#getInitPW | Obtaining the initial password for a server. |
VServer#cloning | Collecting a cloning image from a deployed server. |
Event#notify | Notifying events that occurred on a server. With the current version, changes to the power status and migration events are notified. |
EventLog#getList | Obtaining a list of event logs. |
VSYS#setLoginDate | Updating the date/time when the user logged in to L-Platform Manager View. |
VSYS#getLoginDate | Obtaining the date/time when the user logged in to the L-Platform Manager View. |
VSYS#setUndeploy | Changing the status of a L-Platform, server or disk to "undeployed". |
VSYS#flowDeploy | Deploying a L-Platform. (For flows: no operation after authorization.) |
VSYS#flowEnableDeploy | Deploying a L-Platform. (For flows: operation to perform after authorization.) |
VSYS#flowUpdate | Reconfiguring a L-Platform. (For flows: no operation after authorization.) |
VSYS#flowEnableUpdate | Reconfiguring a L-Platform. (For flows: operation to perform after authorization.) |
VSYS#flowRejectApplication | Rejecting deployment application. |
VSYS#flowForward | Applying to deploy a L-Platform or change a configuration. |
VSYS#flowError | Executing post-processing when an error has occurred with an application flow for deploying a L-Platform or changing a configuration. |
VSYS#flowCancel | Canceling the application to deploy a L-Platform or change a configuration. |
VSYS#flowSaveCancel | Canceling the application to deploy a L-Platform or change a configuration. |
VSYS#flowCancelRetry | Canceling the flow for saving a configuration and then making another application. |
VSYS#flowReleaseApplication | Applying to return a L-Platform. |
VSYS#flowRelease | Returning all L-Platforms as a batch. (For flows: no operation after authorization.) |
VSYS#flowEnableRelease | Returning all L-Platforms as a batch. (For flows: operation to perform after authorization.) |
VSYS#flowReleaseForward | Setting the status of a return application to "forwarding complete". |
VSYS#changeOrg | Changing a user ID or organization ID for a L-Platform. |
VSYS#recoverSystem | Recovering a L-Platform. |
VSYS#recoverServer | Recovering a server. |
VSYS#recoverDisk | Recovering a disk. |
VSYS#setRecoverInfo | Recovering a resource ID or disk number. |
VSYS#setChangeInfo | Recovering a L-Platform name, server name, or server specification. |
VSYS#setServerStatus | Recovering the status of a server. |
Parameters#set | Registering or updating parameter information. |
Parameters#getList | Obtaining a list of parameter information. |
Parameters#getDetail | Obtaining detailed parameter information. |
Parameters#delete | Deleting parameter information. |
Softwares#create | Registering software information. |
Softwares#getList | Obtaining a list of software. |
Softwares#getDetail | Obtaining detailed software information. |
Softwares#delete | Deleting software information. |
Images#getList | Obtaining a list of images registered. |
Images#register | Registering image information with this product. |
Images#unregister | Deregistering image information from this product. |
Images#update | Updating image information. |
Images#search | Searching image information. |
Images#getDetail | Obtaining detailed image information. |
Images#getServerType | Obtaining a list of L-Server Templates. |
Network#getList | Obtaining a list of networks. |
Network#addCategory | Registering a network resource type. |
Network#deleteCategory | Deleting a network resource type. |
Network#getCategoryList | Obtaining a list of network types. |
Templates#importPublic | Registering template information. |
Templates#search | Searching a L-Platform template. |
Templates#getDetail | Obtaining detailed L-Platform template information. |
Templates#changeShow | Changing the settings as to whether L-Platform templates can be displayed. |
Templates#deletePublic | Deleting L-Platform templates. |
DeployMaster#getTemplate | Obtaining a deployment master from a L-Platform template. |
DeployMaster#save | Saving configuration information. |
DeployMaster#getSaveList | Obtaining a list of configuration information. |
DeployMaster#getDetail | Obtaining detailed configuration information. |
DeployMaster#delete | Deleting configuration information. |
DeployMaster#setStatus | Setting the status of configuration information. |
VSYS#getPoolList | Obtaining a list of resource pools for ServerView Resource Orchestrator. |
Procedure for changing output destination
Use the following procedure to change the audit log output destination.
Rewrite the settings file.
The following table shows the settings file and the location to change:
[Windows]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | <Installation directory for this product>\RCXCFMG\config\vsys_log4j.xml | <param name="File" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\vsys_audit_log" /> |
[Linux]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | /etc/opt/FJSVcfmg/config/vsys_log4j.xml | <param name="File" value="/var/opt/FJSVcfmg/logs/vsys_audit_log" /> |
Restart the manager.
Refer to "7.2 Starting and Stopping the Manager" in the Setup Guide CE for information on how to Restart the manager.
Procedure for changing the size of the file
Use the following procedure to change the audit log file size.
Rewrite the settings file.
The location to change is shown below:
[Windows]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | <Installation directory for this product>\RCXCFMG\config\vsys_log4j.xml | Change the underlined part of the <param name="MaxFileSize" value="10MB" /> element under the <appender name="auditfileout"class="org.apache.log4j.RollingFileAppender"> element to the desired value. Example: value="100MB" (to change the size of the audit log file to 100 MB) |
[Linux]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | /etc/opt/FJSVcfmg/config/vsys_log4j.xml | Change the underlined part of the <param name="MaxFileSize" value="10MB" /> element under the <appender name="auditfileout"class="org.apache.log4j.RollingFileAppender"> element to the desired value. Example: value="100MB" (to change the size of the audit log file to 100 MB) |
Restart the manager.
Refer to "7.2 Starting and Stopping the Manager" in the Setup Guide CE for information on how to Restart the manager.
Procedure for changing the number of generations to be saved
Use the following procedure to change the number of audit log generations to be saved.
Rewrite the settings file.
The location to change is shown below:
[Windows]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | <Installation directory for this product>\RCXCFMG\config\vsys_log4j.xml | Change the underlined part of the <param name="MaxBackupIndex" value="9" / /> element under the <appender name="auditfileout"class="org.apache.log4j.RollingFileAppender"> element to the desired value. Example: value="100" (to change the number of audit log generations to 100) |
[Linux]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | /etc/opt/FJSVcfmg/config/vsys_log4j.xml | Change the underlined part of the <param name="MaxBackupIndex" value="9" / /> element under the <appender name="auditfileout"class="org.apache.log4j.RollingFileAppender"> element to the desired value. Example: value="100" (to change the number of audit log generations to 100) |
Restart the manager.
Refer to "7.2 Starting and Stopping the Manager" in the Setup Guide CE for information on how to Restart the manager.