反馈已提交
网络繁忙
This article will briefly introduce the meaning of each data table and table field in the Logdb database.
surface
name
fine_record_execute
BI execution table
fine_record_login
login form
fine_record_logout
logout form
fine_record_email
mailing list
fine_record_write
Fill out the report
fine_record_error
Execution error log table
fine_record_param
Common parameter combination table
fine_record_sms
SMS sending form
fine_record_operate
Manage log tables
fine_record_sql
SQL execution table
fine_record_gc
GC log sheet
fine_record_conf
Part of the configuration information table
fine_record_lock
User lock log table
fine_tpl_info
Template property sheet
fine_container_entity
Container Information Sheet
fine_function_process
Function point information table
fine_operation_process_log
Cloud operation and maintenance operation log table
fine_operation_shutdown_record
Semaphore Information Table
fine_plugin_usage
Plugin Information Sheet
fine_schedule_record
Scheduled task execution log table
fine_config_operation
delete behavior monitoring table
fine_relationship
blood relationship analysis table
fine_intelli_honeypot
Instant burial table
fine_intelli_log_honeypot
log entry table
fine_update_task
Update task list
fine_update_task_detail
Update task schedule
performAnalysis
data structure
fine_intelli_focus_point
Function Buried Point Table
fine_real_time_usage
Application Live Fact Sheet
fine_intelli_consume_point
Performance Information Sheet
BI execution table: report access/export/print log, that is, if the report is accessed/exported/printed, a record will be added to the table, and the corresponding information record will be filled in the corresponding field.
The corresponding meanings of each field are shown in the following table:
field
meaning
Remark
Field Type
id
primary key
VARCHAR
tname
Dashboard storage path
displayName
The name of the directory to mount to the platform
record directory full path
Empty if the link is accessed directly
type
Report access method
The details are listed in the table below
The range is 0~105, and 33 codes have been used so far
INTEGER
param
Record the shared node name
2020-08-04 and later JARs have a value for this field
If the shared node is a multi-level department, the record format is: 1-level node/2-level node/node
Record one row of data per share, only record, but not export
ip
Operator IP
Only log, but not export
username
User who executed the report
userrole
User role to execute the report
consume
time consuming to execute
Including SQL execution time and report calculation time
The unit is ms
BIGINT
time
log start time
sql
SQL statement
sqlTime
Total time for SQL execution
FR valid field, 0 for BI Dashboard, not used by BI
browser
The browser version used by the client to access the report
5.1.11 and later versions, you can use the terminal in this field to determine the access terminal
browser: browser type and version
OSInfo : Operating system, divided into Windows, Mac, Unix
terminal: Client ID, divided into PC, App, H5
PC: The access terminal is the PC side
App: The access terminal is FanRuan App/HTML5 terminal to access the public link
H5: HTML5 side access to non-public link templates
memory
Report occupies memory, unit B
reportId
Template number
userId
User ID
complete
Whether the calculation is complete
source
interview method
sessionID
session id
the front-end rendering time-consuming related points in the performance point table ( fine_intelli_consume_point )
node
The node name of the loaded template
treasure package needs to be exported. For details, please refer to: Cloud operation and maintenance steps
error
The first error message during template execution
webInfo
Template execution information
webResolution : The resolution of the current template execution when accessed on the front end, the record format is x*y
fullScreen : Whether the current template execution is in full screen mode when accessed on the front end, the record format is 1/0
Note: The node, error, and webInfo fields need to be updated to the JAR package of 2021-03-17 and later versions.
The specific meaning of the field type:
coding
parameter
0
Pagination preview
page
1
Online analysis
view
2
Fill in the preview
write
3
Decision report preview
form
4
line engine
layer
5
online editing
edit
6
new report
write_plus
7
New engine preview
page_plus
10
Excel Paginated Export
excel
11
Export to Excel as is
excelO
12
Excel full page export
excelL
13
Excel pagination and sheet export
excelS
14
PDF export
pdf
15
Word export
word
16
SVG export
svg
17
CSV export
csv
18
Text export
text
19
JPG image export
jpg
20
PNG image export
png
21
GIF image export
gif
22
BMP image export
bmp
23
WBMP image export
wbmp
24
Built-in dataset export templates
cpt
25
HTML export
html
26
Fill out HTML export
write_html
27
BI Export Excel
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
View BI Templates
bi_view
102
Edit BI templates
1) Recording logic: Click on a dashboard to enter the editing state, wait for the page to be fully loaded, no matter how many operations are performed or no operations are performed, record it once; next time, click on the template to edit or refresh the web page to record the second time
2) The same dashboard, each edit will have a record
bi_edit
103
Share BI templates
bi_share
104
Create BI public link
bi_create_publink
105
View BI public link
bi_view_share
106
BI template global export PDF
bi_template_export_pdf
107
BI template global export to Excel
bi_template_export_excel
108
BI component export to Excel
bi_component_export_excel
109
BI template save as
201
Close the browser or tab page (BI)
202
Edit Self-Service Datasets
203
Share self-service datasets
bi_analysis_table_share
204
Close Share Self-Service Datasets
205
Close Share BI Template
206
Close BI public link
Login table : User login log, used to record user login information.
Log in time
Login IP address
logged in user
logged in user role
Logout table : User logout log, used to record user logout information.
User exit the platform time
logout IP address
Username to log out of the platform
User role to log out of the platform
Mail table : Mail sending log (only includes "Mail" in the toolbar), that is, if the report sends mail, a record will be added to the table, and the corresponding information record will be filled in the corresponding field.
receiver
recipient username
mail
recipient email
The IP address from which the email was sent
the user who sent the email
The actual name of the dashboard, not the name of the dashboard in Catalog Management
content
content of email
send time
result
Is it sent successfully
BIT
detail
Details
Fill in the report : record the log information of the report, that is, if the report is filled out, a record will be added to the table, and the corresponding information record will be filled in the corresponding field.
User who filled out the report
Fill in time
Whether the filling is successful
The IP address for filling in the report
Execution time, including SQL execution time, report calculation time
1) Key: request fixed flag
2）value：(times, max,min,avg)
Times: occurrence times of this type of request, unit: Times
Max: maximum response time of this type of request, unit: ms
Min: minimum response time of this type of request, unit: ms
AVG: average response time of this type of request, unit: ms
Execution error log table : that is, if an error is reported during the execution of the report, a record will be added to the table, and the corresponding information record will be filled in the corresponding field to record all error and fatal level error messages.
Note: finebi5.1.19 and later, fine_ record_ Error is no longer used, and the error information is recorded in fine_ template_ Error table.
The IP address where the report is executed
msg
error message
Error record time
DATE
Incorrect dashboard storage path
If it is not a template error, tname is logged as "non-template trigger error".
trace
wrong path
errorcode
error code
Empty when there is no error code
platformDisplay
Whether to show in the platform
1 - yes
0-no
There is an error log recorded to this table, this field is recorded as 1, otherwise this field is recorded as 0
Filter the display in the error log of the platform log, and only display the records with platformDisplay =1.
Common parameter combination table : record common parameter combination log information.
Note: fine_ record_ Param table is a common parameter table of fr
templateid
Dashboard ID
user
pgroup
Parameters, values are displayed in array form:
{parameter1: parameter value, parameter2: parameter value}
2020-02-28 and later JAR, pgroup field value encrypted display
record time
SMS sending table : record the message sending log information, that is, if sending a short message, a record will be added to the table, and the corresponding information record will be filled in the corresponding field.
mobile
Receiver's mobile phone number
sender
sender username
Management log table: that is, when the user operates the module, a record will be added to the table, and the corresponding information record will be filled in the corresponding field.
Module (stores internationalized keys)
item
setting item
resource
Accessed resource
operate
User IP address
User operation time
requestParam
request parameters
Platform display level
status
success or failure of this operation
The specific scenarios that need to be recorded are shown in the following table:
TYPE-module
ITEM-settings
RESOURCE - Accessed resource
OPERATION - Operation
DETAIL-details
Directory management
"node full path"
add/delete/modify
template
Link
escalation label
User Management
Global Settings
change
"name (username)"
department
"Department-wide path"
Under the department
"Job Full Path"
add/delete
Position
"position Name"
Person under the post
"Job Title" - "Name (Username)"
Role
"Role Name"
Personnel under the role
"role name" - "name (username)"
Platform users
BI view only users
BI editor user
mobile platform users
authority management
Permission settings
"Department/Role/Name (Username)"
Permission Item: "Directory/Data Connection/Business Package/Manageable Department Role" Type: View/Authorize/Edit
Permission reuse
"Effective object [department/role/name (username)]"
multiplex
Source: "Department/Role/Name (Username)" Type: "Permission Item"
System Management
Log in
single sign-on
switch
Single sign-on setup
Last login information prompt
Forgot password
SMS verification
conventional
General parameters
BI parameters
Print
Print Settings
Short message
SMS platform
account binding
Mail
sender account
Backup restore
Global configuration
Platform configuration
automatic backup
backup file
Add/Delete/Restore
report template
BI template
jar package
plugin
Update and upgrade
jar package update
renew
jar package restore
reduction
Backup jar package
delete
Platform log
log settings
access details
export
user behavior
Template heat
performance monitoring
memory management
Intelligent early warning
memory session
"name (username)" - "template path"
Finish
Smart release
Template restrictions
The life cycle
Data Connections
"Data Connection Name"
registration message
Public cloud authentication/private cloud authentication/upload lic file
safety management
SQL injection prevention
Disable special keywords
Disabled special keywords
escape character
escaped character
Scheduled
timed task
"mission name"
Multi-level reporting
Reporting process
"process name"
escalate task
"task name"
mobile platform
Authorized device
QR code configuration
Template authentication
Permission item: "Template Path" Type: View/Fill
Remote Design Permission
Changed permission item: "template path"
Plugin management
"plugin name"
install/remove/enable/disable/update
SQL execution table: records the execution of SQL.
Note: fine_ record_ The SQL table does not store the SQL records of the Bi template, but only the SQL calculation process of the report engine.
columns
dataset size
number of record columns
dsname
the name of the dataset
executeid
execution table id
rows
number of records
sqltime
SQL execution time
Unit: milliseconds
connection
data connection name
connectionID
data connection ID
with the data source connection related points in the function point table ( fine_intelli_focus_point )
GC record table: record the GC information of the system.
heapBeforeUsed
Heap memory usage before GC
heapAfterUsed
heapBeforeCommitted
Heap request memory after GC
heapAfterCommitted
gcStartTime
GC start time
duration
GC duration
gcCause
Reasons for GC
Common causes are: System.gc () , allocation failure, humongous
gcType
GC type
Divided into Young GC and Full GC
metaspaceBeforeUsed
metaspace GC
metaspaceBeforeCommitted
metaspaceAfterUsed
metaspaceAfterCommitted
balancePromoterScore
stop score
youngBeforeUsed
Memory used before young generation GC
youngBeforeCommitted
Allocate memory before young generation GC
youngAfterUsed
Memory usage after young generation GC
youngAfterCommitted
Allocating memory after young generation GC
loadScore
Overall Load Score
User named node name
Standalone is empty
oldBeforeUsed
Memory used before old generation GC
oldBeforeCommitted
Allocate memory before old age GC
oldAfterUsed
Memory usage after old generation GC
oldAfterCommitted
Allocating memory after old age GC
pid
process pid
releasePromoterScore
release points
Record some configuration information in fine_conf_entity.
configuration item
value
Configuration item value
log user lockout
warehousing time
lockItem
lock object
lockTime
lock time
autoUnlockTime
Auto unlock time
record template properties
Note: This table has no practical use and is only for backup. So no data will be recorded in the table.
serial number
tid
template id
Physical template name
Record the full path under the reportlet
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 , value formulas
submitnums
Number of built-in commits
isfrozen
whether to use freeze
isfoldtree
whether a folded tree is used
widgetnums
Number of controls
tsize
total template size
imgsize
The size of the image in the template
execute0
Engine Condition Summary 0
execute1
Engine Condition Summary 1
execute2
Engine Condition Summary 2
execute3
Engine Condition Summary 3
execute4
Engine Condition Summary 4
mem0
Summary of memory conditions 0
mem1
Summary of memory conditions 1
mem2
Memory situation summary 2
mem3
Memory situation summary 3
mem4
Memory situation summary 4
sql0
sql situation summary 0
sql1
sql situation summary 1
sql2
sql situation summary 2
sql3
sql situation summary 3
sql4
sql situation summary 4
filternums
number of filters
injectnums
The number of parameter injections
formula
Use of formulas in templates
jsapi
JS API usage in templates
recordtime
Template detection time
record container information
node name
Record function point information
function
function points
Record cloud operation and maintenance operation logs
process
log content
record semaphore information
Note: fine_ operation_ shutdown_ Record and fine_ plugin_ Usage integrated into fine_ intelli_ focus_ Point table
Process ID
startTime
Starting time
upTime
deadline
signalName
signal name
Log plugin information
plugin name
version
Plugin version
API
Interface usage in plugins
operation
Plugin operation
register
Plug-in registration
enable
Whether the plugin is enabled
Record timing task execution information
UUID
creator
-
detailMessage
details
filePath
Generate attachment path
reserved field, unused
logMessage
log information
logTime
task execution time
log print time
logType
log type
0 - fail
1 - Success
2- Skip
nextFireTime
next recording time
runType
Attachment Handling Type
0 - snapshot generation
1- Mail sending
2-FTP upload
3-Message push
4-File printing
5-SMS sending
6-Platform mount
7- Custom class
8- Timely fill in the report
9- Client Notification
10-SFTP upload
taskName
mission name
taskID
task id
Function burial point table: used to save all public burial point information.
Buried point ID number
Main content of the record
Buried point source
-1 - no source defined (UNDEFINED)
1- Function point of built-in JAR package (EMBED)
2-Plug-in function point (PLUGIN)
4- FineReport 's function points (REPORT)
8- Function Points (BI) of FineBI
Transcoding processing, super user is 0
The IP of the departure point
title
title, what's the point
body
a JSON data structure
Store the information of different function points according to the function point ID
secondary information, may be empty
Field id format description:
Example: FR-P1001
FR prefix, indicating that it is the buried point of FR.
The first letter indicates function/performance: F-function, P-performance.
The second digit indicates the classification: 1-data source, 2-frontend, 3-error, 4-intelligent operation and maintenance, 5-designer.
The relationship between the field id and body in the table is shown in the following table:
effect
FR-P1001
id: data connection ID
version: data source version
driver: connection driver information
times: times of use
connecttime : the time the connection was created
Used to log data connection related information
FR-F3001
Record the specific error stack
Record the cause of the project startup failure error message
FR-F4001
Example of the first version of the plug-in record: {node:2,memory:16,situation:normal,inform:1,type:auto}
node is the recommended number of nodes (referred to as 1 when a single machine is recommended)
memory is the recommended single machine/single node memory
situation is the recommended situation: when it is marked as "normal", it is a normal recommendation, when it is "error", it is an abnormal situation of the recommended value, when it is " inequacy ", it is a situation where the running data is insufficient, and when it is "nonsupport", the recommended configuration is not supported. Among them, in the "normal" case, node and memory have values, and in other cases, node and memory are recorded as empty.
inform is whether the notification has been made, recorded as 1 for notified, and 0 for not notified
type is the recommended type, marked as "auto" is the result of recommendation based on the running data of a natural day, marked as "manual" is the result recommended by the user access interface link
Recommended values for memory configuration
FR-F4002
Record example: { sessionid : xxxxxx , reason: release, detail: row count, load: high load, cell num: 100000, survival time: 600000}
sessionid : the session id being cleared
reason: Category of the reason why the session was cleared. Including life (life cycle), limit (template limit), release (smart release) three items
detail: the detailed reason why the session was cleared
When reason is recorded as life, this record is empty.
When reason is recorded as limit, this record is: row count (limit of rows in a single data set), cell count (limit of cells in a single template), sql time ( limit of sql execution time), excel cell count (limit of imported Excel cells) ), commit row count (commit record number limit), cartesian (fill in Cartesian product limit)
When reason is recorded as release, this record is: stop calculating
load: The load status of the system when the session was killed. Including endanger (dangerous state), terrible load (ultra-high load), high load (high load), normal load (medium and low load)
cell num: the number of cells that have been calculated
survival time: survival time
Logs when sessions are cleared due to lifetime, template limits, and stops computing at high load
FR-F4003
Record example: {type: high load kill, kill num time: 50, kill num cell: 50, session num: 300, load: terrible load}
type: including high load kill (small kill), terrible load kill (big kill), remove all (super kill to clear all sessions)
kill num time: The number of sessions killed due to not updating for a long time. When the type is removeAll , it is recorded as empty
kill num cell: The number of sessions killed due to too many cells. When the type is removeAll , it is recorded as empty
kill num sum: the sum of the number of sessions killed
session num: the total number of sessions before releasing the session
Record the release session triggered by the GC callback
FR-F5001
Example record: {disk_beforegc:50, disk_aftergc:50}
Record template version management GC cleanup
FR-F5002
node: node name
time: process shutdown time
pid : process pid
startTime : Process start time
upTime : Process duration
signalName : semaphore
System shutdown record: record the process information and shutdown type before and after system shutdown
FR-F5003
containerMem : The memory size set by the container
cpu : the number of CPU cores
disk: total disk space
diskUsed disk used space
jdkVersion : JDK version
containerVersion : Web container version
machineMem : physical machine memory
system: server operating system
systemNum : Server OS Bits
arch: processor architecture, such as x86_64, x86
diskSpeed : disk access speed
FRbuildNO : the jar package version of FR
BIbuildNO : BI jar package version (record the BI jar package version, if BI is not used, record it as empty)
serverType : server type (cloud represents cloud server, local represents local server)
gcType : garbage collector type
Container configuration: configuration information of the container and server where the application is located. record once a day
FR-F5004
licType : registration type
expireTime : registration expiration time
CTRID: Contract ID
companyId : Company ID
productVersion : product version
platformUserNum : the number of users
User basic information: the user's registration information and other content. record once a day
FR-F5005
tid : Template ID
tName : Physical template name ( full path under reportlets )
cNums : the number of conditional attributes
formNums : the number of formulas
sheetNums : the number of multiple sheets
dsNums : the number of datasets
compFormNums : The number of complex formulas (including hierarchical coordinates, SQL, and Value formulas)
submitNums : the number of built-in submissions
isFrozen : whether freezing is used
isFoldTree : whether a folded tree is used
widgetNums : the number of controls
filterNums : number of filters
injectNums : the number of parameter injections
formula: formula usage in the template
jsAPI : In-template JS API usage (limit record to 255 characters)
tSize : total template size
imgSize : The size of the image in the template
lineEngine : whether to enable the line engine (1 is enabled, 0 is not enabled)
execute0-execute4: 5-level segmented record of execution time
mem0-mem4: 5-level segmented record of memory usage
sql0-sql4: 5-level segmented record of SQL execution time
Template attribute information: record the information of the template, each template outputs one record per day
FR-F5006
id: the location of the data in the configuration
value: data value
Configuration information: record specific information in the fine_conf_entity table in FineDB once a day
FR-F5007
plugin: plugin name
version: plugin version
API: The interface used in the plug-in
opration : plugin operation status
register: plugin registration status
enable: whether the plugin is enabled
Plugin usage: the usage of plugins, each plugin is recorded once a day
FR-F5008
function: Purchase status of function points
Purchase of function points: Purchase of function points, recorded once a day
Application real-time situation table: record application real-time situation.
2019-05-20 and later JAR new fields
cpu
CPU utilization
DOUBLE
Current JVM memory situation
Record time, one per minute
sessionNum
Number of live sessions
onlineNum
Number of people online
Process PID
templateRequest
Counting template requests
httpRequest
The total number of http requests being processed
sessionRequest
Number of requests with sessionid being processed
fineIO
fineIO occupies off-heap memory size
Unit KB
2020-08-04 and later JAR new fields
NIO
NIO occupies off-heap memory size
bufferMemUse
Total memory used off-heap
directMem " nio " and mappedMem
physicalMemUse
Physical memory used space
physicalMemFree
Physical memory free space
Performance Information Sheet: Records performance-related information.
Buried point id number
BI is X961
Resource content
Inside the Original class
embed: Indicates the current system
plugin: Indicates the buried point of the plugin
undefined: indicates that no source is defined
End Time
FR valid field, BI is 0, this field is not used by BI
Time-consuming unit ms
Memory size unit byte
Operation type
It is possible to indicate which operation was performed. BI does not use the field
comment
Resource Notes
It can be more specific information, data that needs to be analyzed directly. BI does not use the field
Bury specific information
A JSON data structure that stores different information according to different buried points
field name
Data Format
uuid
Unique identification field of the user
Error recording time
The name of the directory mounted to the platform. The front-end processing of the platform is internationalized
Nopath: indicates non mounted access
The user who executes the template, and the platform front-end processing is internationalized
Notlogged: no login access
Fromschedule: scheduled scheduling
Error stack
Length 1000 characters, exceeding truncation
Preview successfully
1: Preview succeeded
0: preview failed
Record grouping, business package, table, a ssociated delete operations
This table is added in 5.1.12 and later versions.
Long
resource_type
Resource types, including:
Dashboard
grouping
business package
association
operate_type
Operation type, currently only delete operations are recorded
info
Configuration information, table name, business package name, group name, etc.
thread_name
thread name
Record bloodline data for the data table dashboard.
This table is added in 5.1.14 and later versions.This table is empty by default. The contents of this table will appear only after the administrator performs synchronization data in the blood relationship analysis function of dashboard in Bi tools.
tableId
Table Name
tableName
escaped name
engine
use engine
tableType
Table type:
database
server
analysis
confAnalysis
creatorName
table creator
childTable
child table name
firstChild
Is it a direct child table
0: not a direct child table
1: is a direct child table
dashboardName
Dashboard name
dashboardId
Field format
definition
Buried point ID
log time
addr
userName
Operation username
Action table ID
Operation object escape name
target
Operation object
Action table name
transferName
Operation Notes
describe
ID
Error log time
errorCode
Note: For BI projects before 5.1.12, this part of the information can be viewed in LogDB .
For BI projects of version 5.1.12 and later, this part of the information can be viewed in FineDB .
planId
The unique identifier of the task instance, which is different for each run
string
Table name + task type (single table/business package/global)
task start time
endTime
task end time
runningResult
finished condition
ALL: All successful
PART: Partial success
state
update status
END: has ended
RUNNING: run
triggerType
Trigger method
MANUAL: Manual
AUTO: timing
roleId
Trigger Id
roleName
Trigger name
countOverView
The update status of each type of table in the task . JSON
expectBaseTableUpdate expects the number of base tables
actualBaseTableUpdate the actual number of base tables that were successfully updated
expectComplexUpdate expected number of bootstrap datasets
actualComplexUpdate actual number of successful bootstrap datasets
expectRelationUpdate expected number of association updates
actualRelationUpdate actual number of successful associations
extra1
extra field 1
extra2
extra field 2
extra3
extra field 3
Data insertion time, swift table cleanup required
Note: For BI projects before 5.1.6 , the information related to the update task is recorded in fine_DSGenerateFinishMap_SwiftTable (dataset update information temporary table) and fine_DSGenerate_SwiftTable (dataset update information table)
For BI projects between 5.1.6 and 5.1.11, this part of the information can be viewed in the fine_update_task_detail (update task detail table) of LogDB .
For BI projects of version 5.1.12 and later, this part of the information can be found in FineDB View in fine_update_task_detail (update task detail table) .
loadId
Detail ID, unique within an update task
Integer
loadName
name of detail
The table is the table name + package name, and the association is the associated information
loadType
detail type
BASE: base table
FAST, ETL: Self-Service Datasets
RELATION: Relation
updateType
update type
FULL: full amount
INCREASE: Increment
LOADING: Updating
SUCCESS: success
PART_SUCCESS: Partial success
WAITING: waiting in line
WRONG: failed
Data update end time
effectTime
Effective time, really available
Update start time
execption
failure error message
failedSonId
The set of IDs of the table whose update failed due to the underlying table
fatherFailedIds
The ID collection of the parent table that failed to update
extra fields
updateCount
The number of rows changed, may increase or decrease
New fields in version 5.1.10
totalCount
total number of rows
deleteCount
Increment and decrement the number of rows
writeTime
file write time
etlFlow
Steps for Self-Service Datasets
appendCount
Incremental number of rows
List
jdbcTime
data acquisition time
openTime
sql execution time
infos
Non-error message (only internationalized key values and parameters)
Includes both dashboard and data preparation structures.
Note: this table is currently disabled and no data will be written. To view the SQL statements related to the data table, please view them in the SQL performance monitoring of bi tools.
an identifier that uniquely represents the event
Category type
enumerable numeric type
0: Dashboard
1: Data preparation
user name
date format string
category
Dashboard Name/Table Name
subCategory
component name/step name
event
exclusiveDuration
Exclusive time for this event
number ( ms )
dataSource
Describe data source information
query
SQL executed
row
Rows
number
contentSize
Occupied memory size
Number (kb)
exception
exception information
If there is any abnormal information, please record it here to facilitate troubleshooting
additionalInfo
extra information
String (JSON parsable)
event list
event category
event name
event subname
dash board
type: 0
cache
SpiderBaseCriteria
SQL L3 cache
GroupCacheProcedure
CrossCacheProcedure
GroupPagingCacheProcedure CrossPagingCacheProcedure
crossPage groupPage
makeTree
postGroup
treeSort
multiTarget (Old)
multiTarget (New)
data preparation
type:1
previewData
Preview of table data (non-editable)
public event
type: 0 or 1
sqlQuery
SQL data query
This table is added in version 5.1.22 and later.
Engine performance burying point requirements, burying point records of calculation time and other relevant information
Engine type
1: Direct connection
2: Draw
Hit situation of some strategies
0: indicates a miss
1: Indicates a rule hit but an actual miss
2: Indicates rule hit, actual hit
running state
0: success
1: Error reporting
售前咨询电话
400-811-8890转1
在线技术支持
在线QQ：800049425
热线电话：400-811-8890转2
总裁办24H投诉
热线电话：173-1278-1526
文 档反 馈
鼠标选中内容，快速反馈问题
鼠标选中存在疑惑的内容，即可快速反馈问题，我们将会跟进处理。
不再提示
10s后关闭