Overview
This document briefly describes data tables in the LogDB database and their fields.
Table | Name |
|---|---|
fine_record_execute | Report (FineBI) execution table |
fine_record_login | Login table |
fine_record_email | Email table |
fine_record_write | Data entry 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 lockout log table |
fine_record_security | Illegal session alert table |
fine_container_entity | Container information table |
fine_function_process | Function point information table |
fine_operation_process_log | Cloud O&M operation log table |
fine_schedule_record | Scheduled task execution log table |
fine_intelli_focus_point | Function event tracking table |
fine_real_time usage | Application real-time status table |
fine_intelli_consume_point | Performance information table |
fine_record_open_client_api | API and application ID table |
fine_cloud_execution_record | Cloud O&M execution record table |
fine_template_error | Execution error log table |
| fine_pretreat_job_result | Daily access statistics cache table |
fine_record_logout | Logout table For versions 11.0.13 and later, this table is deprecated, and its content is now recorded in the fine_record_login table. |
fine_record_error | Execution error log table For versions 11.0.1 and later, this table is deprecated, and its content is now recorded in the fine_template_error table. |
fine_operation_shutdown_record | Semaphore information table This table is deprecated, and its content is now recorded in the fine_intelli_focus_point table. |
fine_plugin_usage | Plugin information table This table is deprecated, and its content is now recorded in the fine_intelli_focus_point table. |
fine_tpl_info | Template attribute table This table is deprecated. |
fine_record_execute Report (FineBI) Execution Table
Table to which a record is added upon report access/export/printing, with corresponding information filled in the respective fields.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log start time | BIGINT |
id | Primary key | VARCHAR |
tname | Template path This field records the actual storage location of the template, i.e., the full path under reportlet. | VARCHAR |
forkId | Reused ID This field records the ID of the template reused by the current template. For example, you create a new template A, and template A is copied/saved as template B.
| VARCHAR |
displayName | Name of the directory in which a template is mounted on the decision-making platform (full path, including the parent directory) If the template is accessed directly via a link, this field is empty. | VARCHAR |
type | Report access method For details, see the following table. | INTEGER |
param | Parameter | VARCHAR |
ip | IP address for report execution | VARCHAR |
username | User who executes reports | VARCHAR |
userrole | Identity (department, role, etc.) of the user who executes reports | VARCHAR |
consume | Execution time consumption, including SQL execution time and report calculation time, in ms | BIGINT |
sql | SQL statement | VARCHAR |
sqlTime | Total SQL execution time | BIGINT |
browser | Version of the browser used by the client to access reports The access terminal can be determined by terminal in this field. browser: browser type/version OSInfo: operating system, which can be Windows, Mac, or Unix. terminal: client identifier, which can be App, H5, or an empty value.
| VARCHAR |
memory | Report-occupied memory, in bytes
| BIGINT |
reportId | Template ID | VARCHAR |
userId | User ID | VARCHAR |
complete | Whether the calculation is completed.
| INTEGER |
source | Access method
| VARCHAR |
sessionID | Session ID This field is used to link to the function event related to frontend rendering time consumption in the performance event tracking table (fine_intelli_consume_point). | VARCHAR |
node | Name of the node that loads templates You need to export the treasure package to see this field. | VARCHAR |
error | First error message during template execution You need to export the treasure package to see this field. | VARCHAR |
webInfo | Template execution information Recorded in array format: {"webResolution":"x*y","fullScreen":0}
| VARCHAR |
lastMod | Last template modification time | BIGINT |
detail | This field records the detailed information of the shared FineBI dashboard. | VARCHAR |
fineMarkId | ID of the device used to preview templates | VARCHAR |
estimate | This field records the actual estimated memory, in KB | BIGINT |
frFullVersion | FineReport version | VARCHAR |
biFullVersion | FineBI version | VARCHAR |
cloudVersion | Cloud O&M version | VARCHAR |
The following table describes the values of the type field.
Field Value | Description |
|---|---|
0 | Pagination preview |
1 | Online analysis |
2 | Data entry preview |
3 | FRM report preview |
4 | Row-based engine preview |
5 | Online editing (currently deprecated) |
6 | New data entry (currently deprecated) |
7 | New engine preview |
8 | FVS visualization dashboard preview |
9 | Developer debugging preview |
10 | Pagination export to Excel |
11 | Unaltered export to Excel |
12 | Full-page export to Excel, including the following scenarios: (1) Export to Excel via the large dataset export plugin (2) Pagination export or unaltered export to Excel with the row-based engine enabled |
13 | Pagination export to Excel by sheet |
14 | Export as PDF |
15 | Export to Word |
16 | Export as SVG |
17 | Export as CSV |
18 | Export to text |
19 | Export as JPG |
20 | Export as PNG |
21 | Export as GIF |
22 | Export as BMP |
23 | Export as WBMP |
24 | Export as a template with built-in dataset(s) |
25 | HTML content export |
26 | Data entry report's HTML content export |
27 | Exporting FineBI templates to Excel |
30 | Flash printing |
31 | PDF printing |
32 | Applet printing |
33 | Zero client printing |
34 | Local printing |
101 | Viewing FineBI templates |
102 | Editing FineBI templates (1) Record logic:
(2) Each editing event for the same dashboard triggers a record. |
103 | Sharing FineBI templates |
104 | Creating FineBI public links |
105 | Viewing FineBI public links |
106 | Exporting FineBI templates globally as PDF |
107 | Exporting FineBI templates globally to Excel |
108 | Exporting FineBI components to Excel |
109 | FineBI templates save as |
201 | Closing the browser or tab pages (FineBI) |
202 | Editing self-service datasets |
203 | Sharing self-service datasets |
204 | Disabling self-service dataset sharing |
205 | Disabling FineBI template sharing |
206 | Closing FineBI public links |
301 | Previewing components |
302 | Editing components |
401 | Previewing templates integrated with Excel plugins |
402 | Editing templates integrated with Excel plugins (reserved) |
403 | Sharing templates integrated with Excel plugins |
404 | Creating public links for templates integrated with Excel plugins |
405 | Accessing templates integrated with Excel plugins via public links |
408 | Exporting Excel components to Excel |
409 | Excel dashboards save as |
fine_record_login (Login and Logout Table)
This table records user login logs.
Field | Definition | Field Data Type |
|---|---|---|
uuid | 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 -1: Unknown login method 0: Default login 1: Cross-domain login 2: Remote design 3: Third party 4: Mobile terminal | INTEGER |
actionType | Operation type 0: Login 1: Logout 2: Timeout logout 3: Stay logged in | INTEGER |
authMethod | Authentication method -1: Unknown authentication method 0: Password 1: Verification code 2: Integration | INTEGER |
actionResult | Operation result 0: Success 1: Failure | INTEGER |
fine_record_email (Email Table)
This table logs email delivery records (limited to emails sent via the email button in the toolbar). Each time a report is sent by email, a new record is added to this table, with relevant email information recorded in the corresponding fields.
The following table defines each field.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
sender | Sender's username | VARCHAR |
receiver | Recipient's username | VARCHAR |
Recipient's mailbox | VARCHAR | |
ip | IP address for sending the email | VARCHAR |
username | User who sends the email | VARCHAR |
tname | Template path This field records the actual storage location of the template, i.e., the full path under reportlet. | VARCHAR |
displayName | Name of the directory in which a template is mounted on the decision-making platform (full path, including the parent directory) If the template is accessed directly via a link, this field is empty. | VARCHAR |
content | Mail content | VARCHAR |
time | Sending time | BIGINT |
result | Email sent successfully or not | BIT |
detail | Details | VARCHAR |
fine_record_write (Data Entry Table)
This table records data entry logs. Each time data is entered in a report, a new record is added to this table, with relevant information recorded in the corresponding fields.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | BIGINT |
ip | Data entry IP address | VARCHAR |
username | Data entry user | VARCHAR |
tname | Template path This field records the actual storage location of the template, i.e., the full path under reportlet. | VARCHAR |
displayName | Name of the directory in which a template is mounted on the decision-making platform (full path, including the parent directory) If the template is accessed directly via a link, this field is empty. | VARCHAR |
sql | Internal use The content recorded here is not the SQL statement for data entry. | VARCHAR |
sqlTime | Total SQL execution time | BIGINT |
browser | Type and version of the browser used by the client to access reports | VARCHAR |
result | Successful data entry or not 0: Failure 1: Success | BIT |
detail | Internal use The content recorded here is not the specific values for data entry. | VARCHAR |
consume | Execution time consumption This field includes SQL execution time and report calculation time. | VARCHAR |
body | This field uses the JSON data structure to record the following information: (1) key: fixed identifier of the request (2) value: (times, max, min, avg)
| VARCHAR |
frFullVersion | FineReport Version | VARCHAR |
biFullVersion | FineBI Version | VARCHAR |
cloudVersion | Cloud O&M version | VARCHAR |
fine_record_param (Common Parameter Combination Table of FineReport)
This table records common parameter combinations for FineReport templates.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | BIGINT |
templateid | Template ID | VARCHAR |
username | Username | VARCHAR |
pgroup | Common parameters used in templates The parameter values are encrypted and displayed in array format. {Parameter 1: value, Parameter 2: value} | VARCHAR |
fine_record_sms (SMS Sending Table)
SMS sending table: a table to which an SMS sending log is added when an SMS is sent, with related information recorded in the corresponding fields.
The following table defines each field.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | BIGINT |
receiver | Recipient's username | VARCHAR |
mobile | Recipient's phone number | VARCHAR |
content | Mail content | VARCHAR |
result | Email sent successfully or not | BIT |
detail | Details | VARCHAR |
sender | Sender's username | VARCHAR |
fine_record_operate (Management Log Table)
A record is added to this table when you operate a module, with corresponding information recorded in the respective fields.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | User's operation time | BIGINT |
type | Module (storing internationalization keys) | VARCHAR |
item | Setting item | VARCHAR |
resource | Accessed resource | VARCHAR |
operate | Operation | VARCHAR |
username | Username | VARCHAR |
ip | User's IP address | VARCHAR |
detail | Details | VARCHAR |
requestParam | Request parameter | VARCHAR |
platformDisplay | This field determines whether the log will be displayed in System Management > Intelligent O&M > Platform Log. 0: No display 1: Display | INTEGER |
STATUS | Operation successful or failed 0: Failed 1: Successful | INTEGER |
The following table lists common management log scenarios (the operation items are numerous and cannot be exhaustively enumerated).
Type | Module | Item | Operate |
|---|---|---|---|
Dec-Platform_Directory_Manage | Directory management | Dec-Directory: Directory Dec-Platform_Template: Report template | Dec-Log_Update: Update Dec-Log_Add: Add Dec-Log_Delete: Delete Dec-Log_Auto_Clean: Auto clean |
Dec-Module-User_Manager | User management | Dec-User | Dec-Log_Add: Add users Dec-User_Enable: Enable users |
Dec-Module-Privilege_Manager | Permission management | Dec-Basic_Global_Settings Dec-Authority_Set | Dec-Log_Recover_Inherit_Authority Dec-Log_Update: Update Dec-Log_Add: Add Dec-Log_Delete: Delete |
Dec-Module-Management_BI_Publish | Publication management | ||
BI-Tool_Data_Manage_Title | Public data management | ||
Dec-Module-Look_And_Feel | Appearance configuration | Dec-Look_Login_Page | Dec-Log_Update |
Dec-Manage_PlatformModule | System management | Dec-Basic_Login Dec-System_SMS | Dec-Log_Open Dec-Log_Close Dec-Log_Update |
Dec-Module-Simple_Scheduler | Task schedule | Fine-Schedule_Task | Dec-Log_Update: Update Dec-Log_Add: Add Dec-Log_Delete: Delete Dec-Log_Execute: Execute |
Dec-Mobile_Plate | Mobile platform | Dec-Mobile-Platform-Module_Directory | Dec-Log_Open Dec-Log_Close |
Dec-Module-Simple_Register | Registration management | Dec-Basic_Global_Settings Dec-Register_Info | Dec-Log_Export Dec-Log_Update |
Dec-Common-Help_Intelligence_Operation | Intelligent O&M | ||
Dec-Data_Connection | Data connection | Dec-Data_Connection_Manage Dec-Data_Connection Dec-Server_Table_Data | Dec-Basic_Preview Dec-Log_Test_Connection Dec-Log_Add |
Dec-Management_Plugin | Plugin management | Dec-Management_Plugin | Dec-Log_Update: Update Dec-Log_Add: Add Dec-Log_Delete: Delete |
Dec-Module-Security_Management | Security management | ||
Dec-Module-Template_Management | Template authentication | ||
Dec-Module-Management_Map | Map configuration | ||
Dec-BI_Resource_Handover | Resource handover | ||
ESD_Title | Extracted data cache | ESD_Global-Config | Dec-Log_Update |
fine_record_sql (SQL Execution Table)
This table records SQL execution.
Note:The fine_record_sql table stores only the SQL calculation process of the FineReport templates (rather than that of FineBI templates).
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | BIGINT |
executeid | Execution batch ID The same batch ID is used for batch-executed SQL statements during each preview/query. | VARCHAR |
dsname | Dataset name | VARCHAR |
sqltime | SQL execution time, in milliseconds | BIGINT |
rows | Dataset scale field, which records the row quantity | BIGINT |
columns | Dataset scale field, which records the column quantity | BIGINT |
connectionID | Data connection ID This field is used to link with the events related to the data source connection in the function event tracking table (fine_intelli_focus_point). | VARCHAR |
connection | Data connection name | VARCHAR |
fine_record_gc (GC Record Table)
This table records the system's GC information.
Field | Definition | Field Data Type |
|---|---|---|
uuid | 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 types (GC and 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 | Calculation abort score | 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-defined node name Empty in standalone mode | 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)
This table records partial configuration information in the fine_conf_entity table.
Field | Definition | Field Data Type |
|---|---|---|
uuid | 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)
This table logs user lockout events, and the frontend table is displayed under System Management > System Setting > Login > Login Lock Setting.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | BIGINT |
lockItem | Lockout object | VARCHAR |
lockTime | Lockout time | VARCHAR |
autoUnlockTime | Automatic unlock time | VARCHAR |
fine_record_security Invalid Session Alarm Table
This table is added in version 11.0.30 and later, which records invalid sessions of unauthorized users, helping admins detect and respond to malicious attacks.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | BIGINT |
user | Username | VARCHAR |
ip | User IP | VARCHAR |
level | Severity of invalid session 1: Critical (most severe) 2: Suspicious 3: Warning | INTEGER |
name | Invalid session type
| VARCHAR |
module | Affected functional modules 1: Report 2: Platform 3: Reports and platform | INTEGER |
msg | Error message, which displays different error messages based on the invalid session types
| VARCHAR |
fine_container_entity (Container Information Table)
This table records container information.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | BIGINT |
node | Node name | VARCHAR |
item | Configuration Item | VARCHAR |
value | Configuration item's value | VARCHAR |
fine_function_process (Function Information Table)
This table records function information.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | BIGINT |
function | Function | VARCHAR |
fine_operation_process_log (Cloud O&M Log Table)
This table records cloud O&M logs.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | BIGINT |
node | Node name | VARCHAR |
process | Log content | VARCHAR |
fine_schedule_record (Scheduled Task Execution Log Table)
This table records scheduled task execution information.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | BIGINT |
id | Primary key UUID | VARCHAR |
creator | Creator | VARCHAR |
detailMessage | Details | VARCHAR |
filePath | Path of generated attachments Reserved field, unused | 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 Reserved field, unused | BIGINT |
runType | Attachment processing type 0: Snapshot generation 1: Email sending 2: FTP upload 3: Message push 4: File printing 5: SMS sending 6: Platform mounting 7: Customized type 8: Regular data entry 9: Client notification 10: SFTP upload | INTEGER |
taskName | Task name | VARCHAR |
taskID | Task ID | VARCHAR |
fine_intelli_focus_point (Function Event Tracking Table)
All public function event tracking information is saved in this table.
Field | Definition | Field Format |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | DATE |
id | Function event tracking ID 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) | VARCHAR |
Text | Main content recorded | VARCHAR |
source | Event tracking source -1: Undefined source (UNDEFINED) 1: Functions of the built-in JAR package (EMBED) 2: Plugin functions (PLUGIN) 4: FineReport functions (REPORT) 8: FineBI functions (BI) | INTEGER |
username | Username Transcoded (0 for the super admin) | VARCHAR |
ip | IP address that triggers event tracking | VARCHAR |
title | Title (tracked event) | VARCHAR |
body | JSON data structure, which stores information about different functions based on their IDs Secondary information, which may be empty | VARCHAR |
frFullVersion | FineReport version | VARCHAR |
biFullVersion | FineBI version | VARCHAR |
cloudVersion | Cloud O&M version | VARCHAR |
fine_real_time_usage (Real-Time Application Status Table)
This table records real-time application status, with one record per minute.
Field | Definition | Field Format |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time (one record per minute) | BIGINT |
node | Node name | VARCHAR |
cpu | CPU utilization | double |
memory | Current JVM memory status | BIGINT |
sessionnum | Active session count | BIGINT |
onlinenum | Number of online system users | BIGINT |
pid | Process PID | VARCHAR |
templateRequest | Number of template requests being calculated | INTEGER |
httpRequest | Total number of HTTP requests being processed | INTEGER |
sessionRequest | Number of requests carrying session IDs being processed | INTEGER |
fineIO | Off-heap memory occupied by fineIO Unit: KB | BIGINT |
NIO | Off-heap memory occupied by NIO Unit: KB | BIGINT |
bufferMemUse | Total used off-heap memory directMem「nio」and mappedMem Unit: KB | BIGINT |
physicalMemUse | Used physical memory Unit: KB | BIGINT |
physicalMemFree | Free physical memory Unit: KB | BIGINT |
fine_intelli_consume_point (Performance Information Table)
This table records system performance-related information.
Field | Definition | Field format |
|---|---|---|
uuid | Unique identifier field | String |
time | Log record time | long |
id | Performance event tracking ID | String |
text | Resource content Template name, analysis table name, etc. | String |
source | Source of event tracking, defined by description in the Original class 1: Current system 2: Plugins 4: FineReport 8: FineBI 32: Jiushuyun -1: 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 | FineReport version | String |
biFullVersion | FineBI version | String |
cloudVersion | Cloud O&M version | String |
finish | End time | String |
consume | Time consumption, in milliseconds | String |
memory | Memory, in bytes | String |
type | Operation type, which indicates the type of the performed operation | String |
comment | Resource remarks, which can be more specific information or data to be analyzed directly | String |
body | Specific event tracking information in a JSON data structure, storing different information according to the event tracking type | String |
fine_template_error (Execution Error Log Table)
Note:Field | Description | Data Format |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | BIGINT |
displayName | Name of the directory in which a failed template is mounted on the decision-making platform (full path, including the parent directory) If the template is accessed directly via a link, this field is empty. | VARCHAR |
tname | Template path This field records the actual storage location of the failed template, i.e., the full path under reportlet. | VARCHAR |
username | User who executes the template notLogged: access without login fromSchedule: scheduled task | VARCHAR |
ip | IP address for template execution If the scheduled task is faulty, this field is empty. | VARCHAR |
msg | Error information This field provides information that basically corresponds to error codes, without specifying the error location. For example, it may indicate a circular reference without identifying specific cells. | VARCHAR |
trace | Error stack This field contains a maximum of 1,000 characters (truncated if the length exceeds 1,000 characters). | VARCHAR |
code | Error code -1 represents no error code. | VARCHAR |
para | Parameter for query when an error occurs | VARCHAR |
result | Successful preview or not 0: Failed preview 1: Successful preview | BIGINT |
platformDisplay | This field determines whether the log will be displayed in System Management > Intelligent O&M > Platform Log. 0: No display 1: Display | BIGINT |
fine_pretreat_job_result Daily Access Statistics Cache Table
Note:Every day at midnight, the Swift engine runs a scheduled task to query the previous day’s statistics, including daily visits, daily active templates, and daily active users, and caches the results in this table.
task in the field names refers to this specific scheduled task.
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | BIGINT |
taskId | Task ID | VARCHAR |
taskResult | Query results: including daily active users, daily active templates, and daily visits | VARCHAR |
taskCondition | Query conditions: Task type + Query time range | VARCHAR |
taskType | Task type | VARCHAR |
fine_cloud_execution_record Cloud O&M Execution Record
Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Log record time | BIGINT |
node | Nodes in the cluster project | VARCHAR |
name | Name of the running task | VARCHAR |
module | Business module name
| VARCHAR |
action | Execution type COLLECT: Event collection EXPORT: Event export | VARCHAR |
metricType | Event type
| VARCHAR |
startTime | Start time | BIGINT |
endTime | End time | BIGINT |
consume | Time consumption, in milliseconds | BIGINT |
Deprecated Tables
Due to content integration or functional changes, the following tables are now deprecated and no longer record relevant information.
For data security reasons, FanRuan does not delete any historical tables, so you can still view the related tables in the product, but no more content will be written to them.
fine_record_logout (Logout Table)
Note:Field | Definition | Field Data Type |
|---|---|---|
uuid | 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_error (Execution Error Log Table)
Note:Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
displayName | Name of the directory in which a template is mounted on the decision-making platform (full path, including the parent directory) If the template is accessed directly via a link, this field is empty. | VARCHAR |
ip | IP address for report execution | VARCHAR |
msg | Error information | VARCHAR |
time | Error record time | DATE |
tname | Path of the faulty template This field records the full path under reportlet. If the error is not caused by a template, this field records a non-template-triggered error. | VARCHAR |
trace | Error path | VARCHAR |
username | User who executes the report | VARCHAR |
userrole | Role of the user who executes reports | VARCHAR |
errorcode | Error code If there is no error code, this field is empty | VARCHAR |
platformDisplay | This field determines whether the log will be displayed in System Management > Intelligent O&M > Platform Log. 0: No display 1: Display | INTEGER |
fine_operation_shutdown_record (Semaphore Information Table)
This table records the semaphore information.
Note:Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | 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)
This table records plugin information.
Note:Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | 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_tpl_info (Template Attribute Table)
Note:Field | Definition | Field Data Type |
|---|---|---|
uuid | Unique identifier field | VARCHAR |
time | Record time | BIGINT |
id | ID | VARCHAR |
tid | Template ID | VARCHAR |
tname | Physical template path This field records the full path under reportlet. | 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 | Whether the freezing function is used | BIT |
isfoldtree | Whether the collapsible tree is used | BIT |
widgetnums | Number of widgets | BIGINT |
tsize | Total template size | BIGINT |
imgsize | Size of an 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 |