You (the admin) can help users collect and analyze the trace details in the query request in case of dashboard/report lagging, without passively waiting for user feedback.
You can filter requests by ID, time, and others to examine requests and query latency for specific users accessing specific reports within a specified period.
You have enabled the Tracing function and configured related parameters in global settings before using this function.
For details, see Prerequisites for Using Tracing.
The collection of first-screen trace data by FineOps has specific requirements for browsers used by business users.
Therefore, ensure business users access FineBI/FineReport/FineDataLink applications using the supported browsers. Otherwise, relevant first-screen trace information may not be obtained or displayed.
You are advised to use Google Chrome of the latest version to access FanRuan applications.
58 and later versions
1. Log in to FineOps as the admin and select the required O&M project. Choose Tracing > First-Screen Trace.
2. Click Filter, configure the query conditions, and click Search.
The following table describes the supported query conditions.
Description: Searches for all queries started within the specified period.
Option: any time range within the past five days from the current date, but the span cannot exceed three days
Default: the past 30 minutes from the current time
Description: Searches for records related to the specified session.
Option: IDs of all sessions within the selected time range
Default: empty
Description: Searches for all queries triggered by the specified user.
Option: all recorded users
Description: Searches for query records corresponding to the accessed object.
Option:
FineReport project: actual template path
FineBI project: dashboard name and component name
Description: Searches for query records where the first-screen loading time falls within the specified range.
Option: non-negative integers (If it is left empty, no upper/lower limit will be set.)
The page after you click Search is shown in the following figure.
You can sort the query result traces:
Ascend by Duration: Sorts queries by their first-screen loading time from shortest to longest.
Descend by Duration: Sorts queries by their first-screen loading time from longest to shortest.
Ascend by Start Time: Sorts queries by their trigger time from oldest to most recent.
Descend by Start Time: Sorts queries by their trigger time from most recent to oldest.
Internal users can click this button to export trace data, which can be provided to FanRuan technical support personnel for troubleshooting.
The first 100 trace data records after sorting will be exported.
The accessed content, first-screen loading time, and query start time for each trace are displayed.
Loading time in yellow indicates that the first-screen loading time or the time consumption on associated traces exceeds 10 s. You are advised to click the record and inspect its traces carefully.
Loading time in red indicates that an error occurred in this trace. You are advised to click the record and inspect its traces carefully.
This area displays details of the selected trace in a Gantt chart.
You can hover over each request line to view more details.
You can click the View Trace button to be redirected to the Trace tab page, where details of the current trace will be displayed automatically.