Overview
This document briefly describes each data table and their fields in LogDB database.
Table | Description |
---|---|
fine_record_execute | FineBI execution table |
fine_record_login | Login table |
fine_record_logout | Logout table (deprecated in 6.0.8 and later versions) |
fine_record_email | Email table |
fine_record_write | Filling table |
fine_record_error | Execution error log table |
fine_record_param | Common parameter combination table |
fine_record_sms | SMS sending table |
fine_record_operate | Management log table |
fine_record_sql | SQL execution table |
fine_record_gc | GC record table |
fine_record_conf | Partial configuration information table |
fine_record_lock | User lock log table |
fine_tpl_info | Template attribute table |
fine_container_entity | Container information table |
fine_function_process | Function point information table |
fine_operation_process_log | Cloud O&M log table |
fine_operation_shutdown_record | Semaphore information table |
fine_plugin_usage | Plugin information table |
fine_schedule_record | Log table recording task schedule execution |
fine_config_operation | Deletion monitoring table |
fine_relationship | Lineage analysis table |
fine_intelli_honeypot | Real-time event tracking table |
fine_intelli_log_honeypot | Log tracking table |
fine_update_task | Update task table |
fine_update_task_detail | Update task details table |
performAnalysis | Data structure |
fine_intelli_focus_point | Function tracking table |
fine_real_time_usage | Application real-time status table |
fine_intelli_consume_point | Performance information table |
fine_template_error | Execution error log |
fine_engine_performance | Basic information record of computing tasks |
fine_record_execute (FineBI Execution Table)
FineBI execution table: table to which a record is added upon report access/export/print, with corresponding information filled in the respective fields.
The following table defines each field.
Field | Definition | Notes | Data Format |
---|---|---|---|
uuid | User's unique identifier field | - | VARCHAR |
id | Primary key | - | VARCHAR |
tname | Dashboard storage path | - | VARCHAR |
displayName | Name of the directory to the platform | Records the full path of the directory. If you access the link directly, empty content is displayed. | VARCHAR |
type | Report access method | For details, see the following table. The value ranges from 0 to 504. Currently 58 codes are used. | INTEGER |
param | Name of a shared node. | The field has a value in JAR packages generated at and after 2020-08-04. If the shared node is a multi-level department, the name is recorded in Level-1 node/Level-2 node/Node format. One row of data is recorded only (without export) for each sharing. | VARCHAR |
ip | Operator IP address | Recorded only (without export) | VARCHAR |
username | User who execute reports | - | VARCHAR |
userrole | Role assigned to the user who execute reports | - | VARCHAR |
consume | Execution time consumption | Includes SQL execution time and report calculation time (in milliseconds). | BIGINT |
time | Log start time | - | BIGINT |
sql | SQL clause | Valid for FineReport and empty for FineBI dashboards (not used by FineBI). Records SQL clauses (excluding SQL clauses in FineBI-related SQL data tables) executed in FineReport reports. | VARCHAR |
sqlTime | Total SQL execution time | Valid for FineReport and 0 for FineBI dashboards (not used by FineBI). | BIGINT |
browser | Version of the browser used by the client to access reports | In 5.1.11 and later versions, you can use terminal in this field to identify the access terminal. browser: browser type/version OSInfo: operating system, which can be Windows, Mac, and Unix. terminal: client identifier, which can be PC, App, and H5. PC: PC terminal as the access terminal App: FineReport app/HTML5 terminal as the access terminal to access public links H5: HTML5 terminal as the access terminal to access non-public links | VARCHAR |
memory | Report-occupied memory, in byte | Valid for FineReport and 0 for FineBI dashboards (not used by FineBI). | BIGINT |
reportId | Template ID | - | VARCHAR |
userId | User ID | - | VARCHAR |
complete | Calculation complete or not | Valid for FineReport and 0 for FineBI dashboards (not used by FineBI). | INTEGER |
source | Access method | Valid for FineReport and 0 for FineBI dashboards (not used by FineBI). integration: access through URL single: platform access | VARCHAR |
sessionID | Session ID | Associates with event tracking related to frontend rendering time consumption in the performance tracking table (fine_intelli_consume_point). | VARCHAR |
node | Name of the node loading templates | VARCHAR | |
error | First error message during template execution | VARCHAR | |
webInfo | Template execution information | webResolution: resolution of the current template execution during frontend access, in x*y record format fullScreen: indicates whether to use the full-screen mode for the current template execution during frontend access, which can be 1 or 0 | VARCHAR |
lastMod | Last template modification time | - | BIGINT |
detail | Details | Records details of shared dashboards. | VARCHAR |
fineMarkId | ID of the device used to preview template | - | VARCHAR |

