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 (*) |
* Note: 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 Manager]
Output folder | Output destination file |
---|---|
Installation_folder\RCXCFMG\logs | vsys_audit_log.[n] (n is the number of generations) |
[Linux Manager]
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. (*) |
parameters | The parameters specified by the request. |
operation result | "SUCCESS" if the operation was successful and "FAILURE" if the operation failed. |
* Note: The operation types are as follows:
Operation type | Description |
---|---|
AccessControl#evaluate | Checking access permissions. |
AccessControl#getAuthority | Obtaining information about resource operation privileges for a user. |
DeployMaster#delete | Deleting configuration information. |
DeployMaster#getDetail | Obtaining detailed configuration information. |
DeployMaster#getSaveList | Obtaining a list of configuration information. |
DeployMaster#getTemplate | Obtaining a deployment master from an L-Platform template. |
DeployMaster#save | Saving configuration information. |
DeployMaster#setStatus | Setting the status of configuration information. |
Event#notify | Notifying events that occurred on a server. With the current version, changes to the power status, migration, reconfiguring, pool information, events are notified. |
EventLog#getList | Obtaining a list of event logs. |
Images#changeShow | Changing whether images are displayed. |
Images#getDetail | Obtaining detailed image information. |
Images#getList | Obtaining a list of images registered. |
Images#getServerType | Obtaining a list of L-Server Templates. |
Images#register | Registering image information with this product. |
Images#search | Searching image information. |
Images#unregister | Deregistering image information from this product. |
Images#update | Updating image information. |
Network#addCategory | Registering a network resource type. |
Network#deleteCategory | Deleting a network resource type. |
Network#getCategoryList | Obtaining a list of network types. |
Network#getList | Obtaining a list of networks. |
Network#getRulesetList | Obtaining a list of rulesets. |
Network#detailRuleset | Obtaining detailed ruleset information. |
Parameters#delete | Deleting parameter information. |
Parameters#getDetail | Obtaining detailed parameter information. |
Parameters#getList | Obtaining a list of parameter information. |
Parameters#set | Registering or updating parameter information. |
Softwares#create | Registering software information. |
Softwares#delete | Deleting software information. |
Softwares#getDetail | Obtaining detailed software information. |
Softwares#getList | Obtaining a list of software. |
Softwares#update | Updating software information. |
Templates#changeShow | Changing the settings as to whether L-Platform templates can be displayed. |
Templates#deletePublic | Deleting L-Platform templates. |
Templates#getDetail | Obtaining detailed L-Platform template information. |
Templates#importPublic | Registering L-Platform template information. |
Templates#search | Searching an L-Platform template. |
Templates#updatePublic | Updating templates |
VDisk#getList | Obtaining a list of existing disks. |
VServer#addPatch | Registering patch information. |
VServer#attach | Adding an expansion disk. |
VServer#backup | Creating a snapshot. |
VServer#cancelError | Releasing the error status of snapshots or restorations. |
VServer#changeSpec | Changing server performance. |
VServer#cloning | Collecting a cloning image from a deployed server. |
VServer#create | Adding a server. |
VServer#deletePatch | Deleting patch information. |
VServer#detach | Deleting an expansion disk. |
VServer#getBackupList | Obtaining a list of snapshots. |
VServer#getInitPW | Obtaining the initial password for a server. |
VServer#release | Returning a server. |
VServer#removeBackup | Deleting a snapshot. |
VServer#restore | Restoring a server. |
VServer#search | Obtaining server information. |
VServer#start | Starting a server. |
VServer#stop | Stopping a server. |
VSYS#addNetwork | Adding a segment to an L-Platform. |
VSYS#changeOrg | Changing a user ID or organization ID for an L-Platform. |
VSYS#convertFolder | Converting a system deployed with Systemwalker Software Configuration Manager V14.1 to an L-Platform for this product. |
VSYS#delete | Deleting an L-Platform from just the resource window after deleting failed, etc. |
VSYS#deleteLServer | Deleting a server included in an L-Platform from the L-Platform. |
VSYS#deleteNetwork | Deleting a segment from an L-Platform. |
VSYS#deploy | Deploying an L-Platform. |
VSYS#flowCancel | Canceling the application to deploy an L-Platform or change a configuration. |
VSYS#flowCancelRetry | Canceling the flow for saving a configuration and then making another application. |
VSYS#flowDeploy | Deploying an L-Platform. (For flows: no operation after authorization.) |
VSYS#flowEnableDeploy | Deploying an L-Platform. (For flows: operation to perform after authorization.) |
VSYS#flowEnableRelease | Returning all L-Platforms as a batch. (For flows: operation to perform after authorization.) |
VSYS#flowEnableUpdate | Reconfiguring an L-Platform. (For flows: operation to perform after authorization.) |
VSYS#flowError | Executing post-processing when an error has occurred with an application flow for deploying an L-Platform or changing a configuration. |
VSYS#flowForward | Applying to deploy an L-Platform or change a configuration. |
VSYS#flowRejectApplication | Rejecting deployment application. |
VSYS#flowRelease | Returning all L-Platforms as a batch. (For flows: no operation after authorization.) |
VSYS#flowReleaseApplication | Applying to return an L-Platform. |
VSYS#flowReleaseForward | Setting the status of a return application to "forwarding complete". |
VSYS#flowSaveCancel | Canceling the application to deploy an L-Platform or change a configuration. |
VSYS#flowUpdate | Reconfiguring an L-Platform. (For flows: no operation after authorization.) |
VSYS#getConfigurations | Obtaining configuration information. |
VSYS#getCurrency | Obtaining product currency information. |
VSYS#getDetail | Obtaining detailed information for an L-Platform. |
VSYS#getHostnameCounter | Obtaining a list of host name serial number counters. |
VSYS#getList | Obtaining a list of L-Platforms. |
VSYS#getLoginDate | Obtaining the date/time when the user logged in to the L-Platform Manager View. |
VSYS#getOperationLNetDevResult | Obtaining the operation logs for the server load balancer. |
VSYS#getPoolList | Obtaining a list of resource pools for ServerView Resource Orchestrator. |
VSYS#getTask | Obtaining task information. |
VSYS#getTenantList | Obtaining a list of tenants. |
VSYS#importLServer | Importing an L-Server under resource management to an L-Platform. |
VSYS#lock | Locking an L-Platform. |
VSYS#operateLNetDev | Executing server load balancer operations. |
VSYS#recoverDisk | Recovering a disk. |
VSYS#recoverNet | Recovering a network segment. |
VSYS#recoverNic | Recovering an NIC. |
VSYS#recoverServer | Recovering a server. |
VSYS#recoverSystem | Recovering an L-Platform. |
VSYS#release | Returning all L-Platforms as a batch. |
VSYS#resetHostnameCounter | Resetting the host name serial number counter. |
VSYS#setChangeInfo | Recovering an L-Platform name, server name, or server specification. |
VSYS#setDisplayStatus | Changing the status of an L-Platform. |
VSYS#setLoginDate | Updating the date/time when the user logged in to L-Platform Manager View. |
VSYS#setRecoverInfo | Recovering a resource ID or disk number. |
VSYS#setServerStatus | Recovering the status of a server. |
VSYS#setUndeploy | Changing the status of an L-Platform, server or disk to "undeployed". |
VSYS#start | Starting the servers in an L-Platform as a batch. |
VSYS#startServers | Starting the servers for multiple tenants as a batch. |
VSYS#stop | Stopping the servers in an L-Platform as a batch. |
VSYS#stopServers | Stopping the servers for multiple tenants as a batch. |
VSYS#syncServerStatus | Synchronizing server power statuses in a batch. |
VSYS#syncSpec | Synchronizing server performance information with the actual state. |
VSYS#unlock | Unlocking an L-Platform. |
VSYS#update | Reconfiguring an L-Platform. |
VSYS#updateLNetDev | Updating the parameters for the firewall and server load balancer. |
VSYS#updateRemarks | Changing the L-Platform remarks column input values after deploying. |
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 Manager]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | Installation_folder\RCXCFMG\config\vsys_log4j.xml | <param name="File" value="C:\ProgramData\Fujitsu\SystemwalkerCF-MG\logs\vsys_audit_log" /> |
[Linux Manager]
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 "2.1 Starting and Stopping the Manager" 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 Manager]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | Installation_folder\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 Manager]
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 "2.1 Starting and Stopping the Manager" 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 Manager]
Log name | Settings file | Location to change (one location) |
---|---|---|
vsys_audit_log | Installation_folder\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 Manager]
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 "2.1 Starting and Stopping the Manager" for information on how to Restart the manager.