LogDB Database

For projects deployed via FineOps, if you select the Elasticsearch component during deployment, Elasticsearch will replace swift(logdb) as the log storage component.

If Elasticsearch Connection Configuration is displayed on the General page under System Management > System Setting, ElasticSearch has been enabled as the log storage component.

Do not refer to this document to connect to the project log database. If you need to connect to the database, you can contact Fanruan technical support for assistance. For details about how to contact technical support, see Technical Support Channel Introduction.

Application Scenario

To enhance the management of the FineDataLink project and monitor the project running status at any time, you can enable log recording on the platform, as shown in the following figure.

Note:

Adjusting the log level setting only affects the output of system logs, not operation logs. For details about the differences between the two types of logs, see Log Introduction.

Function Description

The LogDB database is the built-in database used to store logs after FineDataLink log monitoring is enabled. You may wonder what content is included in the FineDataLink logs.

This document briefly introduces the LogDB database in the independently deployed FineDataLink project, including its connection method, the query syntaxes it supports, the various data tables it contains, and the meanings of fields in these tables.

Notes

The independently deployed FineDataLink project only allows you to query and preview data tables in the LogDB database through SQL statements in Server Dataset. Referencing related data tables for analysis is unavailable.

Connecting to the LogDB Database

For details, see FineLogDB(FDL) Data Connection.

Querying the Data Tables in the LogDB Database

1. Choose Server Dataset > Create Dataset > SQL Dataset, as shown in the following figure.

2. Enter the database query statement and click Preview to query the data table in the LogDB database, as shown in the following figure.

Note:

If the tables in the example cannot be found, try other tables. For details, see the "Data Tables and Fields in the LogDB Database" section.

Data Tables and Fields in the LogDB Database

For details about various data tables and the meanings of fields in the LogDB database, see LogDB Table Structure.

This section briefly introduces the query syntaxes supported by the LogDB database. Syntaxes not listed in this document may be unavailable.

Detailed Query

The SQL statements are as follows.

1. select * from fine_record_execute

2. select tname, displayName, consume from fine_record_execute

Using the GROUP BY Clause to Query Data

Using the GROUP BY clause to query data supports five aggregation methods: SUM, COUNT, MAX, MIN, and AVG.

If no aggregation method is specified in the SQL statement, COUNT will be used by default.

The SQL statements are as follows.

1. select sum(consume) from fine_record_execute group by tname, displayName

2. select consume from fine_record_execute group by tname, displayName

It is equivalent to: select COUNT(consume) from fine_record_execute group by tname, displayName

3. select min(consume), max(consume) from fine_record_execute group by tname, displayName

Using the WHERE Clause to Set the Filter Conditions

Basic WHERE clauses to set the filter conditions support the use of the AND/OR/IN/ISNULL functions as well as equal to (=), not equal to (<>), greater than (>), greater than or equal to (>=), less than (<), and less than or equal to (<=).

The SQL statements are as follows.

1. select * from fine_record_execute where consume > 10

2. select sum(consume) from fine_record_execute where consume > 10 and consume < 100 group by tname, displayName

3. select consume from fine_record_execute where tname = `doc/Advanced/Chart/GraphSwitching/Unified switching of multiple charts.frm`

4. select sum(consume) from fine_record_execute where tname in (`doc/Advanced/Chart/GraphSwitching/Unified switching of multiple charts.frm`, `doc/Advanced/Chart/Combination/Column-area combination chart.cpt`) group by tname, displayName

Using the TODATE() Function to Convert Timestamps to One of Regular Date Types

The result of the TODATE() function will be in the following date format: 2018-12-18 10:15:26.

The SQL statements are as follows.

1. select todate(time) from fine_record_execute

2. select * from fine_record_execute where todate(time)<'2018-12-18 10:15:26' and todate(time)>'2018-12-17 10:15:26'

Using the LIKE Clause for Fuzzy Query

You can only use the percent sign (%) at the beginning and end of the keyword.

Note:

1. You can use the LIKE clause for fuzzy query, but you cannot use the NOT LIKE clause.

2. Currently, you can only use the percent sign (%) as the wildcard, not the underscore (_). The use of the underscore (_) as the wildcard requires the JAR package released after June 14, 2019.

The SQL statements are as follows.

1. select * from fine_record_execute where tname like '%demo%'