Generally, FineDataLink project is deployed on middleware, relying on JDBC to connect to the database. You can access platform resources through the Internet.
Therefore, when performance problems occur, it is necessary to determine whether they are caused by network problems.
FineDataLink has built-in system detection plugins that support Network Detection. When encountering performance problems, you can use this tool to quickly detect whether there are any network problems.
Basic Network Detection: detects the current network environment, analyzes link latency, and checks external and internal network problems.
Network Component Detection: checks network components like FineDB, business database, FTP file server, Redis status server, and OSS storage server.
Basic network detection checks the network environment and link latency of the network between the user and the FineDataLink server.
Before conducting basic network detection, you (the admin) can customize the detection configurations.
Log in to the FineDataLink system as the admin, choose System Management > Intelligent O&M > Network Detection, and click the icon to go to Global Setting. Then, you can adjust the basic network detection settings, as shown in the following figure.
After setting the configurations, you can perform basic network detection.
Log in to the FineDataLink system as the admin, choose System Management > Intelligent O&M > Network Detection > Basic Network Detection. You are advised to perform Network Environment Detection first before conducting Link Time Consumption Analysis.
You need to wait for a period of time to finish the detection. You can cancel the detection at any time by clicking Stop Detection.
The detection result is displayed on the Basic Network Detection page, as shown in the following figure.
1. Network Environment Detection
The detected speeds of download and upload only represent the download and upload speeds of the connection between a user and the platform, not the actual bandwidth of the user's network connection.
Therefore, there may be a significant difference between the detected speed and that detected by other speed measurement tools.
Download: Download rate during detection (unit: Mbps)
Time Consumption: Download time during detection (unit: ms)
Jittering: Average download time during detection (unit: ms)
Upload: Uploaded rate during detection (unit: Mbps)
Time Consumption: Upload time during detection (unit: ms)
Jittering: Average upload time during detection (unit: ms)
Evaluate the network environment comprehensively based on the above detection items.
There are three levels of detection results: good, moderate, and poor.
2. Link Time Consumption Analysis
The name, time, and status of the links for sending a request by browser, receiving the request by server, sending the response by server, and receiving the response by browser can be recorded.
Network Component Detection checks network components like FineDB, business database, FTP file server, Redis status server, and OSS storage server.
Before conducting network component detection, you (the admin) can customize the detection configurations.
Log in to the FineDataLink system as the admin, choose System Management > Intelligent O&M > Network Detection, and click the icon to go to Global Setting, then you can adjust the network component detection settings, as shown in the following figure.
You need to add a component first before detecting it.
Log in to the FineDataLink system as the admin, choose System Management > Intelligent O&M > Network Detection > Network Component Detection, and click Add Network Component, as shown in the following figure.
Supported network components:
External FineDB can be detected.
If the project is configured with an external FineDB, the FineDB will be automatically added to the Network Component Detection page and cannot be deleted.
Data connections that currently exist in the system can be manually added.During business database detection, the first table returned by the system query is detected by default. You can also customize the query statement for detection.
For the added network components, you can detect a single one or detect them all in batches, as shown in the following figure.
The detection result is displayed on the Network Component Detection page, as shown in the following figure.
The detection logic and return results of various components are shown in the following table.
1. Connectivity detection:
Check if the component is properly connected.
Check the time for the connection between a browser and a component.
2. Component network detection:
Store binary files of 1 MB, 10 MB, and 100 MB in sequence. Then query and delete them.
Record the time of storage, query, and deletion.
Query a single data item. The first table obtained by the SELECT statement (default statement) will be used by default. You can modify the statement.
Record the times when the browser sends the request, the database receives the request, the database sends the response, the browser receives the response, and the query is executed.
Store files of 1 MB, 10 MB, and 100 MB. Then download and delete them.
Record the time consumption of upload, download, and deletion.
Store string data of 1 MB, 10 MB, and 100 MB. Then download and delete them.
Store an image, then read and delete it.
You can view all records of basic network detection and network component detection in Historical Detection Record.
On the Historical Detection Record page, you can:
View the detection content and results of each record.
Copy, delete, or generate reports for each record.
Select multiple records to generate reports in batches.
Historical detection records will occupy memory. Therefore, you (the admin) need to make relevant settings to delete them automatically at a regular time.
Log in to the FineDataLink system as the admin, choose System Management > Intelligent O&M > Network Detection, and click the icon to go to Global Setting to set the frequency of clearing up historical detection records, as shown in the following figure.
The system will clear up records every three months and retain records for the latest three months by default.
Note
:
The latest three months refer to the past three months relative to the current date. For example, records from August 19, 2019, were deleted manually. Then the system would retain records from May 5, 2019, to August 19, 2019.
Therefore, the log files will be retained for at least three months, and actually up to six months at most.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy