FineBI Component Performance- FineOps Help Document

Last update: 2026-08-14

Overview

Version

FineOps Version	Functional Change
V2.34.0	/
V2.35.0	1. Added the following indicators to the Detail tab page in FineBI Component Performance: Query Wait Duration, Data Transfer Duration, Frontend Rendering Duration, and Permission Information Conversion Duration. 2. Optimized the value logic of Total Query Duration to calculate the total time from when a user clicked Query to when frontend loading was complete.
V2.37.0	Supported the display of performance details from multiple queries of a single component under Business Performance > FineBI Component Performance.
V2.38.0	Supported automatic parameter-based redirection to improve troubleshooting efficiency.

Application Scenario

The FineBI Component Performance function helps you comprehensively understand the access and performance of FineBI components, quickly locate performance bottlenecks, and reduce troubleshooting costs.

Usage Prerequisites

1. Confirm the function target.

This function applies only to FineBI dashboards accessed from a desktop.

Ensure the FineBI project version is either between V6.1.9 and V6.1.X or V7.0.8 and later.

2.Enable Tracing.

Enable Tracing before using this function. For details, see Prerequisites for Using Tracing.

3. Configure Performance Setting.

Log in to FineOps as the admin, select the target project, choose Health Inspection > Business Performance, and click Performance Setting in the upper-right corner.

Click FineBI Component Performance, configure the FineBI component performance settings of the project, and click Save.

Data Refresh Time: Set the execution time for daily aggregation based on the default interval. The default value is 3:00 AM.
Default Displayed Field: Configure (as the admin) the fields displayed by default in the overview table and detail table in FineBI Component Performance. This setting applies after the page is refreshed.
Slow Query Threshold: Set the threshold for slow queries on FineBI components.

Function Entry

1. Log in to FineOps as the admin, click the required project, and choose Health Inspection > Business Performance.

2. Select FineBI Component Performance from the drop-down list to switch to the corresponding monitoring dashboard.

Performance Overview

The Overview tab page consists of Performance Overview Chart and Performance Overview Table, providing a global view of FineBI component access.

Query Condition Configuration

1. Set display fields.

On the Overview tab page, click Display Field in the upper-right corner, and select the dimensions and indicators to display.

This setting applies to the drill-down details of the overview chart and the overview table.

The following table describes the dimensions and indicators:

Dimension/Indicator	Description
Component ID	FineBI component ID
Component Name	Latest name of the FineBI component
Subject of Component	Subject name of the FineBI component
Component Type	FineBI component type 1: Group table 2: Cross table 3: Detail table 4: Chart 5: Self-service dataset 6: Filter widget 7: Text component
Engine Type	Data Extraction or Direct Connection
Creator	FineBI component creator
Optimization Suggestion	FineBI component issues identified by FineOps and recommended optimization direction
Last Usage Time	Last access time of the FineBI component
Source Table ID	ID of the data table used in the component
Access Count	Number of accesses to the FineBI component Accesses through dashboards are also counted.
Average Total Query Duration	Query Duration records the total time spent querying the FineBI component. Average Total Query Duration records the average query duration of the component.
Average SQL Execution Duration	This is the average duration of the SQL query execution stage. The execution includes the following stages: Creating a data connection: A connection to the database needs to be obtained before execution. SQL query execution: This is the duration of database query execution.
Average SQL Execution Duration Ratio	Average SQL execution duration/Average total query duration
Slow Query Count	A slow query refers to a request whose duration is greater than the value configured in Slow Query Setting in the "Usage Prerequisites" section.
Source Table Count	Number of data tables used in the component
Affected Template Count	Number of dashboards that use the component
Count of Calculation Fields in Component	Number of calculated fields added to the component analysis area
Access User Count	Number of users who have accessed the FineBI component
Maximum Access Duration (ms)	This is the maximum query duration of the component. If a single component access involves multiple SQL statements, the execution duration of the SQL statement with the longest duration is used as the duration of that component access. The maximum duration of multiple accesses to the component is then calculated.
Median Access Duration (ms)	This is the median query duration of the component. If a single component access involves multiple SQL statements, the execution duration of the SQL statement with the longest duration is used as the duration of that component access. The median duration of multiple accesses to the component is then calculated.
Duplicate Query Ratio	Number of duplicate SQL statements sent by the component/Total query count
Cache Hit Ratio	Number of cache-hit queries/Total query count
Query Failure Ratio	Number of failed queries/Total query count
Slow Query Ratio	Slow query count/Total query count
Maximum Lineage Level of Source Table	Highest lineage level of the component's direct source table

2. Filter the components.

