Platform Log

Version

Application Scenario

With Hierarchical Authorization enabled, administrators must be able to audit management operations, especially abnormal ones, for security and troubleshooting purposes. This requires tracking who performed what management operations and when.

Logs and system environment information for some users are difficult to obtain due to various factors, and this process is quite time-consuming.

Function Description

You can log in to FineDataLink as the super admin and choose System Management > Intelligent O&M > Platform Log, as shown in the following figure.

• User Behavior: You can view user actions, such as Login, Logout, Overtime, and Keep Login. 

• Operation Log: It records operations that the super administrator and sub-administrators have performed on FineDataLink, along with the corresponding timestamps. You can also query management records using specific conditions and export management logs with one click.

• System Log: You can filter and export log files by operation time and log type. It also supports one-click access to log file storage locations via the View Storage Location button and enables exporting project environment information by clicking the Click to export button.

On the User Behavior tab page, you can filter user actions such as Login, Logout, Overtime, and Keep Login, as shown in the following figure.

On the Operation Log tab, you can select the time range of operations via the Year-Month-Day and Dynamic Time filters and export logs.

Click the Query button to view platform management records. Fields include Module, Operation Object, Operation User, Operation IP Address, Operation Time, Accessed Resource, and Operation Type, as shown in the following figure.

Values of Operation Type include:

If you want to filter platform management records by conditions other than operation time, tick Advanced Query Condition, set the required query condition, and then click the Query button, as shown in the following figure.

After the query, you can export the log files, as shown in the following figure.

You can click Export Log to export log files in the TXT format and click Export Excel to export log files in the XLS format.

  Note: A maximum of 10,000 records of log data can be exported.

  Note: In the cluster environment, a cluster selection box is displayed in the upper right of the page. You can select a cluster node to download the corresponding log.

Through the System Log function, you can:

1. Filter logs by operation time and log type and export log files.

2. View the storage locations of log files with one click.

3. Obtain and export the report project environment information with one click.

Operation Time

You can select the operation time range via the Year-Month-Day and Dynamic Time filters to filter and download the corresponding log content. You can select any time range, but if it extends beyond the log file coverage, the downloaded file will only contain logs within the existing range.

• Year-Month-Day: You can select a specific date (Year-Month-Day), for example, 2020-01-01.

• Dynamic Time: You can estimate a date (for example, the beginning of the last quarter) based on the current time.

Log Type

The plugin supports the export of two types of logs: fanruan.log and gc.log.

When deployed on Tomcat, the system supports the export of another five types of logs: catalina.out, catalina.log, fanruan.gc.log, fanruan.log, and localhost_access_log.txt, as shown in the following figure.

Click the Click to download button, then decompress the downloaded package. For instance, the content of the exported fanruan.log file is shown in the following figure.

Viewing the Storage Location

Click View Storage Location to view the storage location of the log of each type, as shown in the following figure.

Environment Info Export

Click Click to export to export the environment information, as shown in the following figure.

 Note: In the cluster environment, a cluster selection box is displayed in the upper right of the page. The admin can select a specific node to download the required log.

The exported file is in the XML format. The following table shows the content.

  Note: The following shows the supported types of deployment containers; unknown will be returned for containers of all unavailable types.

• GERONIMO (returns geronimo)

• GLASSFISH (returns glassfish)

• JBOSS (returns jboss)

• JETTY (returns jetty)

• JONAS (returns jonas)

• OC4J (returns oc4j)

• RESIN (returns resin)

• TOMCAT (returns tomcat)

• WEBLOGIC (returns weblogic)

• WEBSPHERE (returns websphere)

• WILDFLY (returns wildfly)

• UNKNOWN (returns unknown)

For the description of the Global Setting page, see Log Introduction.