CN111324514A - System abnormity monitoring method, device, equipment and storage medium - Google Patents

System abnormity monitoring method, device, equipment and storage medium Download PDF

Info

Publication number
CN111324514A
CN111324514A CN202010190834.9A CN202010190834A CN111324514A CN 111324514 A CN111324514 A CN 111324514A CN 202010190834 A CN202010190834 A CN 202010190834A CN 111324514 A CN111324514 A CN 111324514A
Authority
CN
China
Prior art keywords
monitoring
abnormal
data
preset
logic
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010190834.9A
Other languages
Chinese (zh)
Inventor
杨胜涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen kaniu Technology Co.,Ltd.
Original Assignee
Shenzhen Kaniu Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Kaniu Information Technology Co ltd filed Critical Shenzhen Kaniu Information Technology Co ltd
Priority to CN202010190834.9A priority Critical patent/CN111324514A/en
Publication of CN111324514A publication Critical patent/CN111324514A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3051Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the invention discloses a system abnormity monitoring method, a device, equipment and a storage medium. The system anomaly monitoring method comprises the following steps: starting a monitoring logic according to a preset trigger event; acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table; and executing the monitoring logic to monitor system abnormity based on the configuration information. The embodiment of the invention realizes the customizability of system abnormity monitoring.

Description