Click Filter to filter the FineBI components in the overview chart and overview table.

Filter Item	Description
Time Range	This filters the time range for accessing FineBI components. The default value is Last 24 Hours. You can switch to Last 7 Days, Last 30 Days, Last 90 Days, or Custom. Query results of custom intervals are cached and continuously displayed before the next query. The page displays the last time when custom data check was performed to help avoid repeated queries. The retention period of business data is five days by default. To adjust the retention period, see Prerequisites for Using Tracing.
Access User	Names of users who access FineBI components
Component ID	FineBI component ID
Component Name	FineBI component name
Subject	Subject name of the FineBI component
Component Type	FineBI component type
Engine Type	Data Extraction or Direct Connection
Average Access Duration	Average duration of user access to the component
Average SQL Execution Duration Ratio	Average SQL execution duration/Average total query duration
Slow Query Count	Number of queries whose duration is greater than the value configured in Slow Query Setting in the "Usage Prerequisites" section
Affected Template Count	Number of dashboards that use the component
Count of Calculation Fields in Component	Number of calculated fields added to the component analysis area

Overview Chart

The overview chart visually displays component access in charts, including the following three charts:

Chart Type	Description
Top N by Access Count	This column chart displays FineBI components with the highest access counts in descending order. The x-axis indicates the access count, and the y-axis indicates the component name. You can scroll to view all resources. Click a column to view the query duration and access performance details of the corresponding FineBI component.
Duration Distribution	This chart uses two dimensions, Access Count and Average Total Query Duration, to display all FineBI components and quickly locate problematic dashboards with high access counts and long durations. The x-axis indicates the access count, and the y-axis indicates the average total query duration (ms). Click a scatter point to view the query duration and access details of the corresponding FineBI component.
Overall Access Trend	This chart displays the trends of the overall average total query duration and total access counts within the selected time range, helping identify turning points where performance deteriorates. The x-axis indicates the date, and the y-axis indicates the average total query duration and total access count.

Chart Type

Description

Top N by Access Count

This column chart displays FineBI components with the highest access counts in descending order.

The x-axis indicates the access count, and the y-axis indicates the component name. You can scroll to view all resources.

Click a column to view the query duration and access performance details of the corresponding FineBI component.

Duration Distribution

This chart uses two dimensions, Access Count and Average Total Query Duration, to display all FineBI components and quickly locate problematic dashboards with high access counts and long durations.

The x-axis indicates the access count, and the y-axis indicates the average total query duration (ms).

Click a scatter point to view the query duration and access details of the corresponding FineBI component.

Overall Access Trend

This chart displays the trends of the overall average total query duration and total access counts within the selected time range, helping identify turning points where performance deteriorates.

The x-axis indicates the date, and the y-axis indicates the average total query duration and total access count.

Overview Table

The overview table displays performance indicators aggregated by component ID.

You can export the overview table of the performance overview as an Excel file for offline analysis and archiving.

Click the beside Overview. The system exports the data on the current page as an Excel file to local.

The export timeout limit is five minutes. If the export times out, the prompt "Export timed out. Reduce the data range." is displayed. You are advised to narrow the time range or reduce filtering conditions and execute the export again.

Performance Details

The Performance Detail tab page records detailed data of each component access in a table, allowing you to view the complete performance information of each access.

Query Condition Configuration

1. Set display fields.

On the Detail tab page, click Display Field in the upper-right corner, and select the dimensions and indicators to display. This setting applies to the detail table.

The following table describes the dimensions and indicators:

