CN113162810A - Event data processing method and device - Google Patents
Event data processing method and device Download PDFInfo
- Publication number
- CN113162810A CN113162810A CN202110526193.4A CN202110526193A CN113162810A CN 113162810 A CN113162810 A CN 113162810A CN 202110526193 A CN202110526193 A CN 202110526193A CN 113162810 A CN113162810 A CN 113162810A
- Authority
- CN
- China
- Prior art keywords
- event
- fault
- event data
- events
- alarm
- 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
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 21
- 238000012545 processing Methods 0.000 claims abstract description 38
- 238000000034 method Methods 0.000 claims abstract description 24
- 230000014509 gene expression Effects 0.000 claims abstract description 6
- 230000009191 jumping Effects 0.000 claims abstract description 5
- 238000011084 recovery Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 10
- 230000000875 corresponding effect Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000012544 monitoring process Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000010219 correlation analysis Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L41/065—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving logical or physical relationship, e.g. grouping and hierarchies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
One or more embodiments of the present disclosure provide an event data processing method and device, where the event data processing method includes: collecting event data of network element equipment; identifying the event data through a pre-established event processing strategy to obtain fault events, establishing an incidence relation of the fault events with incidence relation in the fault events, and determining a fault source according to a plurality of fault events with incidence relation, wherein the event processing strategy at least comprises two regular expressions with jumping, branching or backtracking relation; based on the alarm message sent by the fault source, the method can accurately identify the fault event from a large amount of event data and locate the fault source, thereby ensuring the reliability of the system.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to an event data processing method and device.
Background
Nowadays, cloud computing is increasingly popularized, cloud resources are increasingly more, IT resources are built in an accumulating way year by year, IT resources in a cloud environment are gradually and greatly increased, but because IT resources are high in complexity and poor in stability, unified management and control are difficult to achieve, at present, the traditional mode for monitoring and managing IT resource data is low in efficiency, actual requirements cannot be met, especially when a fault occurs in a system, a fault source cannot be determined according to the system data, and therefore fault events cannot be effectively processed, and therefore an efficient event data processing method needs to be provided.
Disclosure of Invention
The present disclosure aims to provide an event data processing method and device, so as to solve the problem of low monitoring efficiency of IT resource data in the related art.
According to one or more embodiments of the present disclosure, there is provided an event data processing method including: collecting event data of network element equipment; identifying the event data through a pre-established event processing strategy to obtain fault events, establishing an incidence relation of the fault events with incidence relation in the fault events, and determining a fault source according to a plurality of fault events with incidence relation, wherein the event processing strategy at least comprises two regular expressions with jumping, branching or backtracking relation; and sending out an alarm message based on the fault source.
Optionally, the method further includes: after the event data of the network element equipment is collected, if the target event data is continuously collected within the first preset time for a preset number of times, the priority of the target event is improved.
Optionally, the method further includes: after event data of the network element equipment is collected, setting processing time for the event according to the priority of the event; and if the event processing time is up and the event is not processed, sending an urging message.
Optionally, the method further includes: after the event data is identified through a pre-established event processing strategy to obtain a fault event, if a message for closing the fault event is not received within a second preset time period; the level of the failure event is increased.
Optionally, the method further includes: after collecting event data of network element equipment, if a recovery event occurs, associating the recovery event with an original fault event corresponding to the recovery event, and updating the state of the original fault event.
Optionally, sending an alarm message based on the fault source includes: and sending the alarm message through different alarm modes and different alarm contents according to the occurrence time of the fault event and the level of the fault event.
Optionally, the event data of the network element device at least includes one of the following: event sequence number, network element name, event occurrence time, original alarm type, original alarm level, alarm content and alarm information source.
Optionally, the method further includes: after the event data is identified through a pre-established event processing strategy to obtain fault information, for repeated fault events, keeping fault items unchanged, and recording the first occurrence time, the last occurrence time and the occurrence times of the fault events.
Optionally, the establishing an association relationship for the fault event having an association relationship in the fault events through a pre-established event processing policy includes: and establishing an association relation between fault events with the same Internet Protocol (IP) address and the same fault type.
According to one or more embodiments of the present disclosure, there is provided an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing any of the event data processing methods as described above when executing the program.
The event data processing method according to one or more embodiments of the present disclosure identifies a fault event from collected event data based on a pre-established event processing policy, associates the fault events having an association relationship among the fault events to determine a fault source according to the association relationship among the fault events, and performs an alarm based on the fault source after determining the fault source. Therefore, the fault event can be accurately identified and the fault source can be positioned from a large amount of event data, and the reliability of the system is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow diagram illustrating a method of event data processing in accordance with one or more embodiments of the present disclosure;
FIG. 2 is a schematic diagram illustrating an event handling strategy according to one or more embodiments of the present disclosure;
FIG. 3 is a flow diagram illustrating an event escalation in accordance with one or more embodiments of the present disclosure;
FIG. 4 is a flow diagram illustrating an event escalation in accordance with one or more embodiments of the present disclosure;
fig. 5 is a block diagram illustrating an electronic device in accordance with one or more embodiments of the present disclosure.
Detailed Description
The technical solutions of the present disclosure will be described clearly and completely with reference to the following embodiments, and it should be understood that the described embodiments are only some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
In the description of the present disclosure, it is to be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", and the like, indicate orientations or positional relationships based on those shown in the drawings, and are used merely for convenience of description and for simplicity of description, and do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore, should not be considered as limiting the present disclosure.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying 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 present disclosure, "a plurality" means two or more unless specifically limited otherwise. Furthermore, the terms "mounted," "connected," and "connected" are to be construed broadly and may, for example, be fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meaning of the above terms in the present disclosure can be understood in specific instances by those of ordinary skill in the art.
Fig. 1 is a flowchart illustrating an event data processing method according to one or more embodiments of the present disclosure, as shown in fig. 1, the method including:
step 101: collecting event data of network element equipment;
for example, IT is possible to automatically discover and adapt IT resources of a data center through a data acquisition toolset built in the system, and automatically adapt acquisition scheduling commands of each resource according to a built-in KPI (Key Performance Indicators)/KQI (Key quality Indicators) acquisition policy of each management object through an adaptive and intelligent acquisition scheduling algorithm, so as to realize active real-time acquisition of operation basic data of each IT resource, and perform preliminary data preprocessing and data caching.
Meanwhile, various TRAP (TRAP), SYSLOG (system log), custom interface and other types of high-performance acquisition engines are built in the system, so that software and hardware faults, operation events, alarm events and other passive acquisition in the operation process of the IT resources can be realized, and key information such as message identification, message segments, message attributes and the like in each protocol can be automatically analyzed according to the type and the message protocol of each device, and centralized dynamic processing is performed.
The data collection toolset can support and adapt to various management interface protocols, such as: support SNMP (Simple Network Management Protocol), CLI (Command-Line Interface), WMI (Windows Management instrumentation, Windows Management specification), ODBC (Open Database Connectivity), JDBC (Java Database Connectivity), TRAP, SNTP (Simple Network Time Protocol), NTP (Network Time Protocol), API (Application Programming Interface), etc., so that device information, configuration information, state information, performance information, and alarm information of each IT resource can be collected.
For example, the collection of event data may be performed by active status polling, by SNMP Trap, by SYSLOG, or by a log file.
In one or more embodiments of the present disclosure, the event data of the network element device includes at least one of:
event sequence number, network element name, event occurrence time, original alarm type, original alarm level, alarm content and alarm information source.
Step 102: identifying the event data through a pre-established event processing strategy to obtain fault events, establishing an incidence relation of the fault events with incidence relation in the fault events, and determining a fault source according to a plurality of fault events with incidence relation, wherein the event processing strategy at least comprises two regular expressions with jumping, branching or backtracking relation;
the event processing strategy can be a rule-based event processing engine and can be a user-defined event processing strategy, and the event processing strategy can analyze and process events by matching input event data with a preset strategy and measuring a series of rule expressions in strategy definition so as to quickly position fault reasons. As shown in fig. 2, a policy consists of a series of rules. A rule is an expression that can be measured. The rules support the relation of jumping, branching and backtracking. A policy that is defined correctly should have a unique fixed output given the input conditions.
Based on the event data acquired in step 101, according to the KPI/KQI index system of each resource, the data is calculated, processed, and analyzed, and converted into a system standard data model for analysis, and a uniform information model is established to achieve consistent interpretation and storage of the data. By establishing a uniform database table, fields and the like, the operation and maintenance management related information such as configuration information, equipment state, alarm condition and the like can be collected, analyzed and translated, various data are compared, analyzed and associated, the state and the configuration information of the equipment are accurately reflected, and therefore risk identification and alarm information push can be carried out according to different alarm rules.
In step 102, event data may be entered into an event handling policy, which may identify a fault corresponding to the event, e.g., may identify a fault identification field corresponding to the event. The fault events having the association relationship may be, for example, fault event data having partial identity.
For example, it is assumed that a network fault of a plurality of devices is known according to collected event data, and it is determined that the plurality of devices are all connected to the same switch, and it is indicated that the switch has a network fault according to the collected event data, so that an association relationship between the network fault of the plurality of devices and the network fault of the switch can be established, and analysis is performed based on the association relationship, and it can be determined that the fault source is the switch.
Step 103: and sending out an alarm message based on the fault source.
The event data processing method according to one or more embodiments of the present disclosure identifies a fault event from collected event data based on a pre-established event processing policy, associates the fault events having an association relationship among the fault events to determine a fault source according to the association relationship among the fault events, and performs an alarm based on the fault source after determining the fault source. Therefore, the fault event can be accurately identified and the fault source can be positioned from a large amount of event data, and the reliability of the system is ensured.
In addition, by customizing the event processing strategy, the fault events are intelligently analyzed and automatically processed according to the incidence relation among the fault events. The high-performance memory database technology can be adopted, the concurrent processing capacity of the whole system is improved, the requirement of large-scale comprehensive facility management is met, and meanwhile the expansibility and flexibility of the platform can be improved. Through the data synchronization technology, the regular update and automatic synchronization of the equipment configuration data and the equipment management information base can be realized, so that the data in the equipment management information base is ensured to be consistent with the actual environment.
In one or more embodiments of the present disclosure, the event data processing method may further include:
after the event data of the network element equipment is collected, if the target event data is continuously collected within the first preset time for a preset number of times, the priority of the target event is improved. Taking the example shown in fig. 3, if an event is triggered three times (which is an example of the preset times) within 15 minutes (which is an example of the first preset time period), the event is upgraded.
In one or more embodiments of the present disclosure, the event data processing method may further include:
after event data of the network element equipment is collected, setting processing time for the event according to the priority of the event; and if the event processing time is up and the event is not processed, sending an urging message. For example,
the system can support the priority Level of the event defined by the user, and can define different processing time for the event with different priority according to SLA (Service-Level agent). When the expected time of the event is not solved, the system can automatically promote the event in an Email, short message and other modes, and can also automatically or manually upgrade the event to a designated person for processing.
In one or more embodiments of the present disclosure, the event data processing method may further include:
identifying the event data through a pre-established event identification strategy, and if a message for closing the fault event is not received within a second preset time period after the fault event is obtained;
the level of the failure event is increased. Taking the example shown in fig. 4, if the event triggered within 10 minutes (which is one example of the second preset time period) is not turned off, the event is upgraded.
In one or more embodiments of the present disclosure, the event data processing method may further include:
after collecting event data of network element equipment, if a recovery event occurs, associating the recovery event with an original fault event corresponding to the recovery event, and updating the state of the original fault event. For example, the system automatically processes the related events according to the event processing policy, such as when a recovery event occurs, automatically associating the recovery event to the original fault event, and setting the state of the original fault event to clear, which indicates that the fault has recovered.
In one or more embodiments of the present disclosure, the issuing of the warning message based on the failure source may include: and sending the alarm message through different alarm modes and different alarm contents according to the occurrence time of the fault event and the level of the fault event. For example, assuming that events are classified into 5 levels from high to low in the hierarchy, the conditions for issuing an alarm message, the fault notification manner, the fault notification content requirement, and the implementation are exemplified as shown in table 1 below.
TABLE 1
All windows and sounds need to specify the address of the notified client machine in advance, and the network manager sends the sounds to the specified machine. The short message automatic alarm needs to record the mobile phone numbers of the monitoring personnel and the supervisor in advance and give the corresponding relation between the event and the monitoring personnel and the supervisor.
In one or more embodiments of the present disclosure, the event data processing method may further include:
after the event data is identified through a pre-established event processing strategy to obtain fault information, for repeated fault events, keeping fault items unchanged, and recording the first occurrence time, the last occurrence time and the occurrence times of the fault events. For example, only one collected repeated fault event can be reserved in the fault database based on the automatic compression (De-duplication) function of the in-memory database, and the time of the first occurrence and the time and the occurrence number of the last occurrence are recorded in the fault database.
In one or more embodiments of the present disclosure, the event data processing method may further include: establishing an association relationship for a fault event with an association relationship in the fault events through a pre-established event processing policy, which may include:
and establishing an association relation between the protocol IP addresses with interconnection between the same networks and the fault events with the same fault types. That is, the fault events corresponding to the same IP address and having the same fault type are regarded as related events, and the relationship between these events is established. For example, the system can automatically associate the event information with the resource information (such as the location of the device, the responsible person, and the like) related in the line according to the configuration information in the configuration management database, so that the manager can directly view the content related to the event while receiving the alarm without performing additional query work.
In one or more embodiments of the present disclosure, the correlation analysis of events may include: the similar alarm correlation is carried out, the fault and the recovery event thereof are automatically correlated, and the state is synchronously updated; analyzing a fault source, finding out a specific position where the fault occurs, and associating other related events caused by the specific position; and (4) analyzing the service correlation, finding out information of services, departments and the like influenced by the fault, and taking different measures according to the range and the degree of the influence.
In one or more embodiments of the present disclosure, when the original event information is acquired through the event collector, since the event information is too professional to be visually recognized by the service personnel, chinese translation may be performed by matching with the original event content. Translation of fields including node, type, and level of the event may be performed.
One or more embodiments of the present disclosure also provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the program, the processor implements any one of the event data processing methods described above.
It should be noted that the method of the embodiments of the present disclosure may be executed by a single device, such as a computer or a server. The method of the embodiment can also be applied to a distributed scene and completed by the mutual cooperation of a plurality of devices. In such a distributed scenario, one of the devices may only perform one or more steps of the method of the embodiments of the present disclosure, and the devices may interact with each other to complete the method.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Fig. 5 is a schematic diagram illustrating a more specific hardware structure of an electronic device according to this embodiment, where the electronic device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.
The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present disclosure, and not for limiting the same; while the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present disclosure.
Claims (10)
1. An event data processing method, comprising:
collecting event data of network element equipment;
identifying the event data through a pre-established event processing strategy to obtain fault events, establishing an incidence relation of the fault events with incidence relation in the fault events, and determining a fault source according to a plurality of fault events with incidence relation, wherein the event processing strategy at least comprises two regular expressions with jumping, branching or backtracking relation;
and sending out an alarm message based on the fault source.
2. The method of claim 1, further comprising:
after the event data of the network element equipment is collected, if the target event data is continuously collected within the first preset time for a preset number of times, the priority of the target event is improved.
3. The method of claim 1, further comprising:
after event data of the network element equipment is collected, setting processing time for the event according to the priority of the event;
and if the event processing time is up and the event is not processed, sending an urging message.
4. The method of claim 1, further comprising:
after the event data is identified through a pre-established event processing strategy to obtain a fault event, if a message for closing the fault event is not received within a second preset time period;
the level of the failure event is increased.
5. The method of claim 1, further comprising:
after collecting event data of network element equipment, if a recovery event occurs, associating the recovery event with an original fault event corresponding to the recovery event, and updating the state of the original fault event.
6. The method of claim 1, wherein issuing an alarm message based on the failure source comprises:
and sending the alarm message through different alarm modes and different alarm contents according to the occurrence time of the fault event and the level of the fault event.
7. The method of claim 1, wherein the event data of the network element device comprises at least one of:
event sequence number, network element name, event occurrence time, original alarm type, original alarm level, alarm content and alarm information source.
8. The method of claim 1, further comprising:
after the event data is identified through a pre-established event processing strategy to obtain fault information, for repeated fault events, keeping fault items unchanged, and recording the first occurrence time, the last occurrence time and the occurrence times of the fault events.
9. The method according to claim 1, wherein the establishing of the association relationship for the fault events having the association relationship among the fault events through the pre-established event processing policy comprises:
and establishing an association relation between fault events with the same Internet Protocol (IP) address and the same fault type.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the event data processing method according to any one of claims 1 to 9 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110526193.4A CN113162810A (en) | 2021-05-14 | 2021-05-14 | Event data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110526193.4A CN113162810A (en) | 2021-05-14 | 2021-05-14 | Event data processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113162810A true CN113162810A (en) | 2021-07-23 |
Family
ID=76875102
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110526193.4A Pending CN113162810A (en) | 2021-05-14 | 2021-05-14 | Event data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113162810A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001811A (en) * | 2012-12-31 | 2013-03-27 | 北京启明星辰信息技术股份有限公司 | Method and device for fault locating |
| CN103412805A (en) * | 2013-07-31 | 2013-11-27 | 交通银行股份有限公司 | IT (information technology) fault source diagnosis method and IT fault source diagnosis system |
| CN104244293A (en) * | 2013-06-06 | 2014-12-24 | 中国移动通信集团广东有限公司 | Network node alarming method and system |
| US20150121136A1 (en) * | 2013-10-30 | 2015-04-30 | Samsung Sds Co., Ltd. | System and method for automatically managing fault events of data center |
| CN105868876A (en) * | 2015-01-21 | 2016-08-17 | 国家电网公司 | Centralized operation and maintenance fault closed-loop processing method based on process monitoring |
-
2021
- 2021-05-14 CN CN202110526193.4A patent/CN113162810A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103001811A (en) * | 2012-12-31 | 2013-03-27 | 北京启明星辰信息技术股份有限公司 | Method and device for fault locating |
| CN104244293A (en) * | 2013-06-06 | 2014-12-24 | 中国移动通信集团广东有限公司 | Network node alarming method and system |
| CN103412805A (en) * | 2013-07-31 | 2013-11-27 | 交通银行股份有限公司 | IT (information technology) fault source diagnosis method and IT fault source diagnosis system |
| US20150121136A1 (en) * | 2013-10-30 | 2015-04-30 | Samsung Sds Co., Ltd. | System and method for automatically managing fault events of data center |
| CN105868876A (en) * | 2015-01-21 | 2016-08-17 | 国家电网公司 | Centralized operation and maintenance fault closed-loop processing method based on process monitoring |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108039957B (en) | Intelligent analysis system for complex network traffic packet | |
| CN108833137A (en) | A kind of flexibility micro services Monitoring framework framework | |
| CN107958337A (en) | A kind of information resources visualize mobile management system | |
| CN112311617A (en) | Configured data monitoring and alarming method and system | |
| CN104243185B (en) | A kind of experience type service monitoring system | |
| CN107957940B (en) | Test log processing method, system and terminal | |
| CN108809701A (en) | A kind of data center's wisdom data platform and its implementation | |
| US20200159607A1 (en) | Veto-based model for measuring product health | |
| CN110209518A (en) | A kind of multi-data source daily record data, which is concentrated, collects storage method and device | |
| CN111078455A (en) | Abnormal behavior sequence correlation processing method and device based on time axis, equipment and storage medium | |
| CN112256542A (en) | eBPF-based micro-service system performance detection method, device and system | |
| CN107635003A (en) | The management method of system journal, apparatus and system | |
| CN112596975A (en) | Method, system, equipment and storage medium for monitoring network equipment | |
| CN111740868A (en) | Alarm data processing method and device and storage medium | |
| CN114048090A (en) | K8S-based container cloud platform monitoring method and device and storage medium | |
| CN115396289A (en) | Fault alarm determination method and device, electronic equipment and storage medium | |
| CN111339466A (en) | Interface management method and device, electronic equipment and readable storage medium | |
| CN111597091A (en) | Data monitoring method and system, electronic equipment and computer storage medium | |
| CN111176950A (en) | Method and equipment for monitoring network card of server cluster | |
| CN113162810A (en) | Event data processing method and device | |
| CN110633191A (en) | Method and system for monitoring service health degree of software system in real time | |
| CN111817865A (en) | Method for monitoring network management equipment and monitoring system | |
| CN114338335A (en) | Integrated monitoring system and method | |
| CN115102828A (en) | Fault analysis method and device | |
| CN109120439B (en) | Distributed cluster alarm output method, device, equipment and readable storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210723 |