System abnormity monitoring method, device, equipment and storage medium
Technical Field
The embodiment of the invention relates to computer technology, in particular to a system abnormity monitoring method, a device, equipment and a storage medium.
Background
With the rapid development of computer technology and the internet, the functional requirements of people for computer systems are increasing, and for multifunctional systems, the anomaly monitoring becomes very important.
In the prior art, personnel can be timely notified or other reactions can be made when tasks are executed or database data are abnormal so as to monitor the system function in real time, but the existing system is not light enough in monitoring, is based on log analysis during monitoring, but the log printing error is considered to be abnormal, and accurate adjustment in accordance with services cannot be made on early warning monitoring; the existing system monitoring also does not provide an extension interface for monitoring customized data and notifying customized exception, and does not support the extension of developers; in addition, for some service data, such as a marketing short message pushing task, when the pushing failure rate is 5%, the situation is abnormal, short message early warning is needed to be sent to a creator of the short message pushing task, and similar to the situation, the existing system monitoring cannot meet the requirement, and customized monitoring cannot be achieved.
Disclosure of Invention
The embodiment of the invention provides a system abnormity monitoring method, a device, equipment and a storage medium, so as to realize customizability of system abnormity monitoring.
To achieve the object, an embodiment of the present invention provides a system anomaly monitoring method, including:
starting a monitoring logic according to a preset trigger event;
acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table;
and executing the monitoring logic to monitor system abnormity based on the configuration information.
Further, the starting the monitoring logic according to the preset trigger event includes:
configuring a timing monitoring task through a batch workflow task scheduler;
and starting a monitoring logic according to the timing monitoring task.
Further, the executing the monitoring logic for system anomaly monitoring based on the configuration information includes:
executing the monitoring logic based on the configuration information to monitor a target system to obtain first monitoring data;
inquiring a preset abnormal monitoring data table to judge whether the first monitoring data is abnormal monitoring data;
if the first monitoring data is abnormal monitoring data, inquiring whether the abnormal monitoring data exists in a cache database;
if the abnormal monitoring data does not exist in the cache database, storing the abnormal monitoring data into the cache database, storing the abnormal monitoring data for a first preset time, and storing the abnormal monitoring data into an abnormal monitoring notification table;
and notifying a preset user according to the abnormal monitoring notification table.
Further, the notifying a preset user according to the abnormal monitoring notification table includes:
and adjusting the abnormal monitoring configuration table according to the abnormal monitoring data.
Further, after notifying a preset user according to the abnormal monitoring notification table, the method further includes:
and writing the notified result state into the abnormal monitoring notification table.
Further, after writing the notified result status into the abnormality monitoring notification table, the method includes:
acquiring abnormal monitoring data which are not notified or failed to be notified from the abnormal monitoring notification table according to the result state of the notification;
acquiring abnormal data to be notified from the abnormal monitoring data which is not notified or fails to be notified according to an abnormal notification configuration table;
and notifying a preset user according to the abnormal data needing to be notified.
Preferably, the batch workflow task scheduler is Azkaban.
In one aspect, an embodiment of the present invention further provides a system anomaly monitoring device, where the system anomaly monitoring device includes:
the monitoring starting module is used for starting monitoring logic according to a preset trigger event;
the information acquisition module is used for acquiring the configuration information of the monitoring logic from a preset abnormal monitoring configuration table;
and the monitoring execution module is used for executing the monitoring logic to monitor system abnormity based on the configuration information.
On the other hand, an embodiment of the present invention further provides a system anomaly monitoring device, where the system anomaly monitoring device includes: one or more processors; a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method as provided by any embodiment of the invention.
In yet another aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method provided in any embodiment of the present invention.
According to the embodiment of the invention, the monitoring logic is started according to the preset trigger event; acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table; and executing the monitoring logic to monitor the system abnormity based on the configuration information, solving the problem that the conventional system monitoring cannot realize customized monitoring, and realizing the customizable effect of the system abnormity monitoring.
Drawings
Fig. 1 is a flowchart of a method for monitoring system anomaly according to an embodiment of the present invention;
fig. 2 is a flowchart of a method for monitoring system anomaly according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a system anomaly monitoring device according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a system abnormality monitoring device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are for purposes of illustration and not limitation. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. A process may be terminated when its operations are completed, but may have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.
Furthermore, the terms "first," "second," and the like may be used herein to describe various orientations, actions, steps, elements, or the like, but the orientations, actions, steps, or elements are not limited by these terms. These terms are only used to distinguish one direction, action, step or element from another direction, action, step or element. For example, a first module may be termed a second module, and, similarly, a second module may be termed a first module, without departing from the scope of the present application. The first module and the second module are both modules, but they are not the same module. The terms "first", "second", etc. are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features. In the description of the embodiments of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Example one
As shown in fig. 1, an embodiment of the present invention provides a system anomaly monitoring method, apparatus, device and storage medium, where the monitoring method includes:
and S110, configuring a timing monitoring task through the batch workflow task scheduler.
And S120, starting monitoring logic according to the timing monitoring task.
In this embodiment, when starting the abnormal monitoring, a batch workflow task scheduler needs to configure a timing monitoring task, where the timing monitoring task may monitor a function of a software system in any computer, a task execution condition of the software system, or data in a database of the computer, and further, a timing monitoring task trigger is adopted in the monitoring of a data type, so that there is no intrusiveness on the monitored software system, a method of adding Spring annotation to a tangent plane may be adopted in the monitoring of system logic, and Spring is a Java open source framework created to solve the complexity of enterprise application development, so as to achieve the intrusiveness on the system logic. Preferably, the batch workflow task scheduler is Azkaban, and the Azkaban is a batch workflow task scheduler opened by Linkedin and used for running a group of works and processes in a workflow in a specific sequence, and the Azkaban defines a KV file format to establish a dependency relationship between tasks and provides an easy-to-use web user interface to maintain and track your workflow, and the configured monitoring tasks can be triggered at preset time to start monitoring logic to monitor the system.
S130, acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table.
And S140, executing the monitoring logic to monitor system abnormity based on the configuration information.
In this embodiment, the monitoring logic needs to obtain configuration information in advance after being started, an abnormal monitoring configuration table needs to be established in advance before monitoring starts, each record in the abnormal monitoring configuration table corresponds to one monitoring logic, the configuration information in the abnormal monitoring configuration table includes an early warning threshold, an early warning frequency, an early warning content template, an early warning target, an early warning mode and the like, the abnormal monitoring configuration table can be stored in a database of a computer, the database can be a MySQL database, the MySQL is a relational database management system, the relational database stores data in different tables instead of storing all data in one large database, and thus, speed is increased and flexibility is improved. After the monitoring logic acquires the corresponding configuration information from the abnormality monitoring configuration table, the monitoring logic can execute the system abnormality monitoring based on the configuration information. The configuration information can be changed by the system according to preset conditions, and also can be changed by developers, so that customized monitoring of the system is realized.
According to the embodiment of the invention, the monitoring logic is started according to the preset trigger event; acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table; and executing the monitoring logic to monitor the system abnormity based on the configuration information, solving the problem that the conventional system monitoring cannot realize customized monitoring, and realizing the customizable effect of the system abnormity monitoring.
Example two
As shown in fig. 2, a second embodiment of the present invention provides a system anomaly monitoring method, and the second embodiment of the present invention explains and explains step S140 further on the basis of the first embodiment of the present invention, and step S140 includes:
s141, the monitoring logic is executed based on the configuration information to monitor the target system to obtain first monitoring data.
And S142, inquiring a preset abnormal monitoring data table to judge whether the first monitoring data is abnormal monitoring data.
S143, if the first monitoring data is abnormal monitoring data, inquiring whether the abnormal monitoring data exists in a cache database.
S144, if the abnormal monitoring data do not exist in the cache database, storing the abnormal monitoring data into the cache database, storing the abnormal monitoring data for a first preset time, and storing the abnormal monitoring data into an abnormal monitoring notification table.
And S145, notifying a preset user according to the abnormal monitoring notification table.
In this embodiment, the part that generates the exception may be defined as an exception producer, the part that handles the exception is defined as an exception consumer, and the database of the software system plays a decoupling role therein, that is, an intermediate decoupling layer between the exception producer and the exception consumer.
The method comprises the steps that a first monitoring data is obtained after a monitoring logic is executed to monitor system abnormity based on configuration information, a preset abnormity monitoring data table is required to be inquired to judge whether the first monitoring data is abnormity monitoring data, and the abnormity monitoring data table stores abnormity information owned by an abnormity producer, and mainly comprises the self attribute of an abnormity record, the attribute of an abnormity record consumption logic and a state record of the process from abnormity record production to consumption. Further, the exception information may further include an exception type, exception content, an exception state, a user name of the early warning, and an alarm mode of the exception producer. The anomaly monitoring data table can be stored in a database of the computer, and the database can be a MySQL database. And inquiring the monitoring data of the current day in an abnormal monitoring data table in the MySQL database, and checking whether the first monitoring data is abnormal monitoring data.
If the first monitoring data is not abnormal monitoring data after the query, ending the monitoring, if the first monitoring data is abnormal monitoring data after the query, continuously querying whether the abnormal monitoring data exists in the cache database, namely, judging whether the abnormal monitoring data is collected within a preset frequency and/or time, wherein the preset frequency can be 3 times within 1 day, the preset time can be 30 minutes, if the abnormal monitoring data exists in the cache database, indicating that the abnormal monitoring data is collected within the preset frequency and/or time, more than 3 times within 1 day, or 30 minutes, ending the monitoring, and if the abnormal monitoring data does not exist in the cache database, indicating that the abnormal monitoring data is not collected within the preset frequency and/or time, and 3 times within 1 day or less, or if the abnormal monitoring data are not collected within 30 minutes, storing the abnormal monitoring data into the cache database, storing the abnormal monitoring data for a first preset time, and storing the abnormal monitoring data into an abnormal monitoring notification table. The cache database may be a cache middleware Redis, and the anomaly monitoring data is put into the cache middleware Redis as a key to implement the frequency control.
Further, for the abnormal monitoring data stored in the abnormal monitoring notification table, if the abnormal monitoring data does not appear within the first preset time, the preset user is notified according to the abnormal monitoring notification table, and the same abnormal data that has appeared within the first preset time is not repeatedly notified. And notifying a preset user, namely an abnormal consumer to process according to the abnormal monitoring notification table, wherein the notification mode can be a mail and a short message, and the preset user can be a developer or a task creator corresponding to the abnormal monitoring data.
And S146, adjusting the abnormity monitoring configuration table according to the abnormity monitoring data.
In this embodiment, the abnormal monitoring configuration table may also be adjusted according to the abnormal monitoring data, and the abnormal monitoring configuration table is adjusted in a targeted manner for the abnormal monitoring data, so as to finally adjust the monitoring logic, for example, if the abnormal monitoring data is data in the database, the abnormal monitoring configuration table is adjusted, so that the monitoring logic enhances monitoring of the database.
And S147, writing the notified result state into the abnormal monitoring notification table.
And S148, acquiring abnormal monitoring data which are not notified or failed to be notified from the abnormal monitoring notification table according to the result state of the notification.
S149, according to the abnormal notification configuration table, obtaining abnormal data to be notified from the abnormal monitoring data which is not notified or fails to be notified.
And S150, notifying a preset user according to the abnormal data needing to be notified.
In this embodiment, after the notification, the status of the result of the notification needs to be written into the abnormality monitoring notification table, and the status result of the notification includes success of the notification, non-notification, and failure of the notification. And then acquiring abnormal monitoring data which are not notified or are notified unsuccessfully from the abnormal monitoring notification table, judging abnormal data which need to be notified from the abnormal monitoring data which are not notified or are notified unsuccessfully according to the abnormal notification configuration table, reconstructing an abnormal data packet according to the abnormal data which need to be notified, and further notifying a preset user.
EXAMPLE III
As shown in fig. 3, a system anomaly monitoring device 100 is provided in a third embodiment of the present invention, and the system anomaly monitoring device 100 provided in the third embodiment of the present invention can execute the system anomaly monitoring method provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method. The system abnormality monitoring apparatus 100 includes a monitoring start module 200, an information acquisition module 300, and a monitoring execution module 400.
Specifically, the method comprises the following steps. The monitoring starting module 200 is configured to start a monitoring logic according to a preset trigger event; the information obtaining module 300 is configured to obtain configuration information of the monitoring logic from a preset abnormal monitoring configuration table; the monitoring execution module 400 is configured to execute the monitoring logic to perform system anomaly monitoring based on the configuration information.
In this embodiment, the monitoring starting module 200 is specifically configured to configure a timing monitoring task through a batch workflow task scheduler; and starting a monitoring logic according to the timing monitoring task. Wherein. The batch workflow task scheduler is Azkaban. The monitoring execution module 400 is specifically configured to execute the monitoring logic to monitor the target system based on the configuration information to obtain first monitoring data; inquiring a preset abnormal monitoring data table to judge whether the first monitoring data is abnormal monitoring data; if the first monitoring data is abnormal monitoring data, inquiring whether the abnormal monitoring data exists in a cache database; if the abnormal monitoring data does not exist in the cache database, storing the abnormal monitoring data into the cache database, storing the abnormal monitoring data for a first preset time, and storing the abnormal monitoring data into an abnormal monitoring notification table; and notifying a preset user according to the abnormal monitoring notification table.
Further, the system anomaly monitoring apparatus 100 further includes a configuration adjusting module 500 and a status writing module 600, where the configuration adjusting module 500 is configured to adjust the anomaly monitoring configuration table according to the anomaly monitoring data. The status writing module 600 is configured to write the notified result status into the exception monitoring notification table. The status writing module 600 is further configured to obtain abnormal monitoring data that is not notified or fails to be notified from the abnormal monitoring notification table according to the result status of the notification; acquiring abnormal data to be notified from the abnormal monitoring data which is not notified or fails to be notified according to an abnormal notification configuration table; and notifying a preset user according to the abnormal data needing to be notified.
In the embodiment of the present invention, the monitoring starting module 200 is configured to start a monitoring logic according to a preset trigger event; an information obtaining module 300, configured to obtain configuration information of the monitoring logic from a preset abnormal monitoring configuration table; the monitoring execution module 400 is configured to execute the monitoring logic to perform system anomaly monitoring based on the configuration information, so that the problem that customized monitoring cannot be performed in the conventional system monitoring is solved, and a customizable effect of system anomaly monitoring is achieved.
Example four
Fig. 4 is a schematic structural diagram of a system abnormality monitoring computer device according to a fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention. The computer device 12 shown in FIG. 4 is only one example and should not bring any limitations to the functionality or scope of use of embodiments of the present invention.
As shown in FIG. 4, computer device 12 is in the form of a general purpose computing device. The components of computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Computer device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. Computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
Computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with computer device 12, and/or with any devices (e.g., network card, modem, etc.) that enable computer device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, computer device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via network adapter 20. As shown, network adapter 20 communicates with the other modules of computer device 12 via bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with computer device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, implementing the methods provided by the embodiments of the present invention:
starting a monitoring logic according to a preset trigger event;
acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table;
and executing the monitoring logic to monitor system abnormity based on the configuration information.
EXAMPLE five
The fifth embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the methods provided in all the embodiments of the present invention of the present application:
starting a monitoring logic according to a preset trigger event;
acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table;
and executing the monitoring logic to monitor system abnormity based on the configuration information.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (10)