Dimension/Indicator	Description
Access Time	Time when a user accesses the FineBI component
Access User	Username of the user who accesses the FineBI component
Component ID	FineBI component ID
Component Name	Latest FineBI component name
Template ID	ID of the dashboard to which the component belongs If this field is empty, the user directly accessed the component without viewing a dashboard.
Dataset ID	ID of the dataset used by the component If multiple datasets are involved, this field is a collection of multiple IDs.
Session ID	Query session ID of the component in the accessed dashboard If this field is empty, the user directly accessed the component without viewing a dashboard.
Task ID	Unique identifier of this component access behavior
Query ID	Unique identifier of each query behavior
Access Type	Preview, Edit, or Export
Engine Type	Data Extraction or Direct Connection
Query Status	This indicates whether the query is executed successfully. The value is Success or Failure.
Cache Hit Status	This indicates whether this query hits the cache. The value is Miss, Page Cache Hit, Tree-Level Cache Hit, or SQL-Level Cache Hit.
Slow Query	A slow query refers to a request whose duration is greater than the value configured in Slow Query Setting in the "Usage Prerequisites" section. The value is Yes or No.
SQL Snippet Count	A component access may trigger multiple queries. SQL Snippet Count is the number of queries triggered by this access.
Total Query Duration	Complete query duration of this access, from when a user clicks query to when frontend loading is complete
Query Wait Duration	Duration from when a user clicks Query to when the query preparation stage starts
Query Preparation Stage (ms)	For direct-connected data, this is the stage of generating SQL queries. For extracted data, this is the stage of generating the query description for the extraction engine.
Execution Plan Building Duration (ms)	Duration for the FineBI engine to build how to organize the query after receiving the query request
Query Execution Duration (ms)	For direct-connected data, this is the execution duration of the direct-connected database. For extracted data, this is the calculation duration of the extraction engine.
Data Transfer Duration (ms)	Time required to return query results to FineBI If data is calculated by the direct connection engine, this field does not exist.
Memory Calculation Duration (ms)	Calculation time of the direct connection engine and all FineBI code
Permission Information Conversion Duration	Duration for permission information conversion on the server side
(FineBI Server-to-User's Browser) Data Transfer Duration	Time required for the FineBI server to transfer data to the user's browser
Frontend Rendering Duration	Total duration consumed by frontend JavaScript calculation, rendering, and display after backend calculation is complete
Query Complexity	Complexity of the SQL statement executed by the query
Data Connection Type	Type of the data connection from which the component data comes This field is specific to the Direct Connection engine.
Data Connection Name	Name of the data connection from which the component data comes This field is specific to the Direct Connection engine.
Data Connection URL	URL of the data connection from which the component data comes This field is specific to the Direct Connection engine.
Snippet ID	A query may have multiple query requests. For example, creating a data connection, SQL execution, and data transfer may each be split into multiple requests, which need to be counted and evaluated separately.
Database Connection Creation Duration (ms)	Time required to obtain a connection to the database before execution
SQL Generation and Optimization Duration (ms)	Stage duration for converting the corresponding query into SQL statements and optimizing the SQL statements
SQL Execution Duration (ms)	Duration of the SQL execution stage, including creating a data connection and executing a database query
(Database-to-FineBI) Data Transfer Duration (ms)	Time required for database query results to return to the FineBI server
Result Set Row Count	Number of rows in the result set returned by the query
Result Set Column Count	Number of columns in the result set returned by the query
Executed SQL	SQL content executed by the query component This field is specific to the Direct Connection engine.
Query Error Message	If a query error occurs, this field records the error content.
Query Detail	Details of the query
Version Time	Last time when the component configuration was changed
Cluster ID	ID of the FineBI - Application Node node that executes the query

2. Filter the templates.

Click Filter to filter the FineBI component scope in the detail table.

Filter Item	Description
Check Time	This filters the time range for accessing FineBI components. The default time range is the 24 hours before the current time. Query results of custom intervals are cached and continuously displayed before the next query. The page displays the last time when custom data check was performed to help avoid repeated queries. The retention period of business data is five days by default. To adjust the retention period, see Prerequisites for Using Tracing.
Access User	Names of users who access FineBI components
Component ID	FineBI component ID
Component Name	FineBI component name
Template ID	ID of the dashboard where the FineBI component is located
Dataset ID	ID of the dataset called by the FineBI component
Access Type	Preview, Edit, or Export
Engine Type	Data Extraction or Direct Connection
Query Status	Success or Failure
Cache Hit Status	The value is Miss, Page Cache Hit, Tree-Level Cache Hit, or SQL-Level Cache Hit.
Data Connection Name	Source data connection called by the direct-connected component
Total Query Duration	Total duration from when a user clicks query to when frontend loading is complete
SQL Execution Duration	Duration of the SQL execution stage, including creating a data connection and executing a database query
Session ID	Query session ID of the component in the accessed dashboard
taskId	Unique identifier of the component access behavior
Query ID	Unique identifier of the query behavior
Snippet ID	A query may have multiple query requests. For example, creating a data connection, SQL execution, and data transfer may each be split into multiple requests, which need to be counted and evaluated separately.

Detail Table

The detail table is shown in the following figure. Each row displays one access detail. If this access triggers multiple queries, you can expand the row to view the SQL snippet details of each query.

The following redirection operations are supported in the performance detail table:

Trace: You will be redirected to the details page of traces corresponding to this access.
Export: You can export the performance detail data on the current page as an Excel file for offline analysis and archiving. The export timeout limit is five minutes. If the export times out, the prompt "Export timed out. Reduce the data range." is displayed. You are advised to narrow the time range or reduce filtering conditions and execute the export again.