The node, error, and webInfo fields need to be updated to JAR packages generated at and after 2021-03-17.
The following table describes specific meanings of the type field.
Code | Type | Field |
---|---|---|
0 | Page preview | page |
1 | Online analysis | view |
2 | Filling preview | write |
3 | Decision-making report preview | form |
4 | Row-based engine | layer |
5 | Online editing | edit |
6 | New filling | write_plus |
7 | New engine preview | page_plus |
8 | FVS preview | |
9 | Developer debugging preview | |
10 | Exporting as Excel by page | excel |
11 | Exporting as Excel | excelO |
12 | Exporting entire Excel, corresponding to the following scenarios: (1) Exporting as Excel by the big dataset export plugin (2) Exporting as Excel by page and Exporting as Excel with the row-based engine enabled | excelL |
13 | Page-based exporting as Excel by sheet | excelS |
14 | Exporting as PDF | |
15 | Exporting as Word | word |
16 | Exporting as SVG | svg |
17 | Exporting as CSV | csv |
18 | Exporting as Text | text |
19 | Exporting as JPG | jpg |
20 | Exporting as PNG | png |
21 | Exporting as GIF | gif |
22 | Exporting as BMP | bmp |
23 | Exporting as WBMP | wbmp |
24 | Template export from the built-in dataset | cpt |
25 | Exporting as HTML | html |
26 | Exporting filled tables as HTML | write_html |
27 | Exporting as Excel from FineBI | |
30 | Flash printing | print_flash |
31 | PDF printing | print_pdf |
32 | Applet printing | print_applet |
33 | Zero-client printing | print_noclient |
34 | Local-software printing | print_native |
101 | FineBI template viewing | bi_view |
102 | FineBI template editing (1) Record logic: The system records once when you perform multiple operations or no operation on the page loaded completely after opening a dashboard and entering the edit mode, and record the second time the next time you click the template to enter the edit mode or refresh the webpage. (2) The system records each time you edit the same dashboard. | bi_edit |
103 | FineBI template sharing | bi_share |
104 | FineBI public link creation | bi_create_publink |
105 | FineBI public link viewing | bi_view_share |
106 | Exporting FineBI templates globally as PDF | bi_template_export_pdf |
107 | Exporting FineBI templates globally as Excel | bi_template_export_excel |
108 | Exporting FineBI components as Excel | bi_component_export_excel |
109 | Saving FineBI templates as | |
201 | Browser/Tab page closing (FineBI) | |
202 | Self-service dataset editing | |
205 | Disabling FineBI template sharing | |
206 | FineBI public link disabling | |
301 | Component preview | |
302 | Component editing | |
401 | Previewing Excel plugin-made templates | |
402 | Editing Excel plugin-made templates (reserved) | |
403 | Sharing Excel plugin-made templates | |
404 | Creating a public link for Excel plugin | |
405 | Accessing Excel plugin-made templates via a public link | |
408 | Exporting Excel components as Excel | |
409 | Saving Excel dashboards as | |
501 | Subject viewing | |
502 | Subject editing | |
503 | Group collaboration | |
504 | Subject collaboration | |
602 | Base table editing |
fine_record_login (Login Table)
Login table: table used to record user login logs.
The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Login time | BIGINT |
ip | Login IP address | VARCHAR |
username | Login user | VARCHAR |
userrole | Login user role | VARCHAR |
actionMethod | Login method | INTEGER |
actionType | Operation type | INTEGER |
authMethod | Authentication method | INTEGER |
actionResult | Operation result | INTEGER |
fine_record_logout (Logout Table)

Logout table: table used to record user logout logs.
The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | User logout time | BIGINT |
ip | Logout IP address | VARCHAR |
username | Logout username | VARCHAR |
userrole | Logout user role | VARCHAR |
fine_record_email (Email Table)
Email table: table to which an email sending log is added when the report sends an email (only that in the toolbar), with corresponding information filled in the respective fields.
The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
sender | Sender's username | VARCHAR |
receiver | Recipient's username | VARCHAR |
Recipient maibox box | VARCHAR | |
ip | IP address for sending the email | VARCHAR |
username | User sending the email | VARCHAR |
tname | Dashboard storage path | VARCHAR |
displayName | Actual dashboard name, not name of the dashboard in Directory Management If you access the link directly, empty content is displayed. | VARCHAR |
content | Email content | VARCHAR |
time | Sending time | BIGINT |
result | Email sent successfully or not | BIT |
detail | Details | VARCHAR |
fine_record_write (Filling Table)
Filling table: table to which a filling log is added when you fill in the report, with corresponding information filled in the respective fields.
The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
username | User who fill in reports | VARCHAR |
tname | Dashboard storage path | VARCHAR |
time | Filling time | BIGINT |
sql | SQL clause | VARCHAR |
sqlTime | Total SQL execution time | BIGINT |
result | Filling successful or not | BIT |
ip | IP address for filling in the report | VARCHAR |
displayName | Actual dashboard name, not name of the dashboard in Directory Management If you access the link directly, empty content is displayed. | VARCHAR |
detail | Details | VARCHAR |
browser | Version of the browser used by the client to access reports | VARCHAR |
consume | Execution time consumption, including SQL execution time and report calculation time | BIGINT |
body | JSON data structure, recording the following information: (1) key: fixed identifier of the request (2) value: (times, max, min, avg) times: occurrence times of requests of this type max: maximum response time for requests of this type, in milliseconds min: minimum response time for requests of this type, in milliseconds avg: average response time for requests of this type, in milliseconds | VARCHAR |
fine_record_error (Execution Error Log Table)
Execution error log table: table to which a record is added when an error occurs during report execution, with corresponding information filled in the respective fields to record all errors and fatal-level errors.
The following table defines each field.

Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
displayName | Actual dashboard name, not name of the dashboard in Directory Management If you access the link directly, empty content is displayed. | VARCHAR |
ip | IP address for report execution | VARCHAR |
msg | Error information | VARCHAR |
time | Error record time | DATE |
tname | Storage path of the error dashboard If no template error occurs, the tname field is recorded as the non-template trigger error. | VARCHAR |
trace | Error path | VARCHAR |
username | User who execute reports | VARCHAR |
userrole | Role assigned to the user who execute reports | VARCHAR |
errorcode | Error code It is recorded as empty if no error code is displayed. | VARCHAR |
platformDisplay | Displayed in the platform or not 1: yes 0: no If an error log is recorded in this table, this field is set to 1. Otherwise this field is set to 0. If you filter error logs from platform logs, only records with platformDisplay=1 are displayed. | INTEGER |
fine_record_param (Common Parameter Combination Table)
Common parameter combination table: table to which common parameter combination logs are recorded.

