Top
ServerView Resource Orchestrator Cloud Edition V3.2.0 Operation Guide
FUJITSU Software
Part 4 Monitoring > Chapter 16 Monitoring Logs > 16.1 Operation Logs > 16.1.3 Operation Logs (Tenant Management, Accounting and System Condition)
PreviousNext

16.1.3 Operation Logs (Tenant Management, Accounting and System Condition)

This section explains operation logs of output by the tenant management, accounting and system condition functions.

Logs are classified into the following types:

Log name

Description

ctsec_audit_a.log

The log recorded when the [Tenants] tab on the ROR console was operated is output.

ctsec_audit_s.log

The log recorded when a temporary account was registered is output.

ctchg_audit.log

The log recorded when the accounting CLI was operated is output.

charging_audit.log

The log recorded when the [Usage Charge] tab on the ROR console was operated is output.

accounting_audit.log

The log recorded when the accounting API was operated is output.

cmdb_audit.log

The log recorded when the [Dashboard (System Conditions)] tab was operated is output.

Point

  • When performing L-Platform management, the operation log of the L-Platform management is output. Refer to "16.1.2 Operation Logs (L-Platform Management)" for details.

  • When performing Single Sign-On authentication, operation logs relating to the registration, modification, or deletion of infrastructure administrators, infrastructure operators, infrastructure monitors, administrators, operators and monitors can be checked in the directory service access log.

    When the directory service that is included with ServerView Operations Manager(hereinafter SVOM) is used, the storage locations and file names of access logs are as follows.

    • For SVOM 7.0 or earlier

      [Windows Manager]

      SVOM installation folder\ServerView Suite\opends\logs\access

      [Linux Manager]

      /opt/fujitsu/ServerViewSuite/opends/logs/access

    • For SVOM 7.1 or later

      [Windows Manager]

      SVOM installation folder\ServerView Suite\apacheds\logs

16.1.3.1 Output Destination

The log output destinations are shown below:

Log name

Output destination folder

Output destination files

ctsec_audit_a.log

[Windows Manager]
Installation_folder\RCXCTMG\SecurityManagement\log

[Linux Manager]
/var/opt/FJSVctsec/log

ctsec_audit_a.log.[n] (*)

ctsec_audit_s.log

[Windows Manager]
Installation_folder\RCXCTMG\SecurityManagement\log

[Linux Manager]
/var/opt/FJSVctsec/log

ctsec_audit_s.log.[n] (*)

ctchg_audit.log

[Windows Manager]
Installation_folder\RCXCTMG\Charging\log

[Linux Manager]
/var/opt/FJSVctchg/log

ctchg_audit.log.[n] (*)

charging_audit.log

[Windows Manager]
Installation_folder\RCXCTMG\Charging\log

[Linux Manager]
/var/opt/FJSVctchg/log

charging_audit.log.[n] (*)

accounting_audit.log

[Windows Manager]
Installation_folder\RCXCTMG\Charging\log

[Linux Manager]
/var/opt/FJSVctchg/log

accounting_audit.log.[n] (*)

cmdb_audit.log

[Windows Manager]
Installation_folder\CMDB\FJSVcmdbm\var\log\audit\uigui

[Linux Manager]
/opt/FJSVctdsb-cmdb/CMDB/FJSVcmdbm/var/log/audit/uigui/

cmdb_audit.log.[n] (*)

*Note: n indicates the number of generations.

16.1.3.2 File Size and Number of Generations

The log file size and number of generations are as follow.

Log name

File size

Number of generations (*1)

Whether the File Size Can Be Changed (*2)

