Platform Log

1. Version 

2. Function introduction

The system status is to monitor and analyze the various conditions of the system operation. Through this function, various indicators of the system operation status can be viewed.

Including: access statistics, user behavior, template heat, performance monitoring, management logs, error logs. As shown below:

Check in detail which report under the directory is accessed and in what way, and you can also count how many times the report has been accessed, in order to see what the usage rate of each report is.

Statistical viewing includes two aspects of information viewing: system access statistics and report access details.

1. Number of system visits

"Number of System Visits" introduces the number of system visits, the number of visited templates, and the number of active customers in the form of a line graph. When FineReport is integrated into FineBI , the "Number of System Visits" interface is shown in the following figure:

·       Administrators can filter access times by month.

·       is accessed from any node, log information of the entire cluster can be viewed.

1) Data sources

The data in "System Visits" is to filter the data in the fine_record_execute table of the LogDB database .

When "Report Template, BI Template" is selected for "Statistical Object", the data in the fine_record_execute table whose type is within the range of the following table is filtered out for indicator statistics in the chart.

Note 1: For details about the fields in the fine_record_execute table, see: LogDB table structure .

Note 2: When "Report Template + BI Template" is selected for "Statistical Object", all the data shown in the table below will be filtered out.

Note 3: "Statistical objects" are counted according to the template name. If a dashboard is renamed, it will be divided into two "statistical objects" before and after the name change .

2) Computational logic

The calculation logic of each numerical value is shown in the following table:

2. Server usage

1) Number of people online in the current system

·       Websocket is not connected , the current number of online users in the system cannot be displayed correctly, and user logins are not counted in the current online population of the system. For details, please refer to: Websocket port is occupied/unavailable

·       When you log in to two accounts with the same browser, the information of the latter user will overwrite the information of the former, and only counts as one user.

·       must enter the platform through the login page to be counted in the current system online population (single sign-on is also applicable), only accessing the template, not the platform, will not be counted.

·       When a new user logs in to check the current online number of the system, remember to refresh the page and check it again.

2) Specific list description

In the "Server Usage" list, "XX user accessed XX template in the platform at XX time and XX place".

·       This detailed list shows the report template that is currently being previewed.

·       Ordinary users log in to view the template, and the access information of the template will be displayed in this detailed list in real time.

·       Ordinary users close the template they are accessing and refresh the platform, and the access information of the template in the detailed list disappears.

3. Template access details

"Template Access Details" records "XX user accessed XX template in the system at XX time and XX location in XX method", and the access records of all templates under the project will be displayed here.

"Template Access Details" details which report under the directory is accessed, access time, IP of access, operation (what way to access BI such as page preview, BI view, BI edit, EXCEL page export, etc.), role (login user) name), username, etc.

1) Query method

The administrator can select a certain time period, the default is "previous day" to "this day", click "Query", you can query the details under this time period, as shown in the following figure:

The administrator can check "Advanced Query Condition", select the content to be queried, and then click Query to query the details under the specific setting conditions, as shown in the following figure:

Note: BI projects of 5.1.15 and later support filtering logs whose operation user is empty, and support filtering templates whose template name is empty.

2) Export access details

After the query, the administrator can export the log file, as shown in the following figure:

·       For projects before 5.1.14, it supports exporting template access details, and only supports exporting in .txt format.

·       5.1.14 and later projects support exporting template access details. Click the "Export as log" button to export the .txt format, and click "Export as excel" to export the .xls format.

Note: Only 1W log data can be exported at most.

3) Operation Type

Some operation fields are numbers in the log, and the corresponding log information types are shown in the following table:

Note: In BI projects of version 5.1.13 and later, "?" is displayed after some operation types. Hover to view the specific operation information.

Supports viewing the access frequency and operation behavior of users within a specified time period, including operations such as viewing and exporting.

Display access data by user group, set date interval parameters and user parameters, and customers can query the report access status of different users within a specified time period, as shown in the following figure:

Note 1: If the public link is used to access, the operation user is empty.

Note 2: BI projects of 5.1.15 and later support filtering logs with empty username.

Click the user name hyperlink, click the user name to jump to the user's operation behavior details, as shown in the following figure:

