The Load Monitor is a system resource monitor tool used to monitor and track resource usage. It provides information about system resource utilization, including CPU, memory, disk, and network.
I recently had the chance to test out the 'Monitor' software, and was thoroughly impressed with its capabilities. This application is divided into two components, the MonitorServer (a Linux daemon) and a MonitorClient (a Java gui), which work together seamlessly to provide comprehensive monitoring and logging of server process, memory, network and CPU information, for multiple servers simultaneously.
The MonitorClient is written in Java and can be easily connected to one or more servers that are running the MonitorServer. The polling time can be easily adjusted as per the user's requirement and the client generates graphical representations of each resource (memory, CPU, network and process information) for one server at a time. Additionally, this component is equipped with logging options for recording information over all servers in individual log files in CSV format.
The MonitorServer is a separate application which is written in C++ and connected to omniORB4, specifically designed to minimize the load it imposes on the monitored server. The Server runs as an idle process until it is being polled by a MonitorClient. It is currently supported only by Linux, specifically kernels 2.2, 2.4, 2.6, and possibly 2.0 and 2.6 or higher, though there is hope of expanding this range in the future.
In conclusion, I was completely satisfied with the performance of the 'Monitor' application, and would highly recommend it to businesses seeking an efficient and easily accessible solution for monitoring multiple servers at once.
The MonitorClient is written in Java and can be easily connected to one or more servers that are running the MonitorServer. The polling time can be easily adjusted as per the user's requirement and the client generates graphical representations of each resource (memory, CPU, network and process information) for one server at a time. Additionally, this component is equipped with logging options for recording information over all servers in individual log files in CSV format.
The MonitorServer is a separate application which is written in C++ and connected to omniORB4, specifically designed to minimize the load it imposes on the monitored server. The Server runs as an idle process until it is being polled by a MonitorClient. It is currently supported only by Linux, specifically kernels 2.2, 2.4, 2.6, and possibly 2.0 and 2.6 or higher, though there is hope of expanding this range in the future.
In conclusion, I was completely satisfied with the performance of the 'Monitor' application, and would highly recommend it to businesses seeking an efficient and easily accessible solution for monitoring multiple servers at once.
What's New
Version 1.0b: N/A