
Technical Exchange
Product Applications
- Compact Control Platform + Mobile Client in Small Production Systems
- How to understand cloud computing? Think of it like a food lover craving pizza...
- Do You Really Know What Cloud Computing Is?
- Walking in the Cloud: Who Pays for Your Security?
- Development and Applications of Cloud Computing
- A Brief Introduction to Cloud Computing and Virtualization
- The Future Data Center: Both Consolidated and Distributed
- Inside a Large-Scale Data Center
- Pros and Cons of Three Linux Server Monitoring Technologies
- 15 Mobile Terminal Trends for 2015
Cloud Computing
Data Center
Other

Pros and Cons of Three Linux Server Monitoring Technologies
This article covers the pros and cons of three Linux server monitoring technologies: SNMP agent (client) method, SSH method, and proprietary agent (client) method.
The powerful capabilities and rich interface of Linux have led many enterprises to adopt it as their server OS. Below are the pros and cons of three Linux server monitoring technologies.
1. SNMP Agent (Client) Method
SNMP (Simple Network Management Protocol), a widely adopted international network management protocol, is commonly used to manage network devices such as switches and routers, and is increasingly used for server monitoring. The advantage of SNMP-based server monitoring is its universality. Once an SNMP Agent is deployed on a server, any SNMP-capable software can monitor it, and this method does not require the monitored server's username and password, making it secure. The drawbacks are that many servers do not have SNMP Agent installed by default, requiring deployment on every server. Additionally, the monitored parameters are relatively fixed and lack depth. Users with special requirements may find it difficult to customize (most lack the ability for secondary development). Furthermore, since SNMP uses UDP, its reliability can be compromised under poor network conditions.
2. SSH Method
This method works by logging into the server via the corresponding client protocol, executing commands, and parsing the results to achieve monitoring. Its advantage is that most servers have the relevant server-side software installed by default, so monitoring is convenient and requires no additional software installation. However, it requires the server's username and password, which many users find unacceptable. In practice, server credentials are frequently changed for security reasons, creating significant difficulties for monitoring software, especially when managing a large number of servers. The monitored parameters are also limited by permissions and available commands, and some metrics important to users may be unobtainable. Its unrestricted remote control capability is another concern for users.
3. Proprietary Agent (Client) Method
This method involves installing a lightweight agent on the monitored machine. Its advantage is deep, targeted monitoring. Compared to SNMP, it can meet virtually any monitoring requirement. Since it does not require the monitored server's username and password, security is also strong. Most proprietary agents use proprietary protocols implemented over TCP, ensuring good reliability. The drawback is that initial deployment requires installing agent software on each machine individually. However, once installed, new monitoring capabilities can typically be auto-updated from the server, largely mitigating the deployment inconvenience.
In summary, each monitoring method has its pros and cons and should be chosen based on actual conditions. However, looking at the broader trend, SNMP and proprietary agent methods are expected to remain dominant.
Source: ChinaByte