Data monitoring method and device

Abstract

The invention discloses a data monitoring method and device. The method comprises the steps that monitoring data reported by an account is received; monitoring parameters configured by the account are acquired, wherein the monitoring parameters include at least monitoring index information and an alarm triggering condition; the monitoring data are counted according to the monitoring index information to acquire a statistical result; whether the statistical result conforms to the alarm triggering condition is detected; and if the fact that the statistical result conforms to the alarm triggering condition is detected, alarm information is generated. According to the invention, the technical problem that a data monitoring index is fixed is solved.

Description

technical field [0001] The present invention relates to the field of information processing, in particular to a data monitoring method and device. Background technique [0002] In the current basic data monitoring solution through cloud hosts, some common indicators are collected regularly, such as cpu usage, memory usage, and disk read and write rates, etc., allowing users to view monitoring charts, configure alarms, and cloud applications on the console A programming interface (Application Programming Interface, API) pulls monitoring data. [0003] The current basic monitoring adopts active collection by the agent side, and regularly reports to the data processing cluster. The processed data is stored in the database DB, and the monitoring data pulled from the database DB is displayed on the front desk. Send an alert notification. [0004] Such as figure 1 As shown, the existing architecture includes: collection agent agent: deployed on the main machine (moagent) and sl...

AI Technical Summary

Problems solved by technology

[0006] Through the above scheme, the reporting agent agent can only collect fixed indicators (such as some common indicators), and cannot report other indicators related to the user-specified business (such as indicators that are not common to other services); and in the above scheme, through When reporting on the agent side, the user cannot perceive whether the report is really successful, that is, the result of each report cannot be known immediately; in addition, for the alarm part of the basic monitoring, all regions share the same set of alarm configurations, which cannot satisfy the user's object settings for different regions Scenarios of different alarm policies; and the alarm policy of basic monitoring, only one alarm policy can be applied to the same object of the same indicator, and more flexible policy configuration cannot be realized

[0007] For the above-mentioned problem of fixed data monitoring indicators, no effective solution has been proposed so far

Images