1. A system anomaly monitoring method is characterized by comprising the following steps:
starting a monitoring logic according to a preset trigger event;
acquiring configuration information of the monitoring logic from a preset abnormal monitoring configuration table;
and executing the monitoring logic to monitor system abnormity based on the configuration information.
2. The method of claim 1, wherein the initiating monitoring logic according to a preset triggering event comprises:
configuring a timing monitoring task through a batch workflow task scheduler;
and starting a monitoring logic according to the timing monitoring task.
3. The method of claim 1, wherein performing the monitoring logic for system anomaly monitoring based on the configuration information comprises:
executing the monitoring logic based on the configuration information to monitor a target system to obtain first monitoring data;
inquiring a preset abnormal monitoring data table to judge whether the first monitoring data is abnormal monitoring data;
if the first monitoring data is abnormal monitoring data, inquiring whether the abnormal monitoring data exists in a cache database;
if the abnormal monitoring data does not exist in the cache database, storing the abnormal monitoring data into the cache database, storing the abnormal monitoring data for a first preset time, and storing the abnormal monitoring data into an abnormal monitoring notification table;
and notifying a preset user according to the abnormal monitoring notification table.
4. The method of claim 3, wherein the notifying the preset user according to the abnormal monitoring notification table comprises:
and adjusting the abnormal monitoring configuration table according to the abnormal monitoring data.
5. The method according to claim 3, further comprising, after notifying a preset user according to the abnormal monitoring notification table:
and writing the notified result state into the abnormal monitoring notification table.
6. The method of claim 5, wherein writing the notified result status into the exception monitoring notification table comprises:
acquiring abnormal monitoring data which are not notified or failed to be notified from the abnormal monitoring notification table according to the result state of the notification;
acquiring abnormal data to be notified from the abnormal monitoring data which is not notified or fails to be notified according to an abnormal notification configuration table;
and notifying a preset user according to the abnormal data needing to be notified.
7. The method of claim 2, wherein the batch workflow task scheduler is Azkaban.
8. A system anomaly monitoring device, comprising:
the monitoring starting module is used for starting monitoring logic according to a preset trigger event;
the information acquisition module is used for acquiring the configuration information of the monitoring logic from a preset abnormal monitoring configuration table;
and the monitoring execution module is used for executing the monitoring logic to monitor system abnormity based on the configuration information.
9. A system anomaly monitoring device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-7.
CN202010190834.9A 2020-03-18 2020-03-18 System abnormity monitoring method, device, equipment and storage medium Pending CN111324514A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010190834.9A CN111324514A (en) 2020-03-18 2020-03-18 System abnormity monitoring method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010190834.9A CN111324514A (en) 2020-03-18 2020-03-18 System abnormity monitoring method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN111324514A true CN111324514A (en) 2020-06-23

Family

ID=71167734

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010190834.9A Pending CN111324514A (en) 2020-03-18 2020-03-18 System abnormity monitoring method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111324514A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110635956A (en) * 2019-10-23 2019-12-31 江苏国泰新点软件有限公司 Equipment management method, platform, system, equipment and storage medium
CN117528431A (en) * 2023-10-25 2024-02-06 广州市玄武无线科技股份有限公司 Data monitoring method and device of communication platform and terminal equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060179349A1 (en) * 2005-02-09 2006-08-10 Preemptive Solutions, Llc System and method for tracking exceptional states
CN106992900A (en) * 2016-01-20 2017-07-28 北京国双科技有限公司 The method and intelligent early-warning notification platform of monitoring and early warning
CN107678907A (en) * 2017-05-22 2018-02-09 平安科技(深圳)有限公司 Database business logic monitoring method, system and storage medium
CN110471824A (en) * 2019-08-19 2019-11-19 中国工商银行股份有限公司 Monitoring method, device, system, electronic equipment and computer readable storage medium
CN110851316A (en) * 2018-08-20 2020-02-28 北京京东尚科信息技术有限公司 Abnormity early warning method, abnormity early warning device, abnormity early warning system, electronic equipment and storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060179349A1 (en) * 2005-02-09 2006-08-10 Preemptive Solutions, Llc System and method for tracking exceptional states
CN106992900A (en) * 2016-01-20 2017-07-28 北京国双科技有限公司 The method and intelligent early-warning notification platform of monitoring and early warning
CN107678907A (en) * 2017-05-22 2018-02-09 平安科技(深圳)有限公司 Database business logic monitoring method, system and storage medium
CN110851316A (en) * 2018-08-20 2020-02-28 北京京东尚科信息技术有限公司 Abnormity early warning method, abnormity early warning device, abnormity early warning system, electronic equipment and storage medium
CN110471824A (en) * 2019-08-19 2019-11-19 中国工商银行股份有限公司 Monitoring method, device, system, electronic equipment and computer readable storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110635956A (en) * 2019-10-23 2019-12-31 江苏国泰新点软件有限公司 Equipment management method, platform, system, equipment and storage medium
CN117528431A (en) * 2023-10-25 2024-02-06 广州市玄武无线科技股份有限公司 Data monitoring method and device of communication platform and terminal equipment

Similar Documents

Publication Publication Date Title
US11308092B2 (en) Stream processing diagnostics
CN105357038B (en) Monitor the method and system of cluster virtual machine
US11481209B2 (en) Intelligent software agent to facilitate software development and operations
CN108595316B (en) Lifecycle management method, manager, device, and medium for distributed application
US20140075357A1 (en) Enabling real-time opertional environment conformity to an enterprise model
US7624309B2 (en) Automated client recovery and service ticketing
JP2018509709A (en) Knowledge-intensive data processing system
CN107885609B (en) Service conflict processing method and device, storage medium and electronic equipment
US11743155B2 (en) Systems and methods of monitoring and controlling remote assets
US8489941B2 (en) Automatic documentation of ticket execution
JP7289334B2 (en) Methods and apparatus, electronic devices, storage media and computer programs for testing code
CN107797887B (en) Data backup and recovery method and device, storage medium and electronic equipment
US20120222009A1 (en) Defective code warning resolution analysis
CN111324514A (en) System abnormity monitoring method, device, equipment and storage medium
US20110022439A1 (en) System for managing events in a configuration of soa governance components
WO2019195482A9 (en) Database lock
US9448998B1 (en) Systems and methods for monitoring multiple heterogeneous software applications
CN113312341A (en) Data quality monitoring method and system and computer equipment
CN112561370A (en) Software version management method and device, computer equipment and storage medium
WO2016138611A1 (en) Monitoring and reporting transmission and completeness of data upload from a source location to a destination location
CN113760491A (en) Task scheduling system, method, equipment and storage medium
US20230113860A1 (en) Proactive network application problem log analyzer
US20230023869A1 (en) System and method for providing intelligent assistance using a warranty bot
Bosch et al. Towards automated detection of data pipeline faults
CN113626288A (en) Fault processing method, system, device, storage medium and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20210304

Address after: 518000 room 602, building B, Kingdee Software Park, Keji South 12th Road, high tech Zone, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province

Applicant after: Shenzhen kaniu Technology Co.,Ltd.

Address before: 518000 room 602, building B, Kingdee Software Park, Keji South 12th Road, high tech Zone, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province

Applicant before: Shenzhen kaniu Information Technology Co.,Ltd.

RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200623