Features:
After FineBI updates the data, if there is an error and you need to locate the cause, you can go to the log to view the detailed information. In this chapter, we will explain the keywords related to the data update in the log;
Applicable people: administrators;
Go to Manage> Intelligent Operations > Platform Log , and click the Global Settings button, as shown below:
At the system log level, you can set the log level (the real-time data is also set here), including DEBUG, INFO, WARN, ERROR, FATAL, and the default is ERROR. As shown below:
level
illustrate
DEBUG
Point out fine-grained information events, very helpful for debugging applications, mainly used to print some running information during development. Try not to use it in the production environment, otherwise it will affect the performance. Only adjust it when locating the problem, and change it back to the default ERROR level after fetching the log.
INFO
Messages highlight how the application is running at a coarse-grained level. Print some information that you are interested in or important. This can be used in the production environment to output some important information about the operation of the program, but it cannot be abused to avoid printing too many logs
WARN
Indicates potential situations, some messages are not error messages, but also some hints for programmers
ERROR
It is pointed out that although an error event occurs, it still does not affect the continued operation of the system. Print error and exception information, if you don't want to output too many logs, you can use this level
FATAL
Point out that each serious error event will cause the application to exit. This level counts high, major errors, this level can directly stop the program
Log location: %FineBI%/logs
Log file: fanruan.log (or fanruan.log.date)
Execution sequence: 1. Start of update > 2. Update base table > 3. Update analysis table > 4. Update association > 5. Update table failed / 6. End of update
Note: The content of the log description here is printed at the info level. After adjusting the log level to view/remove detailed logs, adjust the log level to daily ERROR in time, otherwise performance will be affected.
update type
keywords
single table update
Table Load: {}
Business package update
Package Load Table: {}
Global update
Global Load Trigger!: {}
Function
Subfunction
start of change tag
base table
Full Load:{}
Base table incremental update
Increase Load:{}
Self-service datasets
analysis Load:{}
fast Load:{}
Associative cache
relation load start
relation load success
relation load fail
The update table starts executing
table load start
table executed successfully
table load success
table execution failed
table load fail
Update table start : table load start
Update table successfully : table load success
Failed to update table : table load fail
Update the number of associations: [Group Load] RelationTask Size: {}
Execution of group tasks:
BI version keywords after November 2019
BI version keywords before November 2019
task starts
[Group Load] Start {}
group load start
Task execution failed
[Group Load] Fail {}
group load fail
task executed successfully
[Group Load] Success {}
group load success
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy