Successfully!

Error!

LogDB Table Structure

  • Last update:  2022-01-18
  • I. Overview

    This document will briefly introduce the meaning of each data table and table field in LogDB database.

    Table
    Namr

    fine_record_execute

    Report (BI) execution table

    fine_record_login

    Login table

    fine_record_logout

    Logout table

    fine_record_email

    Mailing list

    fine_record_write

    Data Entry Report

    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_func

    Function point usage log table

    fine_record_conf

    Partial configuration information table

    fine_record_lock

    User lock log table

    fine_tpl_info

    Template property table

    fine_container_entity

    Container information table

    fine_function_process

    Function point information table

    fine_operation_process_Log

    Cloud operation and maintenance log table

    fine_operation_shutdown_record

    Semaphore information table

    fine_plugin_usage

    Plugin information table

    fine_schedule_record

    Scheduled task execution log table

    fine_intelli_focus_point

    Function event track table

    fine_intelli_consume_point

    Performance information sheet

    fine_real_time_usage

    Application real time situation table

    II. fine_record_Execute report (BI) execution table

    Report (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 meaning of each field is shown in the following table:

    Field
    MeaningRemarkField type

    ID

    Primary key


    VARCHAR

    tname

    Template name

    Complete report path under reportlet

    VARCHAR

    displayName

    The name of the directory mounted to the platform

    Full path of record directory

    If the direct access the link, the displayName is empty

    VARCHAR

    type

    Report access mode

    The details are listed in the table below

    The range is from 0 to 105. At present, 33 codes have been used

    INTEGER

    param

    parameter


    VARCHAR

    IP

    IP address of report execution


    VARCHAR

    username

    The user who executed the report


    VARCHAR

    userrole

    User roles for executing reports


    VARCHAR

    consume

    Execution time

    Including SQL execution time and report calculation time

    BIGINT

    time

    Log start time


    BIGINT

    SQL

    SQL statement


    VARCHAR

    sqlTime

    Total time of SQL execution


    BIGINT

    browser

    The browser version used by the client to access the report


    VARCHAR

    memory

    Report occupied memory, unit B

    • If the calculation is interrupted due to downtime, it records the memory occupied from the beginning of report calculation to the calculation interruption (according to the number of grids, one grid occupies 0.2KB)

    • When the template complete field value is 0, the record here is 0

    • If the calculation is completed, the number of cells generated by the report from the beginning to the completion of calculation will be returned after dividing the recorded data by 200

    BIGINT

    reportId

    Template number


    VARCHAR

    userId

    User ID


    VARCHAR

    complete

    Is the calculation completed

    • If the calculation is interrupted due to downtime, the record is 0

    • If the calculation is completed, record as 1

    INTEGER

    source

    Access mode

    Integration: access through URL

    Single: platform access

    VARCHAR

    sessionID

    Session ID

    It is used to associate with the front-end rendering time-consuming event tracks in the function event track table(fine_intelli_consume_point)

    VARCHAR

    nodeThe name of the node where the template is loadedNeed to export treasure package. For details, please refer to: Cloud operation and maintenance stepsVARCHAR
    errorThe first error message during template executionNeed to export treasure package. For details, please refer to: Cloud operation and maintenance stepsVARCHAR
    webInfoTemplate execution information

    webResolution: The resolution when the current template is executed in front-end access, the record format is x*y

    fullScreen: Whether the current template is executed in full screen mode when accessed at the front end, the record format is 1/0

    VARCHAR

    Note: the fields of userId, complete, visitType and resource need to be updated to the jar packages of May 20, 2019 and later versions, 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 is shown in the following table:

    Code
    TypeParameter

    0

    Pagination Preview

    page

    1

    Data analysis

    view

    2

    Data Entry Preview

    write

    3

    Decision report preview

    form

    4

    Line engine

    layer

    5

    Online editing

    edit

    6

    New report

    write_plus

    7

    Preview new engine

    page_plus

    10

    Excel pagination export

    excel

    11

    Excel Unaltered export

    excelO

    12

    Excel full page export

    excelL

    13

    Excel page to 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 template

    cpt

    25

    HTML export

    html

    26

    data entry HTML export

    write_html

    27

    Bi export to excel


    30

    Flash printing

    print_flash

    31

    PDF printing

    print_Pdf

    32 

    Applet printing

    print_applet

    33

    No client printing

    print_noclient

    34

    Local software printing

    print_native

    101

    BI template Preview

    bi_view

    102

    BI template editing

    1) Record logic: click a dashboard to enter the editing state, wait for the page to load completely, no matter how many operations, record once; next time, click the template to edit or refresh the page to record the second time

    2) The same dashboard, each edit will have a record

    bi_edit

    103

    BI template sharing

    bi_share

    104

    Record the public link operation created

    bi_create_publink

    105

    Record access to public links

    bi_view_share

    106

    Export BI template to PDF globally

    bi_template_export_Pdf

    107

    Export BI template to Excel globally

    bi_template_export_excel

    108

    Export BI component to excel

    bi_component_export_excel

    109BI Dashboard Save As

    201

    Close browser or tab page (BI)


    203BI dataset sharingbi_analysis_table_share

    III. fine_record_Login table

    Login table: User log in, used to record user login information.

    The corresponding meanings of each field are shown in the following table:

    Field
    MeaningField type

    time

    Login time

    BIGINT

    IP

    Login IP address

    VARCHAR

    username

    Loggin user name

    VARCHAR

    userrole

    Login user role

    VARCHAR

    IV. fine_record_Logout logout table

    Logout form: user logout, used to record user logout information.

    The corresponding meanings of each field are shown in the following table:

    Field
    MeaningType

    time

    Logout time

    BIGINT

    IP

    Logout IP address

    VARCHAR

    username

    Logout user name 

    VARCHAR

    userrole

    Logout user role 

    VARCHAR

    V. fine_record_Email mailing list

    Mailing list: e-mail sending log (only contains "e-mail" in the toolbar), that is, if the report sends e-mail, 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:

    FieldMeaningRemarkType

    receiver

    Recipient user name


    VARCHAR

    mail

    Recipient mailbox


    VARCHAR

    IP

    IP address to send mail 


    VARCHAR

    username

    Users who send mail


    VARCHAR

    tname

    Template name

    Full path under the reportlet

    VARCHAR

    displayName

    The name of the directory mounted to the platform

    Full path of record directory

    If the direct access the link, the displayName is empty

    VARCHAR

    content

    Email content


    VARCHAR

    time

    Sending time


    BIGINT

    result

    Is it sent successfully


    BIT

    detail

    details


    VARCHAR

    VI. fine_record_Write Data entry report

    Data entry report: record the filling log information, that is, if the report is filled in, 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
    MeaningRemarkType

    username

    Users of data entry


    VARCHAR

    tname

    Template name

    Full path under the reportlet

    VARCHAR

    time

    Filling time


    BIGINT

    SQL

    SQL statement


    VARCHAR

    sqlTime

    Total time of SQL execution


    BIGINT

    result

    Is it filled in successfully


    BIT

    IP

    IP address of the report


    VARCHAR

    displayName

    The name of the directory mounted to the platform

    Full path of record directory

    If the direct access link is empty

    VARCHAR

    detail

    details


    VARCHAR

    browser

    The browser version used by the client to access the report


    VARCHAR

    consume

    Execution time

    Including SQL execution time, report calculation time

    VARCHAR

    VII. fine_record_Error execution error log table

    Execution error log table: that is, if an error is reported in the process of report execution, a record will be added to the table and its corresponding information record will be filled in the corresponding field to record all error and fatal level error information.

    The corresponding meanings of each field are shown in the following table:

    Field
    MeaningRemarkType

    displayName

    The name of the directory mounted to the platform

    Full path of record directory

    If the direct access the link, the displayName is empty

    VARCHAR

    IP

    IP address of report execution


    VARCHAR

    MSG

    error message


    VARCHAR

    time

    Error record time


    DATE

    tname

    Wrong template name

    Record the full path under the reportlet

    If it is not a template error, tname is recorded as "non template trigger error".

    VARCHAR

    trace

    Wrong path


    VARCHAR

    username

    The user who executed the report


    VARCHAR

    userrole

    User roles for executing reports


    VARCHAR

    errorcode

    Error code

    empty when there's no error code

    VARCHAR

    platformDisplay

    Display in platform

    1-yes

    0-no

    If there is an error log recorded in this table, this field is recorded as 1, otherwise, this field is recorded as 0

    The error log of the platform log is filtered and displayed. Only the records with platformdisplay = 1 are displayed.

    INTEGER

    VIII. fine_record_Param common parameter combination table

    Common parameter combination table: record the common parameter combination log information.

    The corresponding meanings of each field are shown in the following table:

    Field
    MeaningRemarkType

    templateid

    Template ID


    VARCHAR

    username

    user


    VARCHAR

    pgroup

    Parameter, and the value is displayed in the form of array

    {parameter 1: parameter value, parameter 2: parameter value}

    2020-02-28 And after jar, pggroup field value encryption display

    VARCHAR

    time

    Recording time


    BIGINT

    IX. fine_record_SMS SMS sending table

    SMS sending table: record the message sending log information, that is, if the message is sent, 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
    MeaningType

    receiver

    Recipient user name

    VARCHAR

    mobile

    Receiver's mobile number

    VARCHAR

    content

    Email content

    VARCHAR

    time

    Sending time

    BIGINT

    result

    Is it sent successfully

    BIT

    detail

    details

    VARCHAR

    sender

    Sender user name

    VARCHAR

    X. fine_record_Operation management log table

    Management log table: when the user operates on the module, 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
    MeaningType

    type

    Module (store internationalized key)

    VARCHAR

    item

    Set item

    VARCHAR

    resource

    Accessed resources

    VARCHAR

    operation

    operation

    VARCHAR

    username

    user name

    VARCHAR

    IP

    User IP address

    VARCHAR

    time

    User operation time

    BIGINT

    detail

    details

    VARCHAR

    requestParam

    Request parameters

    VARCHAR

    platformDisplay

    Platform display level

    INTEGER

    status

    Success or failure of this operation

    INTEGER

    The specific scenarios to be recorded are shown in the following table:

    Type moduleItem - set itemResource - accessed resourceOperation operationDetail - details

    Directory management

    node

    "Node full path"

    Add / delete / modify


    Directory management

    Template

    "Node full path"

    Add / delete / modify


    Directory management

    link

    "Node full path"

    Add / delete / modify


    Directory management

    Report label

    "Node full path"

    Add / delete / modify


    user management

    Global settings


    change


    user management

    user

    Name (user name)

    Add / delete / modify


    user management

    department

    "Department full path"

    Add / delete / modify


    user management

    Position under Department

    "Full path of position"

    Add / delete


    user management

    position

    "Position name"

    Add / delete


    user management

    Personnel under the post

    "Position name" - "name (user name)"

    Add / delete


    user management

    role

    Role name

    Add / delete / modify


    user management

    Personnel under the role

    Role name - name (user name)

    Add / delete


    user management

    Platform users

    Name (user name)

    Add / delete


    user management

    Bi view users only

    Name (user name)

    Add / delete


    user management

    Bi editing user

    Name (user name)

    Add / delete


    user management

    Mobile platform users

    Name (user name)

    Add / delete


    Authority management

    Global settings


    change


    Authority management

    Permission setting

    "Department / role / name (user name)"

    Add / delete

    Permission item: "directory / data connection / business package / manageable department role" type: view / authorize / edit

    Authority management

    Permission reuse

    "User name / Department]"

    multiplexing

    Source: "department / role / name (user name)" type: "permission item"

    system management

    Sign in

    Single sign on

    On / off


    system management

    Sign in

    Single sign on settings

    change


    system management

    Sign in

    Last login information prompt

    On / off


    system management

    Sign in

    Forget the password

    On / off


    system management

    Sign in

    SMS verification

    On / off


    system management

    routine

    General parameters

    change


    system management

    routine

    Bi parameters

    change


    system management

    Printing

    Print settings

    change


    system management

    short message

    SMS platform

    On / off


    system management

    short message

    Account binding

    change


    system management

    mailbox

    Sender account

    change


    Backup restore

    Global configuration


    change


    Backup restore

    Platform configuration

    Automatic backup

    On / off


    Backup restore

    Platform configuration

    Backup files

    Add / delete / restore


    Backup restore

    Report template

    Automatic backup

    On / off


    Backup restore

    Report template

    Backup files

    Add / delete / restore


    Backup restore

    Bi template

    Automatic backup

    On / off


    Backup restore

    Bi template

    Backup files

    Add / delete / restore


    Backup restore

    Jar package

    Automatic backup

    On / off


    Backup restore

    Jar package

    Backup files

    Add / delete / restore


    Backup restore

    plug-in unit

    Automatic backup

    On / off


    Backup restore

    plug-in unit

    Backup files

    Add / delete / restore


    Backup restore

    Update and upgrade

    Update package jar

    to update


    Backup restore

    Update and upgrade

    Jar package restore

    reduction


    Backup restore

    Update and upgrade

    Backup jar package

    Delete


    Platform log

    log setting


    change


    Platform log

    Access details


    export


    Platform log

    User behavior


    export


    Platform log

    Heat of formwork


    export


    Platform log

    Performance monitoring


    export


    memory management

    Intelligent early warning


    change


    memory management

    Memory session

    Name (user name) - template path

    end


    memory management

    Intelligent release


    change


    memory management

    Template restrictions


    change


    memory management

    life cycle


    change


    data connection

    data connection

    Data connection name

    Add / delete / modify


    Registration information

    Public cloud authentication / private cloud authentication / upload LIC file


    change


    security management

    SQL injection prevention

    Disable special keywords

    On / off


    security management

    SQL injection prevention

    Disabled special keywords

    change


    security management

    SQL injection prevention

    Escape character

    On / off


    security management

    SQL injection prevention

    Escaped characters

    change


    Scheduled scheduling

    Timed task

    "Task name"

    Add / delete / modify


    Scheduled scheduling

    Global settings


    change


    Multi level reporting

    Reporting process

    "Process name"

    Add / delete / modify


    Multi level reporting

    Reporting tasks

    "Task name"

    Add / delete / modify


    Mobile platform

    Mobile platform


    On / off


    Mobile platform

    Authorized equipment


    change


    Mobile platform

    QR code configuration


    change


    Template authentication

    Global settings


    change


    Template authentication

    Permission setting

    "Department / role / name (user name)"

    Add / delete

    Permission item: template path type: view / fill in

    Remote design permission

    Permission setting

    Name (user name)

    change

    Changed permission item: "template path"

    Plugin management

    Plu in management

    "Plugin name"

    Install / remove / enable / disable / update


    XI. fine_record_SQL execution table

    SQL execution table: record the execution of SQL.

    The corresponding meanings of each field are shown in the following table:

    Field
    MeaningRemarkType

    columns

    Dataset size

    Number of record columns

    BIGINT

    dsname

    The name of the dataset


    VARCHAR

    executeid

    Execution table ID


    VARCHAR

    rows

    Dataset size

    Number of record lines

    BIGINT

    sqltime

    SQL execution time

    Unit: ms

    BIGINT

    connection

    Data connection name


    VARCHAR

    connectionID

    Data connection ID

    Associate with the data source connection related event tracks in the function event track table (fine_intelli_focus_point)

    VARCHAR

    time

    Recording time


    BIGINT

    XII. fine_record_GC record table

    GC record sheet:Record the GC information of the system.

    The corresponding meanings of each field are shown in the following table:

    Old generation used memory before GC

    Field
    MeaningRemarkType

    gcStartTime

    GC start time


    BIGINT

    gcType

    GC type

    It is divided into young GC and full GC

    VARCHAR

    gcCause

    The reason for GC

    The common reasons are as follows:System.gc() , allocation failure, humongous

    VARCHAR

    PID

    Process PID


    VARCHAR

    node

    User named node name

    Empty under single machine

    VARCHAR

    duration

    GC duration


    BIGINT

    youngBeforeUsed

    use memory before Young GC


    BIGINT

    youngBeforeCommitted

    apply memory before Young GC


    BIGINT

    youngAfterUsed

    use memory after Young GC


    BIGINT

    youngAfterCommitted

    apply memory after Young GC


    BIGINT

    oldBeforeUsed

    use memory before Old GC


    BIGINT

    oldBeforeCommitted

    apply memory before Old GC


    BIGINT

    oldAfterUsed

    use memory after Old GC


    BIGINT

    apply memory after Old GC


    BIGINT


    metaspaceBeforeUsed

    use memory before metaspace GC


    BIGINT

    metaspaceBeforeCommitted

    apply memory before metaspace GC


    BIGINT

    metaspaceAfterUsed

    use memory after Metaspace GC


    BIGINT

    metaspaceAfterCommitted

    apply memory a fter metaspace GC


    BIGINT

    heapBeforeUsed

    Heap memory before GC


    BIGINT

    heapBeforeCommitted

    Heap request memory after GC


    BIGINT

    heapAfterUsed

    Heap memory before GC


    BIGINT

    heapAfterCommitted

    Heap request memory after GC


    BIGINT

    balancePromoterScore

    Stop score


    INTEGER

    releasePromoterScore

    Release score


    INTEGER

    loadScore

    Overall load score


    INTEGER

    XIII. fine_record_Conf partial configuration information table

    Record fine_conf_Part of the configuration information in entity.

    Field
    MeaningType

    time

    Record time

    BIGINT

    ID

    Configuration item

    VARCHAR

    value

    Configuration item value

    VARCHAR

    XIV. fine_record_Lock user lock log table

    Log user locks

    Field
    MeaningType

    time

    Storage time

    BIGINT

    lockItem

    Lock object

    VARCHAR

    lockTime

    Lock time

    VARCHAR

    autoUnlockTime

    Automatic unlocking time

    VARCHAR

    XV. fine_tpl_Info template attribute table

    Record template attribute

    Note: This table has no practical use and is only for backup. So no data will be recorded in the table.

    Field
    MeaningRemarkType

    time

    Storage time


    BIGINT

    ID

    Serial number


    VARCHAR

    Tid

    Template ID


    VARCHAR

    tname

    Physical template name

    Record the full path under the reportlet

    VARCHAR

    cnums

    Number of conditional formattings


    BIGINT

    formnums

    Number of formulas


    BIGINT

    sheetnums

    Number of sheets


    BIGINT

    dsnums

    Number of data sets


    BIGINT

    compformnums

    wThe number of complex formulas

    Including hierarchical coordinates, SQL, value formula

    BIGINT

    submitnums

    Built in multiple commits


    BIGINT

    isfrozen

    Is freezing used


    BIT

    isfoldtree

    Is a folding tree used


    BIT

    widgetnums

    Number of widgets


    BIGINT

    tsize

    Total template size


    BIGINT

    imgsize

    The size of the image in the template


    BIGINT

    execute0

    Engine summary 0


    BIGINT

    execute1

    Engine summary 1


    BIGINT

    execute2

    Engine summary 2


    BIGINT

    execute3

    Engine summary 3


    BIGINT

    execute4

    Engine summary 4


    BIGINT

    mem0

    Memory summary 0


    BIGINT

    mem1

    Memory summary 1


    BIGINT

    mem2

    Memory summary 2


    BIGINT

    mem3

    Memory summary 3


    BIGINT

    mem4

    Memory summary 4


    BIGINT

    sql0

    SQL summary 0


    BIGINT

    sql1

    SQL summary 1


    BIGINT

    sql2

    SQL summary 2


    BIGINT

    sql3

    SQL summary 3


    BIGINT

    sql4

    SQL summary 4


    BIGINT

    filternums

    Number of filters


    BIGINT

    injectnums

    Number of parameter injections


    BIGINT

    formula

    Formula usage in template


    VARCHAR

    jsapi

    Usage of JS API in template


    VARCHAR

    recordtime

    Template detection time


    VARCHAR

    XVI. fine_container_Entity container information table

    Record container information

    Field
    MeaningType

    time

    Storage time

    BIGINT

    node

    Node name

    VARCHAR

    item

    Configuration item

    VARCHAR

    value

    Configuration item

    VARCHAR

    XVII. fine_function_Process function point information table

    Record function point information

    Field
    MeaningType

    time

    Storage time

    BIGINT

    function

    Function point

    VARCHAR

    XVIII. fine_operation_process_Log cloud operation and maintenance log table

    Record cloud operation and maintenance log

    Field
    MeaningType

    time

    Recording time

    BIGINT

    node

    Node name

    VARCHAR

    process

    Log content

    VARCHAR

    XIX. fine_operation_shutdown_Record semaphore information table

    Record semaphore information

    Field
    MeaningType

    time

    Storage time

    BIGINT

    PID

    Process ID

    VARCHAR

    startTime

    start time

    BIGINT

    upTime

    deadline

    BIGINT

    node

    node

    VARCHAR

    signalName

    Signal name

    VARCHAR

    XX. fine_plugin_Usage plugin information table

    Record plug-in information

    Field
    MeaningType

    time

    Storage time

    BIGINT

    plugin

    Plugin name

    VARCHAR

    version

    Plugin version

    VARCHAR

    API

    Interface usage in plug-ins

    VARCHAR

    operation

    Plugin operation

    VARCHAR

    register

    Plugin registration

    VARCHAR

    enable

    Is the plug-in enabled

    BIT

    XXI. fine_schedule_Record timing task execution log table

    Record timing task execution information

    Field
    MeaningRemarkType

    ID

    Primary key

    UUID

    VARCHAR

    creator

    creator

    -

    VARCHAR

    detailMessage

    detailed information

    -

    VARCHAR

    filePath

    Generate attachment path

    Reserved field, not used

    VARCHAR

    logMessage

    log information

    -

    VARCHAR

    logTime

    Task execution time

    Log printing time

    BIGINT

    logType

    Log type

    0-fail

    1-success

    2-skip

    INTEGER

    nextFireTime

    Next record time

    Reserved field, not used

    BIGINT

    runType

    Attachment processing type

    0-Snapshot generation

    1-Mail sending

    2-FTP upload

    3-Message push

    4-Document printing

    5-SMS sending

    6-Platform mount

    7-Custom class

    8-Fill in regularly

    9-client notification

    10-SFTP upload

    INTEGER

    taskName

    Task name

    -

    VARCHAR

    taskID

    Task ID

    -

    VARCHAR

    time

    Storage time

    -

    BIGINT

    XXII. fine_intelli_focus_Point function event track table

    Function event track table:It is used to save all common function event track information.

    The corresponding meanings of each field are shown in the following table:

    Field
    MeaningRemarkType

    ID

    event track ID Number


    VARCHAR

    text

    Main contents of records


    VARCHAR

    source

    Source of event track

    -1-Undefined source

    1-Function point of built-in jar package (embedded)

    2-Plugin function point

    4 - Report of finereport

    8-FineBI function point (BI)

    INTEGER

    time

    time


    DATE

    username

    user name

    Transcoding processing, super tube user is 0

    VARCHAR

    IP

    Starting point IP


    VARCHAR

    title

    Title, what is the event track


    VARCHAR

    body

    A JSON data structure

    Store the information of different function points according to the function point ID

    Secondary information, may be empty

    VARCHAR

    Field ID format description:

    For example: FR-F1001

    The FR prefix indicates the event of FR.

    The first letter indicates function/performance: F-function, p-performance.

    The second digit indicates the classification: 1 - data source, 2 - foreground, 3 - error reporting, 4 - intelligent operation and maintenance, 5 - designer.

    The relationship between field ID and body in the table is as follows:

    ID
    bodyEffect

    FR-F1001

    ID: data connection ID

    Version: data source version

    Driver: connect driver information

    Times: use times

    Connect time: the time when the connection was created

    Used to record data connection related information

    FR-F3001

    Record the specific error stack

    Record the cause of error report for project startup failure

    FR-F4001

    First version plug-in record example:{node:2,memory:16,situation:normal,inform:1,type:auto}

    Node is the number of recommended nodes (1 when a single machine is recommended)

    Memory is the recommended single machine / single node memory

    Situation refers to the recommended situation: when it is marked as "normal", it is normal recommendation; when it is marked as "error", it is abnormal recommendation value; when it is "inequacy", it is insufficient running data; when it is "nonsupport", it is not recommended configuration.In the case of "normal memory" and "node memory", the rest values are empty

    Information is whether or not the notification has been made, 1 means that the notification has been made, and 0 means that the notification has not been made

    Type is the type of recommendation, marked as "auto" is the result of recommendation based on the running data of a natural day, and marked as "manual" is the result of user interface link recommendation

    Recommended memory configuration values

    FR-F4002

    Record example: {sessionid: XXXXXX, reason: release, detail: row count, load: high load, cell num: 100000, survival time: 600000}

    Sessionid: cleared session ID

    Reason: the reason why the session is cleared.It includes life, limit and release

    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, the records are row count, cell count, SQL time, excel cell count, commit row count and Cartesian

    • When the record is reason stopping calculating, record it as: releasing

    Load: the load condition of the system when the session is killed.It includes danger, terrible load, high load and normal load

    Cell num: the number of calculated cells

    Survival time

    Record the situation when the session is cleared due to the life cycle, template restrictions, and 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, terrible load kill and remove all

    Kill num time: the number of sessions that were killed due to too long time of not updating. When the type is removeAll, it is recorded as blank

    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: sum of killed sessions

    Session num: the total number of sessions before releasing the session

    Load: the load condition of the system when the session is killed.It includes danger, terrible load, high load and normal load

    Record the release session triggered by GC callback

    FR-F5001

    Record example: {disk}_beforegc:50, disk_aftergc:50}

    Record the cleaning of template version management GC

    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

    Node: node name

    Containermem: the memory size set by the container

    CPU: number of CPU cores

    Disk: total disk space

    Diskused disk space used

    Jdkversion: JDK version

    Containerversion: web container version

    Machinemem: physical machine memory

    System: server operating system

    Systemnum: number of server operating system bits

    Arch: processor architecture, such as x86_64、x86

    Diskspeed: disk access speed

    Frbuildno: jar package version of fr

    Bibuildno: jar package version of Bi

    Servertype: server type (cloud stands for cloud server, local stands for 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

    Company ID: Company ID

    Product version: product version

    Platform user num: number of users

    User basic information: user's registration information, etc.Record once a day

    FR-F5005

    TID: template ID

    Tname: physical template name (full path under reportlets)

    Cnums: number of condition formattings

    Formnums: number of formulas

    Sheetnums: number of multiple sheets

    Dsnums: number of data sets

    Compformnums: number of complex formulas (including hierarchical coordinates, SQL and value formulas)

    Submitnums: number of built-in submissions

    Isfrozen: is freezing used

    Isfoldtree: is a folding tree used

    Widgetnums: number of controls

    Filternums: number of filters

    Injectnums: number of parameter injections

    Formula: formula usage in template

    Jsapi: usage of JS API in template (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 segment record of execution time

    Mem0-mem4: Level 5 segmented record of memory usage

    Sql0-sql4: 5-level segment record of SQL execution time

    Template attribute information: record various information of the template, and output one record every day for each template

    FR-F5006

    ID: the location of the data in the configuration

    Value: data value

    Configuration information: change the fine in finedb every day_conf_The specific information in the entity table is recorded once

    FR-F5007

    Plugin: plugin name

    Version: plugin version

    API: interfaces used in plug-ins

    Opration: plugin operation

    Register: plugin registration

    Enable: enable or not

    Plugin usage: the usage of plug-ins is recorded once a day

    FR-F5008

    Function: purchase of function points

    Function point purchase: function point purchase, recorded once a day

    XXIII. fine_intelli_consume_Point performance information table

    Performance information sheet: record performance related information.

    The corresponding meanings of each field are shown in the following table:

    Field
    MeaningRemarkType

    ID

    event track ID Number


    VARCHAR

    source

    Source of event

    In the original class

    Embedded: represents the current system

    Plugin: represents the event track of the plug-in

    Undefined: indicates that no source is defined

    INTEGER

    time

    time

    start time

    BIGINT

    finish

    End time


    BIGINT

    consume

    time consuming

    Unit: ms

    BIGINT

    memory

    Memory size

    Unit byte

    BIGINT

    username

    operator


    VARCHAR

    IP

    Operation IP


    VARCHAR

    title

    Resource ID

    It can be template ID, analysis table ID, table ID, etc

    VARCHAR

    text

    Resource content

    It can be template name, analysis table name, etc

    VARCHAR

    type

    Operation type

    It can indicate what kind of operation has been carried out

    VARCHAR

    comment

    Resource notes

    It can be more specific information that needs to be analyzed directly.

    VARCHAR

    body

    Specific information of event track

    A JSON data structure, which stores different information according to different buried points

    VARCHAR

    XXIV. fine_real_time_Real time situation table of usage application

    Application real time situation table: record the real-time situation of the application.

    The corresponding meanings of each field are shown in the following table:

    FieldMeaningRemarkType

      field

    meaning

    remarks

    Field type

    node

    Node name

    2019-05-20 New and after jar fields

    VARCHAR

    CPU

    CPU utilization


    DOUBLE

    memory

    Current JVM memory


    BIGINT

    time

    Record the time, one per minute


    BIGINT

    sessionNum

    Number of surviving sessions

    2019-05-20 New jar fields

    BIGINT

    onlineNum

    Number of people online

    2019-05-20 New jar fields

    BIGINT

    PID

    Process PID

    2019-05-20 New jar fields

    VARCHAR

    templateRequest

    Number of template requests being calculated


    INTEGER

    httpRequest

    Total number of HTTP requests being processed


    INTEGER

    sessionRequest

    Number of requests with sessionid being processed


    INTEGER

    fineIO

    Size of memory outside the heap occupied by fineio

    Unit: KB

    2020-06-08New jar fields

    BIGINT

    NIO

    The size of memory out of heap occupied by NIO

    Unit: KB

    2020-06-08New jar fields

    BIGINT

    bufferMemUse

    Total memory used out of heap

    Directmem "NiO" and mappedmem

    Unit: KB

    2020-06-08New jar fields

    BIGINT

    physicalMemUse

    Used space of physical memory

    Unit: KB

    2020-06-08New jar fields

    BIGINT

    physicalMemFree

    Physical memory free space

    Unit: KB

    2020-06-08New jar fields

    BIGINT



    Attachment List


    Theme: Decision-making Platform
    Already the First
    Already the Last
    • Helpful
    • Not helpful
    • Only read

    Doc Feedback