Real-time Data Log

  • Last update:  2022-08-02
  • Ⅰ. Description

    Features:

    • When using real-time data, the front-end can perform real-time data calculation and processing through simple mouse clicks and drags. So when doing real-time data analysis, if you encounter some errors, how should you troubleshoot? In this chapter, we introduce the configuration and viewing of real-time data execution logs;

    Applicable people: administrators;

    Ⅱ. Log level

    • Go to  , and click the Global Settings button "Manage > Intelligent Operations > Platform Log".

    • 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:

    error.png

    level

    illustrate

    DEBUG

    Point out fine-grained information events, very helpful for debugging applications, mainly used to print some running information during development

    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 path

    Log path: %FineBI%/logs

    Log name: fanruan.log (or fanruan.log.date)

    Log example:

    1564024340925729.png      

    Ⅳ. Log description

    1. SQL Editing Interface Preview

    log level: INFO;

    Log keyword: the preview sql is;

    1.png

    2. SQL data set to take fields

    log level: DEBUG;

    Log keyword: direct.sql.table.field.sql;

    2.png

    3. SQL data set fetching

    log level: DEBUG;

    log key:

    • sql create: time-consuming to convert sql;

    • sql execute/slice sql execute: time-consuming sql query;

    • sql foreach result/slice sql foreach result: time-consuming sql fetching;

    The log screenshot corresponding to the dashboard preview:

    3.png

    The corresponding log screenshot when the dashboard is edited:

    4.png

    附件列表


    主题: System Management
    Previous
    Next
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy