Author: Zhang Yanfeng, please indicate the source pseudonym: clouds dreams
51CTO course address: https://edu.51cto.com/lecturer/12750547.html Linux technology exchange group: 1127825548
Common monitoring software and features:
1) The veteran monitoring system of mrtg, which has existed more than 10 years ago, can be said to be a very good monitoring system, website bandwidth flow graph, historical trend graph, and resource monitoring. Not much use now.
2) Nagios features: focus on alarms, and can also cooperate with pnp, cacti, hyperic to produce pictures, etc.
It is especially suitable for monitoring a large number of servers to check whether a large number of services are normal. The focus is not on graphical monitoring. The main feature is focused on alarms, which are not or very weak in cacti. However, the fineness of drawing and pattern shaping is weaker than cacti. Realize page configuration management NagiosQL through plug-in.
3) The feature of cacti is drawing (rrdtool), historical trend graph, alarm can be realized through plug-in.
In terms of monitoring, there is a good drawing. Cacti is strong in terms of traffic and graph shaping, but it is poor in fault analysis, and the alarm mechanism needs to be improved. At this time, nagios comes in handy. Has page configuration management
4) Zabbix's new image alarm software. There is page configuration management, and the diagram is drawn through the PHP program.
5) Munin's special Niucha software, focusing on historical trend drawing, is very detailed. Built-in plugins.
6) Where can hyperic go to re-use, java development, and JAVA he is very good at. The control of the alarm is relatively fine, and there are particularly many plug-ins. Monitoring queue ActiveMQ, JVM, MVN.