Whether the Number of Generations to Save Can Be Changed (*2

ctsec_audit_a.log

10MB

11

Yes

Yes

ctsec_audit_s.log

ctchg_audit.log

charging_audit.log

accounting_audit.log

cmdb_audit.log

10

*1: If this number is exceeded, old generations will be deleted, starting with the oldest generation.

*2: For the method for changing the output destination, refer to "16.1.3.3 Procedure for changing the file size and the number of generations held".

The approximate file size of each log is as follows. If necessary, back up the logs at appropriate intervals according to the usage frequency.

Log Name

File Size

ctsec_audit_a.log

Approximately 5 KB for recording each series of operations (tenant creation, user creation, user change, etc.) on the [Tenants] tab.

ctsec_audit_s.log

Approximately 1 KB for recording each user registration.

ctchg_audit.log

Approximately 100 bytes for recording each execution of a command.

charging_audit.log

Approximately 300 bytes for recording each series of operations (displaying the [Usage Charge Detail] window, file downloading, etc.) on the [Usage Charge] tab.

accounting_audit.log

Approximately 100 bytes for recording each API call.

cmdb_audit.log

Approximately 100 bytes for recording when the [Dashboard (System Conditions)] tab was operated for the first time after logging in to the ROR console.

Example

When backing up ctsec_audit_a.log for three generations, the names of the files to be backed up are as follows:

  • ctsec_audit_a.log.1

  • ctsec_audit_a.log.2

  • ctsec_audit_a.log.3

16.1.3.3 Procedure for changing the file size and the number of generations held

Use the following procedure to change the file size and the number of generations to be saved.

  1. Stop the manager.
    Refer to "2.1 Starting and Stopping Managers" for information on how to stop the manager.

  2. Edit the appropriate items in the following setting files:

    • Setting files

      Log name

      Settings file

      ctsec_audit_a.log

      [Windows Manager]
      Installation_folder\RCXCTMG\conf\auditsecalog4j.xml

      [Linux Manager]
      /etc/opt/FJSVctmg/conf/auditsecalog4j.xml

      ctsec_audit_s.log

      [Windows Manager]
      Installation_folder\RCXCTMG\conf\auditsecslog4j.xml

      [Linux Manager]
      /etc/opt/FJSVctmg/conf/auditsecslog4j.xml

      ctchg_audit.log

      [Windows Manager]
      Installation_folder\RCXCTMG\conf\auditchglog4j.xml

      [Linux Manager]
      /etc/opt/FJSVctmg/conf/auditchglog4j.xml

      charging_audit.log

      [Windows Manager]
      Installation_ folder\RCXCTMG\conf\auditchgguilog4j.xml

      [Linux Manager]
      /etc/opt/FJSVctmg/conf/auditchgguilog4j.xml

      accounting_audit.log

      [Windows Manager]
      Installation_ folder\RCXCTMG\conf\auditacntlog4j.xml

      [Linux Manager]
      /etc/opt/FJSVctmg/conf/auditacntlog4j.xml

      cmdb_audit.log

      [Windows Manager]
      Installation_folder\CMDB\FJSVcmdbm\CMDBConsole\WEB-INF\classes\log4j.properties

      [Linux Manager]
      /opt/FJSVctdsb-cmdb/CMDB/FJSVcmdbm/CMDBConsole/WEB-INF/classes/log4j.properties

    • Setting items

      Setting item

      Description

      MaxFileSize

      This item sets the maximum size of log files.
      The file size can be specified using a combination of an integer greater than 0 and a unit (KB, MB or GB). (*1), (*2)
      Example: <param name="MaxFileSize" value="500KB"/>

      MaxBackupIndex

      This item sets the maximum number of generations of log file.
      An integer greater than 0 can be specified. (*1)
      Example: <param name="MaxBackupIndex" value="50"/>

      *1: Do not specify decimal fractions. Also, do not leave a blank space.

      *2: Do not specify a maximum file size that is larger than the size of the disk. Conversely, do not set values that are too small for the maximum file size, or else the logs will be overwritten frequently.

  3. Start the manager.
    Refer to "2.1 Starting and Stopping Managers" for information on how to start the manager.

16.1.3.4 Output format

Logs are CSV files where the following items are output in the following order:

Output format

operation date/time,user ID,tenant name,operation type,operation information,operation result


Item

Description

operation date/time

The date/time when the operation was performed.
The date/time is output using the following format:
YYYY-MM-DD HH:MM:SS.sss (local time)

user ID

The user ID of the user that performed the operation.
Fixed as ctmgadm for command operations.

tenant name

The tenant name of the user that executed the operation.
Fixed as ctmgadm for the infrastructure administratrative role or multiple roles users.

operation type

The type of the operation performed.
Refer to "16.1.3.5 Operation types and operation information" for details.

operation information

Detailed information for the operation type.
Refer to "16.1.3.5 Operation types and operation information" for details.

operation result

The result of the operation performed.
One of the following values is output:
SUCCESS: When the operation was successful
FAILURE: When the operation failed

16.1.3.5 Operation types and operation information

The following table shows the operation types and operation information that are output to operation logs:

Log name

Operation type

Content

Operation information (*1)

ctsec_audit_a.log

registUser

Notify user registration

"mail=""xxx@com"""

createUser

Create users

"userid=""<user ID of the user created>""&mail=""xxx@com""
&lastname=""<last name>""&firstname=""<first name> ""&auth=""<role name >(*7)""
&explanation=""xxxx""&corporatename=""fujitsu""
&emergencymail=""yyy@com""&emergencytel=""0000"""
(only if the infrastructure administrator performed or the tenant administrator performed by the direct registration method)

deleteUser

Delete users

"userid=""<user ID of the user deleted>"""

updateUser

Update user information

"userid=""<user ID of the user updated>""&mail=""xxx@com""
&lastname=""<last name>""&firstname=""<first name>"""
&auth=""<role name>(*8)""
&explanation=""xxxx""&corporatename=""fujitsu""
&emergencymail=""yyy@com""&emergencytel=""0000"""

listUser

Get a list of user information

None.

moveUser

Relocate users

"userid=""<user ID of the user that has been relocated>""&oldorgid=""<name of the original tenant>""
&neworgid="" name of the tenant to which the user has been relocated""

updatePassword

Update passwords

"userid=""<user ID of the user whose password has been updated>""

createOrg
(*2) (*3)

Create a tenant

  • With default setting

"orgid=""<tenant name of the tenant that has been updated>""&orgname=""<tenant name>""
&mail=""xxx@com""&globalpool=""<global pool that has been set>"""

  • With calculation of Usage Charges, following items will be added to output

&cutoffdate =""< Cutoff date>""&accountingmail=""<email address where usage charges are sent>""

  • With tenant of unique application process, following items will be added to output

&applicationprocess=""workflow.policy=default|custom,workflow.subscribe=infra-tenant|infra|tenant,workflow.reconfigure=infra-tenant|infra|tenant ,workflow.unsubscribe=infra-tenant|infra|tenant""

deleteOrg
(*3)

Delete tenants

"orgid=""<tenant name of the tenant that has been deleted>"""

updateOrg
(*2) (*3)

Update tenant information

  • With default setting

"orgid=""<tenant name of the tenant that has been updated>""&orgname=""<tenant name>""
&mail=""xxx@com""&globalpool=""<global pool that has been set>"""

  • With calculation of Usage Charges, following items will be added to output

&cutoffdate =""< Cutoff date>""&accountingmail=""<email address where usage charges are sent>""

  • With tenant of unique application process, following items will be added to output

&applicationprocess=""workflow.policy=default|custom,workflow.subscribe=infra-tenant|infra|tenant,workflow.reconfigure=infra-tenant|infra|tenant ,workflow.unsubscribe=infra-tenant|infra|tenant""

listOrg

Get a list of tenant information

None.

ctsec_audit_s.log

createUser

Create users

"userid=""<user ID of the user created>""&mail=""xxx@com""
&lastname=""<last name>""&firstname=""<first name>""""&auth=""<role name>(*9)""
&explanation=""xxxx""&corporatename=""fujitsu""
&emergencymail=""yyy@com""&emergencytel=""0000"""

ctchg_audit.log

updatePMaster

Update product master

None.

listPMaster

Get a list of product master

None.

updateMlogSch

Update periodic log schedule settings

"use=""yes|no""&time=""<time of output of periodic log>""&type=""<frequency of output of periodic log>""&day=""<day of output of periodic log>"""

listMlogSch

Get a list of periodic log schedule settings

"use=""yes|no""&time=""<time of output of periodic log>""&type=""frequency of output of periodic log""&day=""<day of output of periodic log>"""

listMeteringlog

Get a list of metering logs

"start=""<start date of the acquisition period>""&end=""<end date of the acquisition period>""
&type=""event|period"""

deleteMlog

Delete metering logs

"retention=""<log entry retention period>"""

getCurrencyUnit

Obtain currency unit settings

None

updateCurrencyUnit

Update currency unit settings

"currencycode=""currency code"""

resetCurrencyUnit

Initialize currency unit settings

None

charging_audit.log

listLplatformCharge

Get a list of usage charge for each L-Platform

None.

getDetailCharge

Get a breakdown of L-Platform usage charges

None.

listTenantCharge

Get a list of usage charge for each tenant

None.

listLplatformChargeByTenant

Get a list of usage charge for each L-Platform under the specified tenant

None.

downloadFile

File download

"target=""LplatformChargeList|DetailCharge|TenantChargeList|LplatformChargeListByTenant"""

accounting_audit.log

getResourceUsage

Get resource usage

None.

getUsagePoint

Get usage frequency

None.

registerUsagePoint

Register usage frequency (*4)

"date=""<date of data registered>(*5)""&id=""<L-Platform ID>""&name=""<L-Platform name>""&tenantname=""<tenant name of managed tenant>""&tenantdeletedate=""<date when managed tenant was deleted>(*6)"""

getDailyCharge

Get daily usage charges

None.

registerDailyCharge

Register daily usage charges (*4)

"date=""<date of data registered>""&id=""L-Platform ID""&name=""<L-Platform name>""&tenantname=""<tenant name of managed tenant>""&tenantdeletedate=""<date when managed tenant was deleted>"""

getMonthlyCharge

Get usage charges

None.

registerMonthlyCharge

Register monthly usage charges (*4)

"date=""<date of data registered>""&id=""L-Platform ID""&name=""<L-Platform name>""&tenantname=""<tenant name of managed tenant>""&tenantdeletedate=""<date when managed tenant was deleted>"""

getTenants

Get tenant information

None.

cmdb_audit.log

dispUsageStatus

Display system condition

None.

*1: If a value is not set for an item, """" is output.
An example is shown below.

... &globalpool=""""...

*2: If multiple global pools have been set, the "globalpool" are output separated by commas.
An example is shown below.

...&globalpool=""/AddressPool,/ImagePool""...

*3: For the operation result of createOrg, deleteOrg, or updateOrg, the processing result will be output. Use the operation log (resource management) to check the actual processing result. Refer to "16.1.1 Operation Logs (Resource Management)" for the checking procedure.

*4: Multiple lines may be output each time there is a registration operation.

*5: Output is in the format yyyy-MM-dd (for example, April 1, 2012 is output as 2012-04-01).

*6: Output is in the format yyyy-MM-dd THH:mm:ss.SSSZ (for example, 12:00 A.M. and 00.000 seconds on April 1, 2012 in time zone UTC+9:00 is output as 2012-04-01T00:00:00.000+0900).

*7: tenant_admin, tenant_operator, tenant_monitor, tenant_user, or names of roles created from copies of these.

*8: infra_admin, infra_operator, administrator, monitor, operator, tenant_admin, tenant_operator, tenant_monitor, tenant_user, or names of roles created from copies of these.

*9: tenant_user, or names of roles created from copies of tenant_user.

PreviousNext
Copyright 2010-2016 FUJITSU LIMITED