The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
templateid | Dashboard ID | VARCHAR |
username | User | VARCHAR |
pgroup | Parameters, which are displayed in array as follows: {Parameter 1: Value, Parameter 2: Value} The pgroup field is displayed in encrypted mode for JAR packages generated at and after 2020-02-28. | VARCHAR |
time | Record time | BIGINT |
fine_record_sms (SMS Sending Table)
SMS sending table: table to which an SMS sending log is added when an SMS is sent, with corresponding information filled in the respective fields.
The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
receiver | Recipient's username | VARCHAR |
mobile | Recipient's phone number | VARCHAR |
content | Email content | VARCHAR |
time | Sending time | BIGINT |
result | Email sent successfully or not | BIT |
detail | Details | VARCHAR |
sender | Sender's username | VARCHAR |
fine_record_operate (Management Log Table)
Management log table: table to which a record is added when you operate a module, with corresponding information filled in the respective fields.
The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
type | Module (storing internationalization keys), namely each sub-tab under System Management | VARCHAR |
item | Setting items on each sub-tab page under System Management, such as templates under Directory Management and users under User Management | VARCHAR |
resource | Accessed resource, such as "Full node path" and "Name (username)" | VARCHAR |
operate | Operation, including adding, deletion, modification, enabling, disabling, reuse, restoration, update, export, end, and installation | VARCHAR |
username | Username | VARCHAR |
ip | User's IP address | VARCHAR |
time | User's operation time | BIGINT |
detail | Details | VARCHAR |
requestParam | Request parameter | VARCHAR |
platformDisplay | Platform display level | INTEGER |
status | Operation successful or failed | INTEGER |
fine_record_sql (SQL Execution Table)
SQL execution table: table to which SQL execution status is recorded.

The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
columns | Dataset size, recording the column quantity | BIGINT |
dsname | Dataset name | VARCHAR |
executeid | Execution batch ID (same batch ID used for batch-executed SQL clauses during each preview/query) | VARCHAR |
rows | Dataset size, recording the row quantity | BIGINT |
sqltime | SQL execution time, in milliseconds | BIGINT |
connection | Data connection name | VARCHAR |
connectionID | Data connection ID Associates with event tracking related to data source connection in the function tracking table (fine_intelli_focus_poin). | VARCHAR |
time | Record time | BIGINT |
fine_record_gc (GC Record Table)
GC record table: table to which system GC information is recorded.
The following table defines each field.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
heapBeforeUsed | Heap memory usage before GC | BIGINT |
heapAfterUsed | Heap memory usage after GC | BIGINT |
heapBeforeCommitted | Applied heap memory before GC | BIGINT |
heapAfterCommitted | Applied heap memory after GC | BIGINT |
gcStartTime | GC start time | BIGINT |
duration | GC duration | BIGINT |
gcCause | GC cause Common causes include: System.gc() Allocation Failure humongous Metadata GC Threshold Ergonomics GCLocker Initiated GC | VARCHAR |
gcType | GC type, which can be GC or Full GC | VARCHAR |
metaspaceBeforeUsed | Metaspace memory usage before GC | BIGINT |
metaspaceBeforeCommitted | Applied metaspace memory before GC | BIGINT |
metaspaceAfterUsed | Metaspace memory usage after GC | BIGINT |
metaspaceAfterCommitted | Applied metaspace memory after GC | BIGINT |
balancePromoterScore | GC ergonomics aborts | INTEGER |
youngBeforeUsed | Young-generation memory usage before GC | BIGINT |
youngBeforeCommitted | Applied young-generation memory before GC | BIGINT |
youngAfterUsed | Young-generation memory usage after GC | BIGINT |
youngAfterCommitted | Applied young-generation memory after GC | BIGINT |
loadScore | Overall load score | INTEGER |
node | User-named node name, which is empty in standalone configuration | VARCHAR |
oldBeforeUsed | Old-generation memory usage before GC | BIGINT |
oldBeforeCommitted | Applied old-generation memory before GC | BIGINT |
oldAfterUsed | Old-generation memory usage after GC | BIGINT |
oldAfterCommitted | Applied old-generation memory after GC | BIGINT |
pid | Process PID | VARCHAR |
releasePromoterScore | Release score | INTEGER |
time | Record time | BIGINT |
fine_record_conf (Partial Configuration Information Table)
Partial configuration information table: table to which partial configuration information is recorded.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Record time | BIGINT |
id | Configuration item | VARCHAR |
value | Configuration item's value | VARCHAR |
fine_record_lock (User Lock Log Table)
User lock log table: table to which user lock logs are recorded.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time of import into the database | BIGINT |
lockItem | Locked object | VARCHAR |
lockTime | Lock time | VARCHAR |
autoUnlockTime | Automatic unlock time | VARCHAR |
fine_tpl_info (Template Attribute Table)
Template attribute table: table to which template attributes are recorded.

Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time of import into the database | BIGINT |
id | ID | VARCHAR |
tid | Template ID | VARCHAR |
tname | Physical template name, recording the full path under reportlets | VARCHAR |
cnums | Number of conditional attributes | BIGINT |
formnums | Number of formulas | BIGINT |
sheetnums | Number of sheets | BIGINT |
dsnums | Number of datasets | BIGINT |
compformnums | Number of complex formulas, including hierarchical coordinates, SQL, and VALUE formulas | BIGINT |
submitnums | Number of built-in submissions | BIGINT |
isfrozen | Freezing used or not | BIT |
isfoldtree | Collapsible tree used or not | BIT |
widgetnums | Number of widgets | BIGINT |
tsize | Total template size | BIGINT |
imgsize | Size of a image in the template | BIGINT |
execute0 | Engine status summary 0 | BIGINT |
execute1 | Engine status summary 1 | BIGINT |
execute2 | Engine status summary 2 | BIGINT |
execute3 | Engine status summary 3 | BIGINT |
execute4 | Engine status summary 4 | BIGINT |
mem0 | Memory status summary 0 | BIGINT |
mem1 | Memory status summary 1 | BIGINT |
mem2 | Memory status summary 2 | BIGINT |
mem3 | Memory status summary 3 | BIGINT |
mem4 | Memory status summary 4 | BIGINT |
sql0 | SQL status summary 0 | BIGINT |
sql1 | SQL status summary 1 | BIGINT |
sql2 | SQL status summary 2 | BIGINT |
sql3 | SQL status summary 3 | BIGINT |
sql4 | SQL status summary 4 | BIGINT |
filternums | Number of filters | BIGINT |
injectnums | Number of parameter injections | BIGINT |
formula | Usage of formulas in the template | VARCHAR |
jsapi | Usage of JavaScript APIs in the template | VARCHAR |
recordtime | Template detection time | VARCHAR |
fine_container_entity (Container Information Table)
Container information table: table to which container information is recorded.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time of import into the database | BIGINT |
node | Node name | VARCHAR |
item | Configuration item | VARCHAR |
value | Configuration item's value | VARCHAR |
fine_function_process (Function Point Information Table)
Function point information table: table to which function point information is recorded.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time of import into the database | BIGINT |
function | Function point | VARCHAR |
fine_operation_process_log (Cloud O&M Log Table)
Cloud O&M log table: table to which cloud O&M logs are recorded.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Record time | BIGINT |
node | Node name | VARCHAR |
process | Log content | VARCHAR |
fine_operation_shutdown_record (Semaphore Information Table)
Semaphore information table: table to which semaphore information is recorded.

Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time of import into the database | BIGINT |
pid | Process ID | VARCHAR |
startTime | Start time | BIGINT |
upTime | End time | BIGINT |
node | Node | VARCHAR |
signalName | Signal name | VARCHAR |
fine_plugin_usage (Plugin Information Table)
Plugin information table: table to which plugin information is recorded.

Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time of import into the database | BIGINT |
plugin | Plugin name | VARCHAR |
version | Plugin version | VARCHAR |
API | Usage of interfaces in the plugin | VARCHAR |
operation | Plugin running status | VARCHAR |
register | Plugin registration status | VARCHAR |
enable | Plugin enabled or not | BIT |
fine_schedule_record (Task Schedule Execution Log Table)
Task schedule execution log table: table to which task schedule execution information is recorded.
Field | Definition | Field Type |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
id | Primary key UUID | VARCHAR |
creator | Creator | VARCHAR |
detailMessage | Details | VARCHAR |
filePath | Generated attachment path, which is a reserved field | VARCHAR |
logMessage | Log information | VARCHAR |
logTime | Task execution time Log print time | BIGINT |
logType | Log type 0: failure 1: success 2: skip | INTEGER |
nextFireTime | Next record time, which is a reserved field | BIGINT |
runType | Attachment processing type 0: generated by snapshot 1: sent by email 2: uploaded by FTP 3: pushed by message 4: file print 5: sent by SMS 6: mounted by platform 7: customized 8: regularly filled 9: notified by client 10: uploaded by SFTP | INTEGER |
taskName | Task name | VARCHAR |
taskID | Task ID | VARCHAR |
time | Time of import into the database | BIGINT |
fine_intelli_focus_point (Function Tracking Table)
Function tracking table: table to which all common event tracking information is saved.
The following table defines each field.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
id | Event tracking ID | VARCHAR |
text | Main content recorded | VARCHAR |
source | Event tracking source -1: UNDEFINED 1: EMBED (function point of the built-in JAR package) 2: PLUGIN (plugin function point) 4: REPORT (FineReport function point) 8: BI (FineBI function point) | INTEGER |
time | Time | DATE |
username | Username, which is transcoded (0 for super admin) | VARCHAR |
ip | IP address triggering event tracking | VARCHAR |
title | Title (what is event tracking) | VARCHAR |
body | One JSON data structure, storing information of different function points by function point ID Secondary information, which may be empty | VARCHAR |
Field ID format description:
Example: FR-P1001
FR: prefix, indicating FR event tracking
First character: function (F)/performance (P)
Second character: category, which can be 1 (data source), 2 (frontend), 3 (error reporting), 4 (intelligent O&M), or 5 (designer)
The following table describes the relationship between the field ID and body.
ID | Body | Function |
---|---|---|
FR-P1001 | id: data connection ID version: data source version driver: connection driver information times: usage times connecttime: time when connection is created | Records information related to data connection. |
FR-F3001 | Specific error stacks | Records project startup failure causes. |
FR-F4001 | Initial plugin record example: {node:2,memory:16,situation:normal,inform:1,type:auto} node: recommended number of nodes (1 recommended in standalone deployment) memory: recommended standalone/single-node memory situation: recommended situation; normal: normal configuration as recommended, in which case node and memory have values; error: abnormal configuration (not as recommended), in which case node and memory are empty; inequacy: insufficient running data, in which case node and memory are empty; nonsupport: recommended configuration unsupported, in which case node and memory are empty inform: indicates whether notification is made; 1: yes; 0: no type: recommended type; auto: type recommended based on daily operation data; manual: type recommended based on user interface access links | Recommended value for memory configuration |
FR-F4002 | Record example: {sessionid: xxxxxx, reason: release, detail: row count, load: high load, cell num: 100000, survival time: 600000} sessionid: ID of the cleared session reason: reason for session clearance, which can be divided into life (lifecycle), limit (template limit), and release (intelligent release) detail: detailed reason for session clearance When the value of reason is life, this record is empty. When the value of reason is limit, this record is displayed as follows: row count (row quantity limit for a single dataset), cell count (cell limit for a single template), sql time (SQL execution time limit), excel cell count (cell limit of Excel to be imported), commit row count (quantity limit of records to be submitted), cartesian (limit for filling in Cartesian product). When the value of reason is release, this record is displayed as follows: stop calculating. load: system's load condition when the session is killed, which can be endanger (endangered status), terrible load (extremely high load), high load (high load), or normal load (medium/low load) cell num: number of calculated cells survival time: survival time | Records the situation in which the session is cleared due to lifecycle, template limitation, and high load-caused computation suspension. |
FR-F4003 | Record example: {type: high load kill, kill num time: 50, kill num cell: 50, session num: 300, load: terrible load} type: high load kill (minor kill); terrible load kill (major kill); remove all (super kill to clear all sessions) kill num time: number of sessions killed due to long time without update (recorded as empty if the value of type is remove all) kill num cell: number of sessions killed due to too many cells (recorded as empty if the value of type is remove all) kill num sum: number summary of killed session session num: total number of sessions before session release load: system's load condition when the session is killed, which can be endanger (endangered status), terrible load (extremely high load), high load (high load), or normal load (medium/low load) | Records session release situation triggered by GC callback. |
FR-F5001 | Record example: {disk_beforegc:50, disk_aftergc:50} | Records GC cleaning situation of template version management. |
FR-F5002 | node: node name time: process shutdown time pid: process PID startTime: process start time upTime: process duration signalName: semaphore | System shutdown record: records process information before and after system shutdown and shutdown types. |
FR-F5003 | node: node name containerMem: memory set for the container cpu: number of CPU cores disk: total disk space diskUsed: used disk space jdkVersion: JDK version containerVersion: web container version machineMem: physical machine's memory system: server's operating system systemNum: server's operating system bit arch: processor architecture, such as x86_64 and x86 diskSpeed: disk access speed FRbuildNO: FineReport's JAR package version BIbuildNO: FineBI's JAR package version (empty if FineBI is not used) serverType: server type (cloud: cloud server; local: local server) gcType: garbage collector type | Container configuration situation: records configuration information of the container and server where the application is located once a day. |
FR-F5004 | licType: registration type expireTime: registration expiration time CTRID: contract ID companyId: company ID productVersion: product version platformUserNum: number of users | User's basic information: records user's registration information once a day. |
FR-F5005 | tid: template ID tName: physical template's name (complete path under reportlets) cNums: number of conditional attributes formNums: number of formulas sheetNums: number of sheets dsNums: number of datasets compFormNums: number of complex formulas (including hierarchical coordinates, SQL, and VALUE formulas) submitNums: number of built-in submissions isFrozen: freezing used or not isFoldTree: collapsible tree used or not widgetNums: number of widgets filterNums: number of filters injectNums: number of parameter injections formula: usage of formulas in the template jsAPI: usage of JavaScript APIs in the template (limited to a maximum of 255 characters) tSize: total template size imgSize: size of a image in the template lineEngine: row-based engine enabled or not (1: enabled; 0: disabled) execute0-execute4: each level's record of the 5-level execution time mem0-mem4: each level's record of the 5-level memory usage sql0-sql4: each level's record of the 5-level SQL execution time | Template attribute information: template's various information (one record output per day for each template) |
FR-F5006 | id: location of data in the configuration value: data value | Configuration information: records specific information from the fine_conf_entity table in FineDB once a day. |
FR-F5007 | plugin: plugin name version: plugin version API: usage of APIs in the plugin operation: plugin running status register: plugin registration status enable: plugin enabled or not | Plugin usage situation: recorded once a day for each plugin. |
FR-F5008 | function: purchase status of function points | Purchase status of function points: recorded once a day. |
fine_real_time_usage (Real-Time Application Status Table)
Real-time application status table: table to which real-time application status is recorded.
The following table defines each field.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
node | Node name (new field added for JAR packages generated at and after 2019-05-20) | VARCHAR |
cpu | CPU utilization | DOUBLE |
memory | Current JVM memory status | BIGINT |
time | Record time (one record per minute) | BIGINT |
sessionNum | Number of live sessions (new field added for JAR packages generated at and after 2019-05-20) | BIGINT |
onlineNum | Number of online system users (new field added for JAR packages generated at and after 2019-05-20) | BIGINT |
pid | Process PID (new field added for JAR packages generated at and after 2019-05-20) | VARCHAR |
templateRequest | Number of template requests being calculated | INTEGER |
httpRequest | Total number of HTTP requests being processed | INTEGER |
sessionRequest | Number of sessionid-carried requests being processed | INTEGER |
fineIO | Off-heap memory occupied by FineIO, in KB (new field added for JAR packages generated at and after 2020-08-04) | BIGINT |
NIO | Off-heap memory occupied by NIO, in KB (new field added for JAR packages generated at and after 2020-08-04) | BIGINT |
bufferMemUse | Total used off-heap memory (equal to directMem「nio」plus mappedMem), in KB (new field added for JAR packages generated at and after 2020-08-04) | BIGINT |
physicalMemUse | Used physical memory, in KB (new field added for JAR packages generated at and after 2020-08-04) | BIGINT |
physicalMemFree | Available physical memory, in KB (new field added for JAR packages generated at and after 2020-08-04) | BIGINT |
fine_intelli_consume_point (Perform Information Table)
Performance information table: table to which performance-related information is recorded.
The following table defines each field.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | String |
time | Time Start time | Long |
id | Event tracking ID (X961 for FineBI) | String |
text | Resource content, which can be the template name or analysis table name (not used by FineBI) | String |
source | Event tracking source Original: class embed: current system plugin: plugin event tracking undefined: undefined source | Int |
username | Operator | String |
ip | Operation IP address | String |
title | Resource ID, which can be the template ID, analysis table ID, or table ID | String |
frFullVersion | FineReprot version | String |
biFullVersion | FineBI version | String |
cloudVersion | Cloud O&M version | String |
finish | End time Valid for FineReport and 0 for FineBI (not used by FineBI) | String |
consume | Time consumption, in milliseconds | String |
memory | Memory, in byte Valid for FineReport and 0 for FineBI (not used by FineBI) | String |
type | Operation type (not used by FineBI) | String |
comment | Resource remarks, which can be specific information or data to be analyzed directly (not used by FineBI) | String |
body | Specific event tracking information One JSON data structure, storing information by event tracking type | String |
fine_template_error (Execution Error Log Table)
The following table defines each field.

Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Error record time | BIGINT |
displayName | Name of the directory mounted to the platform (internationalized by the platform frontend) noPath: non-mount access | VARCHAR |
tname | Name of the faulty physical template (complete path under reportlets) | VARCHAR |
username | Template execution user (internationalized by the platform frontend) notLogged: access without login fromSchedule: scheduled dispatch | VARCHAR |
ip | IP address for template execution (empty for scheduled dispatch) | VARCHAR |
msg | Error information, including no specific error location and basically matching error codes (such as not displaying specific cells during cell infinite loop) | VARCHAR |
trace | Error stack, containing a maximum of 1000 characters (truncated if exceeding this limit) | VARCHAR |
code | Error code | VARCHAR |
para | Query parameters when an error occurs | VARCHAR |
result | Preview successful or not 1: yes 0: no | BIGINT |
platfromDisplay | Display level | BIGINT |
fine_config_operation (Deletion Monitoring Table)
Deletion monitoring table: table to which deletion of grouping, business packages, tables, and associations is recorded.
This table is added in 5.1.12 and later versions.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time | Long |
user | Username | VARCHAR |
resource_type | Resource type, including: Dashboard Grouping Business package Table Association | VARCHAR |
operate_type | Operation type (only deletion now) | VARCHAR |
info | Configuration information, including the table name, business package name, and group name. | VARCHAR |
thread_name | Thread name | VARCHAR |
fine_relationship (Lineage Analysis Table)
Lineage analysis table: table to which lineage data of data table-based dashboards is recorded.
This table is added in 5.1.14 and later versions. The table is empty by default.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Time | Long |
tableId | Table name | VARCHAR |
tableName | Escape name | VARCHAR |
engine | Engine in use | VARCHAR |
tableType | Table type: database: DB table sql: SQL table server: server dataset excel: excel table analysis: self-service dataset confAnalysis: edited base table | VARCHAR |
creatorName | Table creator | VARCHAR |
childTable | Subtable name | VARCHAR |
firstChild | Subtable directly from the parent table or not 0: no 1: yes | Long |
dashboardName | Dashboard name | VARCHAR |
dashboardId | Dashboard ID | VARCHAR |
fine_intelli_honeypot (Real-Time Event Tracking Table)
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
id | Event tracking ID | VARCHAR |
time | Log time | BIGINT |
addr | IP address | VARCHAR |
userName | Operator's username | VARCHAR |
tableId | Operation table ID | VARCHAR |
comment | Escape name of an operation object | VARCHAR |
target | Operation object | VARCHAR |
tableName | Operation table name | VARCHAR |
transferName | Operation remarks | VARCHAR |
describe | Parameter | VARCHAR |
fine_intelli_log_honeypot (Log Tracking Table)
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
id | ID | VARCHAR |
startTime | Error log time | BIGINT |
errorCode | Error code | VARCHAR |
time | Record time | BIGINT |
fine_update_task (Update Task Table)

