Redis multi-instance monitoring system and method

Abstract

The invention provides a Redis multi-instance monitoring system and method, and relates to the technical field of cluster operation state monitoring, and the system comprises a state acquisition module which is integrated in Redis instances and is used for acquiring performance indexes; an acquisition mode processing module which is used for adjusting the mode of the state acquisition module according to different monitoring scenes; a monitoring core module which is used for calling a performance index, performing state analysis and alarm analysis according to a configured monitoring rule, and generating a state analysis result and alarm information; a data storage module which is used for data persistence; an alarm management module which is used for acquiring alarm information, generating a state adjustment instruction according to the alarm information, and driving a service discovery module to process an abnormal node in a Redis container; the service discovery module which is used for monitoring a container environment where the Redis instance is located and performing operation and maintenance management on nodes of the Redis container; and a visualization module which is used for displaying a monitoring data report through a visualization interface.

Description

technical field [0001] The invention relates to the technical field of cluster operation status monitoring, in particular to a Redis multi-instance monitoring system and method. Background technique [0002] At present, the monitoring system mostly adopts the technical architecture based on Nagios or Zabbix framework, and these technical frameworks often have problems such as complex configuration, poor flexibility, and low efficiency; for example, Nagios: there is no self-discovery function, and configuration files need to be frequently modified; configuration is limited to Terminal, poor scalability; low performance index processing performance; no historical data, difficult to trace faults and other issues. Zabbix: There is an obvious performance bottleneck; the cost is high, and the bottleneck problem of database writing needs to be solved by adding a proxy, and the efficiency is low; the use requires secondary development, which increases personnel costs and reduces the...

AI Technical Summary

Problems solved by technology

[0002]At present, most monitoring systems use technical architectures based on Nagios or Zabbix frameworks. These technical frameworks often have problems such as complex configuration, poor flexibility, and low efficiency; for example, Nagios: There is no self-discovery function, and the configuration file needs to be frequently modified; the configuration is limited to the terminal, and the scalability is poor; the performance index processing performance is low; there is no historical data, and it is difficult to trace faults, etc.

Zabbix: There is an obvious performance bottleneck; the cost is high, and the bottleneck problem of database writing n

Images