1. Supported manual configuration adjustment of Nginx Monitoring and Boost Engine Monitoring dashboards for projects not deployed via FineOps.
2. Automated the update of the monitoring dashboard configuration upon cluster component changes to ensure normal monitoring.
Added Data Storage Monitoring to help you monitor and manage the data storage component of FineBI 6.1.
Added Nacos Monitoring to help you monitor and manage the Nacos component of FineDataLink.
Dashboards in Component Monitoring are primarily used to monitor the operation status and usage of various components (such as external databases, Nginx, and Elasticsearch) in O&M projects.
1. Ensure all prerequisites are met to use the dashboards described in this document normally. For details, see Prerequisites of Using Monitoring Dashboards.
2. Log in to FineOps as the admin, select the O&M project, and choose Project Monitoring > Component Monitoring.
3. Switch components in the left corner to view corresponding dashboards, including External Database Monitoring, Redis Monitoring, Nginx Monitoring, Elasticsearch Monitoring, MinIO Monitoring, and Boost Engine Monitoring.
1. You can switch the time range in the upper right corner to view the corresponding monitoring data. The default period is Last 30 minutes. You can view the data of up to the last 15 days.
2. Determined by the component composition of the O&M project, some dashboards in the following sections may show no data.
For example, if the Elasticsearch component is not installed, the Elasticsearch Monitoring dashboard will show no data. If the MinIO component is not installed, the MinIO Monitoring dashboard will show no data.
The External Database Monitoring dashboard mainly monitors the load on the external database, preventing instability in the external database from affecting the normal operation of the FanRuan system.
2. The external database must be a MySQL database of V5.6 or later versions.
Dashboard Example
Dashboard Indicator Description
It shows the number of remaining connections and rejected connections of the external database instance.
It displays the number of currently executing query statements on the external database. A consistent increase may indicate that the external database is overloaded.
It displays database deadlock information:
ts: the timestamp of the detected deadlock
thread: the ID of the thread on which the deadlock occurred
txn_id: the InnoDB transaction ID
txd_time: the active duration of the transaction before the deadlock happened
user: the username of the user executing the transaction
db: the database in which the deadlock occurred
tbl: the table on which the deadlock occurred
idx: the index on which the deadlock occurred
lock_type: the lock type (including Record Lock, Gap Lock, and Next-Key lock)
lock_mode: the lock mode (including S and X)
wait_hold: whether the transaction was waiting for the lock or holding the lock (two waited-for locks usually)
victim: whether the transaction was selected as the deadlock victim and terminated
query: the SQL statement that caused the deadlock
The Redis Monitoring dashboard monitors the operation of the Redis state server used by the FanRuan system.
Ensure all prerequisites are met to use the dashboards described in this document normally. For details, see Prerequisites of Using Monitoring Dashboards.
It displays the Redis mode.
Standalone: the standalone mode
Master-Slave Replication: the primary-secondary replication mode
Sentinel: the sentinel mode
Cluster: the cluster mode
It refers to the ratio of memory applied for by Redis from the operating system to the total memory allocated by the allocator. A value between 1 and 1.5 is considered healthy.
A value greater than 1 indicates memory fragmentation. The higher the value, the more severe the fragmentation. A value greater than 1.5 indicates that the system has allocated more memory to Redis than it is actually using. Redis does not release this excess memory back to the system, leading to significant fragmentation. For Redis of versions before V4.0, this issue could only be resolved by a safe restart. Redis of V4.0 and later versions supports automatic memory defragmentation.
A value less than 1 indicates that the system has allocated less memory to Redis than it is actually using. Redis is likely utilizing virtual memory, which severely impacts performance. Virtual memory relies on using disk space, which has significantly slower access speeds than physical RAM. Increasing the physical memory of the machine is recommended to improve performance in this case.
It displays the number of currently active client connections to Redis.
The default maximum number of client connections is 10,000.
A high value may impact Redis throughput. Attention is typically required when the count exceeds 5,000.
It displays the number of successful (hits) and failed (misses) key lookups per second.
You can use it as a reference to optimize Redis configuration based on business requirements.
It displays the count of expired/unexpired database keys in Redis.
You can tune Redis configuration as needed according to this indicator.
The Internal Gateway Monitoring dashboard monitors the operation of the internal gateway used by the FineRuan system, with a focus on request status.
1. For the FanRuan internal gateway Nginx deployed via FineOps, its information is obtained automatically when it is connected to FineOps.
2. For Nginx not deployed via FineOps, as well as Nginx deployed via FineOps but manually configured, its information cannot be obtained automatically when it is connected to FineOps.
Manually install the ngx_http_stub_status_module module to count the number of requests received and processed by the Nginx service, and then configure the information.
For details about installation and configuration methods, see the following section.
1. Check if the module is installed.
Navigate to the installation directory of Nginx of the O&M project. (This example uses /usr/nginx. Ensure that you use the correct directory name.)
cd /usr/nginx
Check which modules are enabled in Nginx.
./nginx -V
Check results.
If the http_stub_status_module module has been enabled, the command output will contain with-http_stub_status_module.
If the http_stub_status_module module has not been enabled, you need to recompile Nginx.
2. Install the module.
Navigate to the installation directory of Nginx. (This example uses /usr/nginx. Ensure that you use the correct directory name.)
Add support for http_stub_status_module through the configure command.
./configure --with-http_stub_status_module
./configure --with-http_stub_status_module --prefix=/usr/nginx --with-pcre=/usr/nginx/pcre-8.42 --with-zlib=/usr/nginx/zlib-1.2.11 --with-http_ssl_module --with-openssl=/usr/nginx/openssl-1.1.1a --with-stream --add-module=/usr/nginx/ngx_healthcheck_module-master
Compile and install Nginx.
make && make install
3. Enable the module.
Open and modify the nginx.conf file.
By default, the nginx.conf file is located in the conf directory in the Nginx installation directory.
cd /usr/nginx/conf
Locate the server {} block in the nginx.conf file and add the following configuration to enable the ngx_http_stub_status_module module for querying Nginx status.
location /basic_status {stub_status on;#allow 127.0.0.1; #Allow a certain IP address to access it. You can modify 127.0.0.1 to the desired IP address. #deny all; #Deny all other IP addresses.}
Notes:
Location must be strictly named basic_status.
The allow 127.0.0.1 and deny all lines mean that only local access is allowed.
If Nginx Exporter needs to be granted access, you can either comment out these two lines or set 127.0.0.1 to the actual IP address of Nginx Exporter.
4. Restart Nginx.
Check and ensure the syntax and structure of the Nginx configuration file are correct.
./nginx -t
Stop the Nginx server.
./nginx -s stop
Reload the Nginx configuration file and start the server.
nginx
5. Verify if the module is enabled.
Verify whether the ngx_http_stub_status_module has been successfully enabled.
Run the following query command. If the output includes the message server accepts handled requests, the ngx_http_stub_status_module has been successfully enabled.
curl http://127.0.0.1/basic_status
6. Connect Nginx to FineOps.
Log in to FineOps as the admin, select the O&M project, choose Project Monitoring > Component Monitoring, select Nginx Monitoring, and click the icon.
Fill in the Nginx information and click OK.
It displays the number of client connections that Redis is currently reading.
Received User Connection Count
2. Elasticsearch Monitoring is only available for projects that have Elasticsearch installed and enabled as the log storage server.
If the Elasticsearch component is not installed, the Elasticsearch Monitoring dashboard will show no data.
2. MinIO Monitoring is only available for projects that have MinIO installed and enabled as the cluster file server.
If the MinIO component is not installed, the MinIO Monitoring dashboard will show no data.
2. Boost Engine Monitoring is only available for FineBI projects that have the StarRocks component installed and enabled.
For the boost engine deployed via FineOps, its information will be obtained automatically when it is connected to FineOps.
For the boost engine not deployed via FineOps, as well as the boost engine deployed via FineOps but manually configured, its information cannot be obtained automatically when it is connected to FineOps. You need to configure the information.
Log in to FineOps as the admin, select the O&M project, choose Project Monitoring > Component Monitoring, select Boost Engine Monitoring, and click the icon.
Enter the information about every StarRocks engine and click OK.
2. Kafka Monitoring is only available for FineDataLink projects that have the Kafka component installed and enabled.
For the Kafka component of V20.0.2 or later versions that is deployed via FineOps, its information will be obtained automatically when it is connected to FineOps.
For the Kafka component not deployed via FineOps, as well as the Kafka component deployed via FineOps but manually configured, its information cannot be obtained automatically when it is connected to FineOps. You need to configure the information.
Log in to FineOps as the admin, select the O&M project, choose Project Monitoring > Component Monitoring, select Kafka Monitoring, and click the icon.
Enter the IP address and the port number of the Kafka server and click OK.
2. Data Storage Monitoring is only available for FineBI 6.1 projects that have the FineBI MinIO component installed and enabled.
2. Nacos Monitoring is only available for FineDataLink projects that have the Nacos component deployed via FineOps.