The server monitoring dashboard primarily monitors the status of servers on which FanRuan applications and related components are running, facilitating timely attention to server indicators to avoid affecting normal application operation.
Ensure all prerequisites are met to use the dashboards described in this document normally. For details, see Prerequisites of Using Monitoring Dashboards.
1. Log in to FineOps as the admin, select the O&M project, and choose Project Monitoring > Server Monitoring.
2. This dashboard is divided into two parts that display server resource overview and server details, respectively.
Dashboard Example
It provides an information overview of servers in the selected O&M project.
For servers with multiple network interface cards or partitions, FineOps only collects information of the one with the highest usage rate.
Indicators with anomalies will be highlighted in red/yellow. If you click an IP address, the server detail section below will display detailed indicators of this server.
Dashboard Indicator Description
It displays the size of the used server memory.
It displays the number of CPU cores of each server.
It displays outgoing network traffic of the server, indicating server upload pressure.
It displays detailed indicators of the specified server. You can click an IP address in the above overview section to switch the content displayed in this section.
Indicators with anomalies will be highlighted in red/yellow.
It displays the maximum and current number of open files.
The user who started the application is subject to a limit on the maximum number of open files. When the current number of open files in the application approaches this limit, subsequent access attempts may generate errors, requiring you to modify the open file limit for the startup user.
It displays the current CPU usage rate.
High usage indicates high computational pressure, requiring you to enhance CPU performance or investigate and optimize heavy tasks.
It displays the memory usage rate of the current server.
Sustained high usage may cause crashes, requiring you to increase physical memory or terminate some memory-intensive processes.
It displays the usage rate of the root disk of the current server.
High disk usage may cause crashes or affect normal use, requiring you to increase disk space or clean up the disk.
It displays the number of read/write operations per second (IOPS) on the root disk, reflecting the disk I/O load.
It displays the percentage of CPU time spent waiting for disk I/O operations to complete over time.
Sustained high values indicate that the system's disks are heavily utilized, and the CPU is spending most of its time waiting for disk I/O. This often signifies an I/O bottleneck.
It displays the number of TCP connections in various states, including LISTEN, SYN_SENT, ESTABLISHED, SYN_RECV, FIN_WAIT1, CLOSE_WAIT, FIN_WAIT2, LAST_ACK, TIME_WAIT, CLOSING, and CLOSED.
It displays the amount of queued incoming/outgoing bytes in the TCP queue.
rx_queued_bytes: the number of bytes received and buffered, waiting to be processed by the receiver
tx_queued_bytes: the number of bytes sent but not yet acknowledged by the receiver
(Linux only) It displays the inode (the index node) usage rate of the server over time.
If all inodes are exhausted, new files cannot be created on the disk even if there is still free disk space.