After the query, the administrator can export the log file, as shown in the following figure:

·       Projects before 5.1.14 support exporting logs, only in .txt format.

·       5.1.14 and later projects support exporting logs. Click the "Export as log" button to export the .txt format, and click "Export as excel" to export the .xls format.

Note: Only 1W log data can be exported at most.

Supports template traffic analysis so that administrators can understand business hotspots. Count the access frequency of templates within a specified time period, including access operations such as viewing, exporting, and printing.

display is displayed in descending order of the total number of operations, the template name is displayed with the name configured in the platform, and the path is the path of the template, as shown in the following figure:

1) If the template is viewed through a non-platform directory (template URL or drillthrough), the template name is empty.

2) If the same template is mounted in multiple directories of the platform, it will be divided into multiple records for statistics.

The same template, if viewed through the URL or viewed through drilling, will be divided into multiple records for statistics.

Note: BI projects of 5.1.15 and later support filtering templates with empty template names.

Click the template path hyperlink , click to display the detailed access status of the template, and display the detailed data in chronological order. As shown below:

After the query, the administrator can export the log file, as shown in the following figure:

·       Projects before 5.1.14 support exporting logs, only in .txt format.

·       5.1.14 and later projects support exporting logs. Click the "Export as log" button to export the .txt format, and click "Export as excel" to export the .xls format.

Note: Only 1W log data can be exported at most.

It supports the response performance analysis of templates, and provides a reference for administrators to optimize the system.

Displays the templates of completed user requests, the longest response time, the shortest response time, the average time spent, and the memory usage. Set the date parameters, and set the operation behavior category parameters, as shown in the following figure:

Check "Details", the effect is as shown below:

After the query, the administrator can export the log file, as shown in the following figure:

·       Projects before 5.1.14 support exporting logs, only in .txt format.

·       5.1.14 and later projects support exporting logs. Click the "Export as log" button to export in .txt format, and click "Export as excel" to export in .xls format.

Note: Only 1W log data can be exported at most.

Same as access statistics, click query to display log information: platform module, platform setting items, operating user, operating IP, operating time, accessed resources, and operating type, as shown in the following figure:

Operation types include:

Check "Advanced Query Conditions", as shown in the following figure:

After the query, the administrator can export the log file, as shown in the following figure:

·       Projects before 5.1.14 support exporting logs, only in .txt format.

·       5.1.14 and later projects support exporting logs. Click the "Export as log" button to export the .txt format, and click "Export as excel" to export the .xls format.

Note: Only 1W log data can be exported at most.

For BI projects of version 5.1.19 and later, the "Template Error" function has been added.

1. Template error reporting function

Click Query to summarize and count the errors in the use of the template, including: template name, accessed resources, error code, error content, number of occurrences, and total number of visits, as shown in the following figure:

1) If the template is viewed through a non-platform directory (template URL or drillthrough), the template name appears as non-mount access.

2) If the same template is mounted in multiple directories of the platform, it will be divided into multiple records for statistics.

The same template, if viewed through the URL or viewed through drilling, will be divided into multiple records for statistics.

3) templates with error records are displayed in the filter bar .

Click "Error Details" to display the detailed error reporting and query information under the corresponding error reporting category of the corresponding template, including: user name, error details, query parameters, error reporting time, and template preview results.

Note: the first 5 errors will be recorded in a single visit

After the query, the administrator can export the template error log file, as shown in the following figure:

Supports exporting logs. Click the "Export as log" button to export the .txt format, and click "Export as excel" to export the .xls format.

Note: Only 1W log data can be exported at most.

2. Template error notification

The administrator logs in to the data decision system, clicks "Manage > Intelligent Operations > Platform Log", clicks "Global Settings", and supports enabling " Error Template Message", as shown in the following figure:

If the "Error Template Message" is enabled, the system will check the error reporting template of the previous day at 2:00 am every day. If there is an error reporting template, the administrator can be notified via SMS alerts, platform messages, and email alerts .

Note:

1) SMS reminder: need to open the SMS platform, click SMS for details

2) Mail reminder: need to configure the mail server, click the mailbox for details

websocket port needs to be configured and opened at the load balancing level . Related documents: Websocket port is occupied / unusable