Information in this table can be viewed in LogDB for FineBI projects of versions earlier than 5.1.12.
Information in this table can be viewed in FineDB for FineBI projects of 5.1.12 and later versions.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | string |
planId | Task instance's unique identifier (varied for each running) | string |
taskName | Task name Table name + Task type (single table/business package/global) | string |
startTime | Task start time | Long |
endTime | Task end time | Long |
runningResult | Completion status ALL: complete success PART: partial success | string |
state | Update status END: finished RUNNING: operating | string |
triggerType | Trigger method MANUAL AUTO | string |
roleId | Trigger person‘s ID | string |
roleName | Trigger person's name | string |
countOverView | Update status of various tables in the task, in JSON format expectBaseTableUpdate: expected number of base tables actualBaseTableUpdate: number of base tables successfully updated expectComplexUpdate: expected number of self-service datasets actualComplexUpdate: number of self-service datasets successfully updated expectRelationUpdate: expected number of associations updated actualRelationUpdate: actual number of associations successfully updated | string |
extra1 | Extra field 1 | string |
extra2 | Extra field 2 | string |
extra3 | Extra field 3 | string |
time | Data insertion time, required by Swift table cleaning | Long |
fine_update_task_detail (Update Task Detail Table)

For FineBI projects of versions earlier than 5.1.6, update task-related information is recorded in fine_DSGenerateFinishMap_SwiftTable (temporary table containing dataset update information) and fine_DSGenerate_SwiftTable (dataset update information table).
For FineBI projects of versions ranging from 5.1.6 to 5.1.11, update task-related information can be viewed in fine_update_task_detail (update task detail table) of LogDB.
For FineBI projects of 5.1.12 and later versions, update task-related information can be viewed in fine_update_task_detail (update task detail table) of FineDB.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | string |
planId | Task instance's unique identifier (varied for each running) | string |
loadId | Detail identifier, unique in an update task | Integer |
loadName | Name of the detailed information Table name + Package name for tables, and associated information for associations | string |
loadType | Detail type BASE: base table FAST/ETL: self-service dataset RELATION: association | string |
updateType | Update type FULL: full INCREASE: increment | string |
state | Update status LOADING: updating SUCCESS: success PART_SUCCESS: partial success WAITING: waiting in queue WRONG: failure | string |
endTime | Data update end time | Long |
effectTime | Effective time (time when updated tables are truly available) | Long |
startTime | Update start time | Long |
execption | Error information | string |
failedSonId | ID collection of tables failing to be updated due to the base table | string |
extra1 | Extra field 1 | string |
extra2 | Extra field 2 | string |
extra3 | Extra field 3 | string |
time | Data insertion time, required by Swift table cleaning | Long |
fatherFailedIds | ID collection of parent tables failing to be updated | string |
tableId | Extra field | string |
updateCount | Number of rows changed (possibly increase or decrease) (new field added in version 5.1.10) | Long |
errorCode | Error code (new field added in version 5.1.10) | Long |
totalCount | Total number of rows (new field added in version 5.1.10) | Long |
deleteCount | Number of rows incrementally decreased (new field added in version 5.1.10) | Long |
writeTime | File writing time (new field added in version 5.1.10) | Long |
etlFlow | Self-service dataset procedure (new field added in version 5.1.10) | string |
appendCount | Number of rows incrementally increased (new field added in version 5.1.10) | Long |
columns | Column (new field added in version 5.1.10) | Long |
jdbcTime | Data acquisition time (new field added in version 5.1.10) | Long |
openTime | Total SQL execution time (new field added in version 5.1.10) | Long |
infos | Non-error information (only internationalized key values and parameters) (new field added in version 5.1.10) | string |
performAnalysis Data Structure
Two structures, dashboard and data preparation, are available.

Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | String |
time | Long | |
type | Category type 0: dashboard 1: data preparation | Int |
user | Username | String |
startTime | Start time | Long |
endTime | End time | Long |
category | Dashboard/Table name | String |
subCategory | Component/Procedure name | String |
event | String | |
subEvent | String | |
exclusiveDuration | Time monopolized by the event | Long |
dataSource | Data source information | String |
query | Executed SQL clause | String |
row | Number of rows | Int |
contentSize | Occupied memory | Long |
exception | Exception information Recording exception information (if any) here can facilitate troubleshooting. | String |
additionalInfo | Additional information | String |
The following table lists events.
Event Category | Event Name | Definition | |
---|---|---|---|
Dashboard type:0 | cache | SpiderBaseCriteria | SQL L3 cache |
GroupCacheProcedure | Data L2 cache | ||
GroupPagingCacheProcedure | Pagination L1 cache | ||
crossPage | Pagination processing | ||
makeTree | Tree creation from two-dimensional tables | ||
postGroup | Re-summary by group after multiple indicators are selected | ||
treeSort | Tree-based sorting | ||
multiTarget(Old) | Multi-indicator calculation logic (old engine) possibly completed by multiple SQL queries | ||
multiTarget(New) | Multi-indicator calculation logic (new engine) possibly completed by multiple SQL queries | ||
Data preparation type:1 | previewData | Table data preview (not after clicking the edit button) | |
processResult | Preview of data in self-service datasets after clicking the edit button | ||
getData | Acquisition of previewed data from self-service datasets after clicking the edit button | ||
Public event type: 0/1 | sqlQuery | SQL data query | |
excelQuery | Excel data query | ||
getFields | Field information acquisition |
fine_engine_performance (Basic Information Table of Calculation Tasks)
Basic information table of calculation tasks: table to which event tracking information related to calculation time consumption is recorded, meeting engine performance tracking requirements.
This table is added in 5.1.22 and later versions.
Field | Definition | Data Format |
---|---|---|
uuid | User's unique identifier field | VARCHAR |
time | Record time | BIGINT |
queryId | Query ID | VARCHAR |
startTime | Start time | BIGINT |
endTime | End time | BIGINT |
engineType | Engine type 1: direct connect 2: extracted | INTEGER |
innerEngineType | Inner engine type | INTEGER |
baseStartTime | Start time of basic calculation | BIGINT |
baseEndTime | End time of basic calculation | BIGINT |
dataModelCol | Number of basic result columns | INTEGER |
dataModelRow | Number of basic result rows | INTEGER |
dataModelMem | Memory occupied by basic results | INTEGER |
peakMemory | Peak memory occupied by calculation results | BIGINT |
cacheHitType | Situation about data acquisition from cache | INTEGER |
cacheCost | Cache processing time | BIGINT |
matchType | Policy match situation 0: no match 1: rule match displayed but actually no match 2: rule match displayed and actually match | INTEGER |
parseTime | Parsing time consumption | BIGINT |
mergeCost | Merge time consumption after concurrent computing | BIGINT |
tableId | Dataset ID | VARCHAR |
widgetId | Component ID | VARCHAR |
widgetType | Component type | INTEGER |
dashboardId | Template ID | VARCHAR |
baseCriteria | Basic query information | VARCHAR |
extra | Extended field | VARCHAR |
executeType | Running status 0: success 1: error | INTEGER |