CN112181787B - Alarm processing method and device for abnormal data, electronic equipment and storage medium - Google Patents

Alarm processing method and device for abnormal data, electronic equipment and storage medium Download PDF

Info

Publication number
CN112181787B
CN112181787B CN202010923047.0A CN202010923047A CN112181787B CN 112181787 B CN112181787 B CN 112181787B CN 202010923047 A CN202010923047 A CN 202010923047A CN 112181787 B CN112181787 B CN 112181787B
Authority
CN
China
Prior art keywords
abnormal data
data
source
abnormal
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.)
Active
Application number
CN202010923047.0A
Other languages
Chinese (zh)
Other versions
CN112181787A (en
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.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet 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 Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202010923047.0A priority Critical patent/CN112181787B/en
Publication of CN112181787A publication Critical patent/CN112181787A/en
Application granted granted Critical
Publication of CN112181787B publication Critical patent/CN112181787B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324Display of status information
    • G06F11/327Alarm or error message display
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Mathematical Physics (AREA)
  • Alarm Systems (AREA)

Abstract

The disclosure relates to an alarm processing method and device for abnormal data, electronic equipment and a storage medium, and belongs to the technical field of computer application. Wherein the method comprises the following steps: acquiring an alarm message of source abnormal data; according to the alarm message, establishing a life cycle of the alarm message; if associated anomaly data associated with the source anomaly data is detected during the life cycle, monitoring the source anomaly data and the associated anomaly data; when the source abnormal data is recovered, the alarm message is closed, and the life cycle is ended. Therefore, through the alarm processing method of the abnormal data, the associated abnormal data acquired in the life cycle corresponding to the source abnormal data is monitored only without sending an alarm message, so that the alarm notification quantity is greatly reduced, and the monitoring effect of the abnormal data is improved.

Description

Alarm processing method and device for abnormal data, electronic equipment and storage medium
Technical Field
The disclosure relates to the technical field of computer application, and in particular relates to an alarm processing method and device for abnormal data, electronic equipment and a storage medium.
Background
With the vigorous development of internet technology, internet products and services are endless, and users generally tend to select products and services with stable services and high quality. The data monitoring alarm is an important means for guaranteeing the product quality and improving the service stability, namely, the monitoring rule is formulated by taking the data as a basis, and an alarm notification is sent after abnormal data of the triggering rule is detected.
In the related art, the traditional alarm service can immediately send alarm notification after detecting abnormal data, so that the alarm notification amount is large, the importance of related responsible personnel on the alarm notification is reduced, and the monitoring effect is restricted.
Disclosure of Invention
The disclosure provides an alarm processing method, an alarm processing device, an electronic device, a storage medium and a computer program product for abnormal data, so as to at least solve the problems that in the related art, the traditional alarm service of immediately sending alarm notification after detecting abnormal data easily causes large alarm notification amount, and the importance of related responsible personnel on the alarm notification is reduced, thereby restricting the monitoring effect. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided an alarm processing method for abnormal data, including: acquiring an alarm message of source abnormal data; establishing the life cycle of the alarm message according to the alarm message; monitoring the source anomaly data and the associated anomaly data if associated anomaly data associated with the source anomaly data is detected during the lifecycle; and closing the alarm message and ending the lifecycle when the source exception data is restored.
Optionally, in a possible implementation manner of the embodiment of the first aspect of the present disclosure, the monitoring the source abnormal data and the associated abnormal data includes:
adding the associated exception data to an exception data maintenance table;
monitoring each associated abnormal data in the abnormal data maintenance table; and
and when the processing time corresponding to the associated abnormal data reaches a first preset time, pushing a processing reminding message of the associated abnormal data.
Optionally, in another possible implementation manner of the embodiment of the first aspect of the present disclosure, the acquiring the alarm message of the source abnormal data includes:
receiving abnormal data; and
and if the abnormal data is not in the fluctuation range and the upstream abnormal data related to the abnormal data does not exist, determining the abnormal data as the source abnormal data and sending the alarm message.
Optionally, in a further possible implementation manner of the embodiment of the first aspect of the present disclosure, the source exception data is upstream exception data of the associated exception data.
Optionally, in a further possible implementation manner of the embodiment of the first aspect of the present disclosure, the detecting, during the life cycle, associated abnormal data related to the source abnormal data includes:
Acquiring configuration parameters of the source abnormal data;
acquiring configuration parameters of new abnormal data detected in the life cycle;
and if the source abnormal data is determined to be upstream abnormal data of the new abnormal data according to a preset configuration table, the configuration parameters of the source abnormal data and the configuration parameters of the new abnormal data, determining the new abnormal data to be associated abnormal data of the source abnormal data.
Optionally, in a further possible implementation manner of the embodiment of the first aspect of the present disclosure, the method further includes:
if no abnormal data is associated in the abnormal data maintenance table and the abnormal data is not received within a second preset time, closing the abnormal data maintenance table.
According to a second aspect of the embodiments of the present disclosure, there is provided an alarm processing apparatus for abnormal data, including: an acquisition module configured to perform the step of acquiring an alarm message of source abnormality data; a setup module configured to perform the step of establishing a lifecycle of the alarm message from the alarm message; a monitoring module configured to perform a step of monitoring the source abnormal data and the associated abnormal data when the associated abnormal data related to the source abnormal data is detected during the life cycle; and a first shutdown module configured to perform the steps of shutting down the alarm message and ending the lifecycle when the source exception data is restored.
Optionally, in a possible implementation manner of the embodiment of the second aspect of the present disclosure, the monitoring module includes:
an adding unit configured to perform a step of adding the associated abnormal data to an abnormal data maintenance table;
a monitoring unit configured to perform a step of establishing monitoring for each associated abnormal data in the abnormal data maintenance table; and
and the pushing unit is configured to perform the step of pushing the processing reminding message of the associated abnormal data when the processing time corresponding to the associated abnormal data reaches a first preset time.
Optionally, in another possible implementation manner of the embodiment of the second aspect of the present disclosure, the acquiring module includes:
a receiving unit configured to perform a step of receiving the abnormal data; and
a first determination unit configured to perform a step of determining the abnormal data as the source abnormal data and transmitting the alarm message when the abnormal data is not within a fluctuation range and there is no upstream abnormal data related to the abnormal data.
Optionally, in still another possible implementation manner of the embodiment of the second aspect of the present disclosure, the source exception data is upstream exception data of the associated exception data.
Optionally, in a further possible implementation manner of the embodiment of the second aspect of the present disclosure, the monitoring module includes:
a first acquisition unit configured to perform a step of acquiring configuration parameters of the source abnormality data;
a second acquisition unit configured to perform a step of acquiring configuration parameters of new abnormal data detected during the life cycle;
a second determining unit configured to perform a step of determining the new abnormal data as associated abnormal data of the source abnormal data when determining that the source abnormal data is upstream abnormal data of the new abnormal data according to a preset configuration table, a configuration parameter of the source abnormal data, and a configuration parameter of the new abnormal data.
Optionally, in a further possible implementation manner of the embodiment of the second aspect of the present disclosure, the apparatus further includes:
and the second closing module is configured to execute the steps of closing the abnormal data maintenance table when no abnormal data is associated in the abnormal data maintenance table and the abnormal data is not received any more within a second preset time.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the alarm processing method of exception data as described above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the alarm processing method of abnormal data as described previously.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product which, when executed by a processor of an electronic device, enables the electronic device to perform the alarm processing method of anomaly data as previously described.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: when the alarm information of the source abnormal data is acquired, a life cycle corresponding to the alarm information is established, and when the associated abnormal data related to the source abnormal data is detected in the life cycle, the associated abnormal data is recorded for analysis, alarm notification is not sent until the source data is recovered, and the life cycle is ended. Therefore, the related abnormal data acquired in the life cycle corresponding to the source abnormal data is monitored only without sending an alarm message, so that the alarm notification quantity is greatly reduced, and the monitoring effect of the abnormal data is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is a flow chart illustrating a method of alarm processing of exception data according to an exemplary embodiment.
FIG. 2 is a schematic diagram illustrating a lifecycle mode, according to an exemplary embodiment.
FIG. 3 is a flowchart illustrating another method of alarm processing of exception data, according to an exemplary embodiment.
Fig. 4 is a flowchart illustrating yet another alarm processing method of abnormal data according to an exemplary embodiment.
FIG. 5 is a block diagram of an alarm processing device for exception data, according to an exemplary embodiment.
Fig. 6 is a block diagram of an electronic device, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
Fig. 1 is a flowchart illustrating a method of alarm processing of abnormal data according to an exemplary embodiment, which is used in an electronic device, as shown in fig. 1, and includes the following steps.
In step 101, an alarm message of source anomaly data is acquired.
It should be noted that, the method for processing the abnormal data according to the embodiment of the present disclosure may be executed by the apparatus for processing the abnormal data according to the embodiment of the present disclosure, and the apparatus for processing the abnormal data according to the embodiment of the present disclosure may be configured in any electronic device to execute the method for processing the abnormal data according to the embodiment of the present disclosure. The alarm processing method of the abnormal data in the embodiment of the present disclosure may be applied in a monitoring scenario of abnormal alarm of any internet product, so that the alarm processing device of the abnormal data in the embodiment of the present disclosure may be configured in a server of any internet product to monitor the abnormal alarm of the internet product, that is, an execution subject of the alarm processing method of the abnormal data in the embodiment of the present disclosure may be a server.
The source abnormal data may be data whose data value meets a preset monitoring rule and is not related to other source abnormal data corresponding to a life cycle existing at present. That is, the source abnormality data is abnormality data whose alarm cause is different from the alarm cause of each life cycle currently existing.
In the embodiment of the disclosure, a preset monitoring rule may be set and stored in the execution subject server according to an actual monitoring requirement, so that the server may determine, according to the preset monitoring rule, abnormal data whose data value meets the preset monitoring rule. After the abnormal data is acquired, if no life cycle which is not finished exists currently, the currently acquired abnormal data can be determined to be source abnormal data, and an alarm message of the source abnormal data is generated; if the life cycle which is not finished exists currently, whether the obtained abnormal data is related to the source abnormal data corresponding to the life cycle which exists currently or not can be further judged, if not, the obtained abnormal data can be determined to prompt a new fault type, namely, the alarm reason of the source abnormal data corresponding to the life cycle which exists currently is different, so that the obtained abnormal data can be determined to be the source abnormal data, and an alarm message of the source abnormal data is generated, so that the necessary alarm message is prevented from being missed.
As a possible implementation manner, after generating the alarm message of the source abnormal data, the server may send the alarm message to the client, so as to remind the user of abnormal service, and perform maintenance and processing in time. The user may be a maintainer, a developer, etc. of the internet product, and the client may be an application program used by the maintainer and the developer to maintain the internet product, or a terminal device such as a computer, a mobile phone, etc.
In step 102, a lifecycle of the alarm message is established based on the alarm message.
In the embodiment of the disclosure, after generating the alarm message, the server may establish a life cycle of the alarm message according to a generation time of the alarm message, and determine the generation time of the alarm message as a start time corresponding to the life cycle of the alarm message.
In step 103, if associated anomaly data associated with the source anomaly data is detected during the life cycle, the source anomaly data and the associated anomaly data are monitored.
In the embodiment of the disclosure, after the life cycle of the alarm message is established, if new abnormal data is detected when the life cycle is not finished, whether the new abnormal data is related to the source abnormal data corresponding to the life cycle can be judged first, if so, the fault type indicated by the new abnormal data can be determined to be the same as or related to the fault type indicated by the source abnormal data, so that the new abnormal data can be determined to be related abnormal data. Since the association of the anomaly data with the source anomaly data may be caused by the same fault, the alarm message may be generated only once to reduce the number of alarm messages and not cause missing necessary alarm information. After determining associated anomaly data associated with the source anomaly data, the associated anomaly data can be recorded for subsequent attribution, association, analysis, etc. of the fault.
In the embodiment of the disclosure, after the associated abnormal data related to the source abnormal data is acquired, each associated abnormal data may be monitored to record the data values of the source abnormal data and the associated abnormal data in the life cycle.
As a possible implementation manner, the frequency of monitoring the source abnormal data and the associated abnormal data may be preset, that is, the data values of the source abnormal data and the associated abnormal data may be obtained and recorded at the preset frequency, so as to monitor the states of the source abnormal data and the associated abnormal data, such as the change trend of the source abnormal data and the associated abnormal data in the life cycle, and further, when the life cycle is not finished, follow-up is performed on the alarm message according to the states of the source abnormal data and the associated abnormal data, so that the alarm message may be processed in time.
When the source anomaly data is recovered, the alarm message is turned off and the lifecycle is ended, step 104.
In the embodiment of the disclosure, when the source abnormal data is restored to the normal value, that is, when the data value of the source abnormal data no longer accords with the preset monitoring rule, it may be determined that the fault triggering the alarm message has been eliminated, so that the alarm message may be closed, and the life cycle of the alarm message may be ended. Therefore, the alarm is carried out only once on the associated abnormal data in the life cycle of the alarm message, and the number of the alarm messages is greatly reduced; and after the life cycle of the alarm message is finished, the alarm of the abnormal data acquired later is not influenced, so that the alarm message is prevented from being missed when the same fault is generated again after the fault is solved.
As a possible implementation manner, the alarm message may be processed manually, so that when an alarm message end instruction sent by the client is obtained, it may be determined that the alarm message has been processed, so that source abnormal data may be determined to be recovered, and the alarm message may be closed, and the lifecycle may be ended.
As another possible implementation manner, the server may further determine whether the source abnormal data has been restored to the normal range according to the monitoring data of the source abnormal data and the associated abnormal data, and determine that the source abnormal data is restored when it is detected that the source abnormal data has been restored to the normal range, so that the alarm message may be automatically turned off, and the life cycle may be ended.
For example, as shown in fig. 2, a schematic diagram of a lifecycle mode is shown, according to an exemplary embodiment. Wherein 100 is life cycle 1, 200 is life cycle 2, and 300 is life cycle 3;110 is source abnormal data corresponding to the life cycle 1, and 120 is associated abnormal data of the source abnormal data 110; 210 lifecycle 2, 220, 230, 240 are associated anomaly data for the source anomaly data 210; 310 are source anomaly data corresponding to lifecycle 3, and 320, 330 are associated anomaly data for source anomaly data 310. In the conventional alarm mode, alarm messages are generated when various data 110, 120, 210, 220, 230, 240, 310, 320, 330 are acquired, whereas in the life cycle alarm mode, only alarm messages are generated when source abnormality data 110, source abnormality data 210, source abnormality data 310 are acquired, thereby greatly reducing the number of alarm messages. As can be seen from fig. 2, the end mode of the lifecycle 1 is data recovery, that is, when the server determines that the source abnormal data 110 is recovered to be normal according to the monitoring data of the source abnormal data 110 and the associated abnormal data 120, the lifecycle 1 can be automatically ended; the ending modes of the life cycle 2 and the life cycle 3 are artificial ending, that is, the server can end the life cycle 2 and the life cycle 3 when acquiring the alarm message ending instructions corresponding to the life cycle 2 and the life cycle 3 sent by the client.
According to the alarm processing method for the abnormal data, when the alarm message of the source abnormal data is acquired, the life cycle corresponding to the alarm message is established, when the associated abnormal data related to the source abnormal data is detected in the life cycle, the associated abnormal data is recorded only so as to be convenient to analyze, an alarm notification is not sent, and the life cycle is ended until the source data is recovered. Therefore, the related abnormal data acquired in the life cycle corresponding to the source abnormal data is monitored only without sending an alarm message, so that the alarm notification quantity is greatly reduced, and the monitoring effect of the abnormal data is improved.
In one possible implementation form of the present disclosure, a fluctuation range in which normal values of various types of data are located may be preset, so as to determine abnormal data according to the preset fluctuation range.
Fig. 3 is a flowchart illustrating another method of alarm processing of abnormal data, which is used in an electronic device, as shown in fig. 3, according to an exemplary embodiment, including the following steps.
In step 401, anomaly data is received.
In step 402, if the anomaly data is not within the fluctuation range and there is no upstream anomaly data associated with the anomaly data, the anomaly data is determined to be source anomaly data and a warning message is sent.
It should be noted that if an exception occurs in data B due to an exception in data a, data B may be the upstream exception data of data a. In the embodiment of the disclosure, the upstream data corresponding to each data may be configured according to actual service requirements; for data containing strict relation specifications, the data source and the data dimension of the stored data can be analyzed to automatically determine the upstream data corresponding to each data.
For example, the network interface data is data including strict specifications of relationship, where the data dimension affecting the success rate of the network interface may be many, such as domain name, content distribution network, network type, region, machine room information, etc., so that the success rate of the network interface may be configured as upstream data of the data such as domain name, content distribution network, network type, region, machine room information, etc.
In the embodiment of the present disclosure, the server may collect the data value of each data in the system at a preset frequency, and if the data value of a certain data obtained at the current moment is not located within the fluctuation range, the data may be determined as abnormal data.
As a possible implementation manner, the fluctuation range may be preset to [ -x,3x ], where x is a data average value of 7 days of data, that is, if the data value of the data is more than 200% greater than the data average value of 7 days, it may be determined that the data is abnormal data at the current moment; or, an open source time sequence estimation tool (such as fbppropset) can be used to estimate the fluctuation range of the data, and then determine that the data is abnormal at the current moment when the data value deviates from the upper and lower limits of the estimated fluctuation range by 100%.
In the embodiment of the disclosure, after the abnormal data is acquired at the current moment, whether an unfinished life cycle exists at the current moment can be further determined, if not, the abnormal data can be determined to be source abnormal data, and an alarm message of the source abnormal data is generated and sent to the client; if the life cycle is not ended, whether the life cycle of the current moment contains upstream abnormal data related to the abnormal data can be further judged, if not, the abnormal data can be determined to be source abnormal data, and a warning message is sent.
For example, as shown in fig. 2, at the time of acquiring the source abnormal data 110, 210, 310, it may be determined that there is no unfinished life cycle currently, so that when the data 110, 210, 310 is acquired, the data 110, 210, 310 may be determined as the source abnormal data, and an alarm message is sent; while at the time the anomalous data 120 is acquired, there is an unexpired lifecycle 100 and the source anomalous data 110 is upstream anomalous data of the anomalous data 120, so that it can be determined that the anomalous data 120 is not source anomalous data.
It should be noted that, the monitoring rule for determining whether the data is abnormal data may include, but is not limited to, the above-listed cases. In actual use, an appropriate monitoring rule can be determined according to actual needs and specific service scenarios, which is not limited by the embodiment of the disclosure.
According to the embodiment of the disclosure, the source abnormal data is determined by presetting the normal fluctuation range of each data and the association relation among the data, so that the time for sending the alarm message is reliably determined, the missing of alarm or repeated alarm is avoided, the alarm quantity is reduced, and the reliability and the importance degree of the alarm are further improved. And the association abnormal data of the source abnormal data is determined according to the causal relationship of the mutual influence among the data, so that the alarm reasons can be conveniently attributed and association analyzed, and the faults can be conveniently repaired.
In step 403, a lifecycle of the alarm message is established based on the alarm message.
The specific implementation process and principle of the step 403 may refer to the detailed description of the foregoing embodiments, which is not repeated herein.
In step 404, configuration parameters of source anomaly data are obtained.
In the embodiment of the present disclosure, the configuration parameter of the abnormal data may refer to the name of the abnormal data. For example, the acquired source anomaly data is: "network interface success rate: x ", so that the network interface success rate can be determined as a configuration parameter of the source exception data.
In step 405, configuration parameters of new anomaly data detected during a life cycle are acquired.
In the embodiment of the present disclosure, if new abnormal data is detected again when the lifecycle corresponding to the source abnormal data is not over, the name of the new abnormal data may be extracted from the detected new abnormal data as a configuration parameter of the new abnormal data. For example, in a life cycle corresponding to the success rate of the network interface, new abnormal data is detected: "Domain name: y ", so that the configuration parameter of the new abnormal data can be determined as" domain name ".
In step 406, if it is determined that the source abnormal data is upstream abnormal data of the new abnormal data according to the preset configuration table, the configuration parameters of the source abnormal data and the configuration parameters of the new abnormal data, the new abnormal data is determined as associated abnormal data of the source abnormal data.
In the embodiment of the present disclosure, when configuring the upstream data of each data, the configured information may be stored in a preset configuration table, so as to determine whether the new abnormal data is related to the source abnormal data by querying the preset configuration table. Specifically, the configuration parameters of the upstream data corresponding to the configuration parameters of each data can be stored in the preset configuration table, so that after the configuration parameters of the source abnormal data and the configuration parameters of the new abnormal data are obtained, whether the configuration parameters of the source abnormal data are the upstream configuration parameters of the new abnormal data or not can be determined according to the preset configuration table; if yes, the source abnormal data can be determined to be upstream abnormal data of the new abnormal data; if the configuration parameter of the source abnormal data is determined not to be the upstream configuration parameter of the new abnormal data, it may be determined that the source abnormal data is not the upstream abnormal data of the new abnormal data, that is, the new abnormal data is not related to the source abnormal data, so that the new abnormal data may be determined to be the new source abnormal data, and an alarm message corresponding to the new source abnormal data may be sent, and a life cycle corresponding to the new source abnormal data may be established.
In the embodiment of the disclosure, if an upstream exception data exists in one exception data, the exception of the upstream exception data is likely to be caused by the exception data, that is, the exception data is associated with the corresponding upstream exception data. Thus, when the source abnormal data is determined to be upstream abnormal data of the new abnormal data, it can be determined that the source abnormal data is likely to be abnormal due to the new abnormal data, namely the source abnormal data and the new abnormal data can indicate the same fault, and therefore the new abnormal data can be determined to be associated abnormal data of the source abnormal data.
According to the embodiment of the disclosure, whether the abnormal data are associated with the source abnormal data or not is determined according to the preset configuration table, so that the efficiency of determining the associated abnormal data is improved, and the efficiency of monitoring the abnormal data is further improved.
In step 407, the source anomaly data and associated anomaly data are monitored.
When the source anomaly data is recovered, the alarm message is turned off and the lifecycle is ended, step 408.
The specific implementation and principles of the steps 407-408 may refer to the detailed description of the embodiments, which is not repeated here.
According to the alarm processing method for the abnormal data, the fluctuation range and the upstream data dimension of each data are preset, so that when the data value of the data is not located in the fluctuation range and related upstream abnormal data do not exist, the data are determined to be source abnormal data, an alarm message is sent, the life cycle is established, the upstream data dimension of each data is preset through a preset configuration table, and whether new abnormal data are related abnormal data of the source abnormal data or not can be determined according to the preset configuration table. Therefore, the associated abnormal data acquired in the life cycle corresponding to the source abnormal data is monitored only without sending alarm information, and the upstream data dimension corresponding to each data is configured so as to analyze the association between the data, thereby greatly reducing the alarm notification quantity, further improving the accuracy of the analysis of the cause of the alarm, and facilitating the repair of faults.
In one possible implementation form of the present disclosure, associated abnormal data related to source abnormal data may also be added to an abnormal data maintenance table to record changes of the associated abnormal data, so as to facilitate subsequent attribution, association, analysis, and so on of faults, and promote reliability of abnormal data monitoring.
Fig. 4 is a flowchart illustrating still another method of alarm processing of abnormal data, which is used in an electronic device, as shown in fig. 4, according to an exemplary embodiment, including the following steps.
In step 501, an alarm message of source anomaly data is acquired.
In step 502, a lifecycle of the alarm message is established based on the alarm message.
The specific implementation and principles of the above steps 501-502 may refer to the detailed description of the above embodiments, which are not repeated here.
In step 503, if associated anomaly data relating to the source anomaly data is detected during the life cycle, the associated anomaly data is added to the anomaly data maintenance table.
In the embodiment of the disclosure, after the life cycle of the alarm message is established, if new abnormal data is detected when the life cycle is not finished, whether the new abnormal data is related to the source abnormal data corresponding to the life cycle can be judged first, if so, the fault type indicated by the new abnormal data can be determined to be the same as or related to the fault type indicated by the source abnormal data, so that the new abnormal data can be determined to be related abnormal data. Since the association of the anomaly data with the source anomaly data may be caused by the same fault, the alarm message may be generated only once to reduce the number of alarm messages and not cause missing necessary alarm information. After determining the associated abnormal data related to the source abnormal data, an abnormal data maintenance table may be established, and the associated abnormal data may be added to the abnormal constant maintenance table to record real-time changes of the associated abnormal data, so as to facilitate subsequent attribution, association, analysis, etc. of the fault.
Furthermore, to save operation resources, the abnormal data maintenance table may be closed when the abnormal data maintenance table is empty. That is, in one possible implementation manner of the embodiment of the present disclosure, the method may further include:
if no abnormal data is associated in the abnormal data maintenance table and the abnormal data is not received in the second preset time, closing the abnormal data maintenance table.
In the embodiment of the disclosure, if no associated abnormal data exists in the abnormal data maintenance table, that is, the abnormal data maintenance table is empty and the abnormal data is not received for a long time, it can be determined that the abnormal data may not exist in the current time period, so that the abnormal data maintenance table can be closed to save operation resources; and when the abnormal data is received, reestablishing the abnormal data maintenance table.
As a possible implementation manner, the second preset time may be determined according to actual needs, so that when the abnormal data maintenance table is empty and the duration of not receiving the abnormal data reaches the second preset time, it is determined that the duration of not receiving the abnormal data is longer, so that the abnormal data maintenance table may be closed.
In step 504, each associated anomaly data in the source anomaly data and anomaly data maintenance table is monitored.
In the embodiment of the disclosure, after the associated abnormal data related to the source abnormal data is acquired, each associated abnormal data may be monitored to record the data values of the source abnormal data and the associated abnormal data in the life cycle.
As a possible implementation manner, the frequency of monitoring the source abnormal data and the associated abnormal data may be preset, that is, the data value of each associated abnormal data in the source abnormal data and the abnormal data maintenance table may be obtained at the preset frequency and recorded in the abnormal data maintenance table, so as to monitor the states of the source abnormal data and the associated abnormal data, such as the change trend of the source abnormal data and the associated abnormal data in the life cycle, and further, when the life cycle is not finished, follow-up the alarm message according to the states of the source abnormal data and the associated abnormal data, so that the alarm message may be processed in time.
In step 505, when the processing time corresponding to the associated abnormal data reaches the first preset time, a processing reminding message of the associated abnormal data is pushed.
The processing time corresponding to the associated abnormal data may refer to a time period for adding the associated abnormal data to the abnormal data maintenance table.
In the embodiment of the present disclosure, after monitoring each associated abnormal data in the abnormal data maintenance table, whether the associated abnormal data has recovered to normal may be further determined according to the data values of the associated abnormal data acquired at each time. If the time length of adding the associated abnormal data to the abnormal data maintenance table (namely the processing time corresponding to the associated abnormal data) has reached the first preset time, and the associated abnormal data is not recovered to be normal, a processing reminding message corresponding to the associated abnormal data can be sent to a client of the user so as to remind the user to process the alarm message in time, and omission of the user in processing the alarm message is avoided.
As a possible implementation manner, whether the associated abnormal data is recovered to be normal or not may be determined according to a preset monitoring recovery policy. For example, the preset monitoring recovery policy may be "the duration from the data to the recovery to the fluctuation range reaches the third preset time", so that when the processing time corresponding to the associated abnormal data reaches the first preset time, whether the duration from the data value of the associated abnormal data to the fluctuation range reaches the third preset time or not may be judged, if yes, it may be determined that the associated abnormal data is recovered normally; or, the preset monitoring recovery strategy may be "continuous N data values corresponding to data are recovered to the fluctuation range", so that when the processing time corresponding to the associated abnormal data reaches the first preset time, it may be determined whether the N continuous monitoring values of the associated abnormal data are recovered to the fluctuation range, and if yes, it may be determined that the associated abnormal data are recovered normally.
It should be noted that the preset monitoring recovery policy may include, but is not limited to, the above-listed cases. In actual use, the method and the device can be preset according to actual needs and specific service scenes, and the embodiment of the disclosure is not limited to the method and the device.
When the source anomaly data is recovered, the alarm message is turned off and the lifecycle is ended, step 506.
It should be noted that, when determining whether the source abnormal data is recovered, whether the source abnormal data is recovered may be determined according to the monitoring recovery policy described in step 505 for determining whether the associated abnormal data is recovered, which is not described herein.
The specific implementation and principles of step 506 may refer to the detailed description of the foregoing embodiments, which is not repeated herein.
According to the alarm processing method for the abnormal data, when the alarm message of the source abnormal data is acquired, a life cycle corresponding to the alarm message is established, when the associated abnormal data related to the source abnormal data is detected in the life cycle, the associated abnormal data is added into an abnormal data maintenance table, real-time changes of the associated abnormal data are recorded for analysis, alarm notification is not sent, and further when the associated abnormal data is not processed for a long time, a processing reminding message is sent to a user until the source data is recovered, and the life cycle is ended. Therefore, the associated abnormal data acquired in the life cycle corresponding to the source abnormal data are only recorded into the abnormal data maintenance table to be monitored, and the alarm message is not sent, so that the alarm notification quantity is greatly reduced, the accuracy of the analysis of the cause of the alarm is improved, and the user is reminded of timely processing the alarm message by timely following the state of the abnormal data, so that the alarm message processing omission is avoided.
FIG. 5 is a block diagram of an alarm processing device for exception data, according to an exemplary embodiment. Referring to fig. 5, the apparatus 60 includes an acquisition module 61, a setup module 62, a monitoring module 63, and a first shutdown module 64.
The acquisition module 61 is configured to perform a step of acquiring an alarm message of source abnormality data;
the establishing module 62 is configured to perform the step of establishing a life cycle of the alarm message from the alarm message;
the monitoring module 63 is configured to perform a step of monitoring the source abnormal data and the associated abnormal data when the associated abnormal data related to the source abnormal data is detected during the life cycle; and
the first shutdown module 64 is configured to perform the steps of shutting down the alarm message and ending the lifecycle when the source exception data is restored.
In actual use, the alarm processing device for abnormal data provided by the embodiment of the disclosure may be configured in any electronic device to execute the alarm processing method for abnormal data.
According to the alarm processing device for the abnormal data, when the alarm message of the source abnormal data is acquired, the life cycle corresponding to the alarm message is established, when the associated abnormal data related to the source abnormal data is detected in the life cycle, the associated abnormal data is recorded only so as to be convenient to analyze, an alarm notification is not sent, and the life cycle is ended until the source data is recovered. Therefore, the related abnormal data acquired in the life cycle corresponding to the source abnormal data is monitored only without sending an alarm message, so that the alarm notification quantity is greatly reduced, and the monitoring effect of the abnormal data is improved.
In one possible implementation form of the present disclosure, the monitoring module 63 includes:
an adding unit configured to perform a step of adding associated abnormal data to the abnormal data maintenance table;
a monitoring unit configured to perform a step of establishing monitoring for each associated abnormal data in the abnormal data maintenance table; and
and the pushing unit is configured to execute the step of pushing the processing reminding message of the associated abnormal data when the processing time corresponding to the associated abnormal data reaches the first preset time.
Further, in another possible implementation form of the present disclosure, the acquiring module 61 includes:
a receiving unit configured to perform a step of receiving the abnormal data; and
and a first determination unit configured to perform a step of determining the abnormal data as source abnormal data and transmitting a warning message when the abnormal data is not within the fluctuation range and there is no upstream abnormal data related to the abnormal data.
Further, in still another possible implementation form of the present disclosure, the source exception data is upstream exception data of the associated exception data.
Further, in still another possible implementation form of the present disclosure, the monitoring module 63 includes:
A first acquisition unit configured to perform a step of acquiring configuration parameters of source abnormality data;
a second acquisition unit configured to perform a step of acquiring configuration parameters of new abnormal data detected during a life cycle;
and a second determination unit configured to perform a step of determining the new abnormal data as associated abnormal data of the source abnormal data when determining that the source abnormal data is upstream abnormal data of the new abnormal data according to a preset configuration table, configuration parameters of the source abnormal data, and configuration parameters of the new abnormal data.
Further, in still another possible implementation form of the present disclosure, the alarm processing device 60 for abnormal data further includes:
and the second closing module is configured to execute the steps of closing the abnormal data maintenance table when no abnormal data is associated in the abnormal data maintenance table and the abnormal data is not received any more within a second preset time.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
According to the alarm processing device for the abnormal data, provided by the embodiment of the disclosure, the fluctuation range and the upstream data dimension of each data are preset, so that when the data value of the data is not located in the fluctuation range and related upstream abnormal data do not exist, the data are determined to be the source abnormal data, an alarm message is sent, the life cycle is established, and further the upstream data dimension of each data is preset through the preset configuration table, and therefore whether the new abnormal data are the related abnormal data of the source abnormal data or not can be determined according to the preset configuration table. Therefore, the associated abnormal data acquired in the life cycle corresponding to the source abnormal data is monitored only without sending alarm information, and the upstream data dimension corresponding to each data is configured so as to analyze the association between the data, thereby greatly reducing the alarm notification quantity, further improving the accuracy of the analysis of the cause of the alarm, and facilitating the repair of faults.
Fig. 6 is a block diagram illustrating an electronic device 700 for information querying, according to an example embodiment.
As shown in fig. 6, the electronic device 700 includes:
the memory 710 and the processor 720, the bus 730 connecting different components (including the memory 710 and the processor 720), the memory 710 stores a computer program, and when the processor 720 executes the program, the alarm processing method of abnormal data according to the embodiment of the present disclosure is implemented.
Bus 730 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include 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.
Electronic device 700 typically includes a variety of electronic device readable media. Such media can be any available media that is accessible by electronic device 700 and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 710 may also include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 740 and/or cache memory 750. Electronic device 700 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 760 may be used to read from or write to non-removable, non-volatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard disk drive"). Although not shown in fig. 6, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 730 through one or more data medium interfaces. Memory 710 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the various embodiments of the disclosure.
A program/utility 780 having a set (at least one) of program modules 770 may be stored in, for example, memory 710, such program modules 770 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 770 typically carry out the functions and/or methods of the embodiments described in this disclosure.
The electronic device 700 may also communicate with one or more external devices 790 (e.g., keyboard, pointing device, display 791, etc.), one or more devices that enable a user to interact with the electronic device 700, and/or any device (e.g., network card, modem, etc.) that enables the electronic device 700 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 792. Also, the electronic device 700 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 793. As shown, the network adapter 793 communicates with other modules of the electronic device 700 over the bus 730. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 700, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processor 720 executes various functional applications and data processing by running programs stored in the memory 710.
It should be noted that, the implementation process and the technical principle of the electronic device in this embodiment refer to the foregoing explanation of the method for processing the abnormal data in the embodiment of the disclosure, and are not repeated herein.
The electronic device provided by the embodiment of the disclosure may execute the alarm processing method of the abnormal data, by establishing a life cycle corresponding to an alarm message when the alarm message of the source abnormal data is acquired, and recording only the associated abnormal data for analysis when the associated abnormal data related to the source abnormal data is detected in the life cycle, without sending an alarm notification until the source data is recovered, and ending the life cycle. Therefore, the related abnormal data acquired in the life cycle corresponding to the source abnormal data is monitored only without sending an alarm message, so that the alarm notification quantity is greatly reduced, and the monitoring effect of the abnormal data is improved.
In order to implement the above-described embodiments, the present disclosure also proposes a storage medium.
Wherein the instructions in the storage medium, when executed by the processor of the electronic device, enable the electronic device to perform the alarm processing method of abnormal data as described above.
To achieve the above embodiments, the present disclosure also provides a computer program product which, when executed by a processor of an electronic device, enables the electronic device to perform the alarm processing method of abnormal data as described above.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (8)

1. An alarm processing method for abnormal data, comprising the following steps:
acquiring an alarm message of source abnormal data;
Establishing the life cycle of the alarm message according to the alarm message;
monitoring the source anomaly data and the associated anomaly data if associated anomaly data associated with the source anomaly data is detected during the lifecycle; and
when the source abnormal data is recovered, closing the alarm message and ending the life cycle;
the alarm message for acquiring the source abnormal data comprises the following steps:
receiving abnormal data, wherein if the data value of certain data acquired at the current moment is not in the fluctuation range, the data is determined to be the abnormal data;
after the abnormal data is obtained, if no unfinished life cycle exists at the current moment, determining the abnormal data as the source abnormal data, generating an alarm message of the source abnormal data and sending the alarm message to a client; if the life cycle which is not ended exists at the current moment, judging whether the life cycle which is at the current moment contains upstream abnormal data related to the abnormal data, if not, determining the abnormal data as the source abnormal data, and sending a warning message;
the source abnormal data is upstream abnormal data of the associated abnormal data, wherein the associated abnormal data is abnormal to cause the source abnormal data to generate abnormality;
The monitoring of the source anomaly data and the associated anomaly data includes:
adding the associated exception data to an exception data maintenance table;
monitoring each associated abnormal data in the abnormal data maintenance table; and
and when the processing time corresponding to the associated abnormal data reaches a first preset time, pushing a processing reminding message of the associated abnormal data.
2. The method of alert processing of anomaly data of claim 1, wherein the detecting associated anomaly data related to the source anomaly data during the lifecycle comprises:
acquiring configuration parameters of the source abnormal data;
acquiring configuration parameters of new abnormal data detected in the life cycle;
and if the source abnormal data is determined to be upstream abnormal data of the new abnormal data according to a preset configuration table, the configuration parameters of the source abnormal data and the configuration parameters of the new abnormal data, determining the new abnormal data to be associated abnormal data of the source abnormal data.
3. The method for alarm processing of abnormal data according to any one of claim 1, further comprising:
If no abnormal data is associated in the abnormal data maintenance table and the abnormal data is not received within a second preset time, closing the abnormal data maintenance table.
4. An alarm processing apparatus for abnormal data, comprising:
an acquisition module configured to perform the step of acquiring an alarm message of source abnormality data;
a setup module configured to perform the step of establishing a lifecycle of the alarm message from the alarm message;
a monitoring module configured to perform a step of monitoring the source abnormal data and the associated abnormal data when the associated abnormal data related to the source abnormal data is detected during the life cycle; and
a first shutdown module configured to perform the steps of shutting down the alarm message and ending the lifecycle when the source exception data is restored;
the acquisition module is used for:
receiving abnormal data, wherein if the data value of certain data acquired at the current moment is not in the fluctuation range, the data is determined to be the abnormal data;
after the abnormal data is obtained, if no unfinished life cycle exists at the current moment, determining the abnormal data as the source abnormal data, generating an alarm message of the source abnormal data and sending the alarm message to a client; if the life cycle which is not ended exists at the current moment, judging whether the life cycle which is at the current moment contains upstream abnormal data related to the abnormal data, if not, determining the abnormal data as the source abnormal data, and sending a warning message;
The source abnormal data is upstream abnormal data of the associated abnormal data, wherein the associated abnormal data is abnormal to cause the source abnormal data to generate abnormality;
the monitoring module comprises:
an adding unit configured to perform a step of adding the associated abnormal data to an abnormal data maintenance table;
a monitoring unit configured to perform a step of establishing monitoring for each associated abnormal data in the abnormal data maintenance table; and
and the pushing unit is configured to perform the step of pushing the processing reminding message of the associated abnormal data when the processing time corresponding to the associated abnormal data reaches a first preset time.
5. The apparatus for alarm processing of abnormal data according to claim 4, wherein said monitoring module comprises:
a first acquisition unit configured to perform a step of acquiring configuration parameters of the source abnormality data;
a second acquisition unit configured to perform a step of acquiring configuration parameters of new abnormal data detected during the life cycle;
a second determining unit configured to perform a step of determining the new abnormal data as associated abnormal data of the source abnormal data when determining that the source abnormal data is upstream abnormal data of the new abnormal data according to a preset configuration table, a configuration parameter of the source abnormal data, and a configuration parameter of the new abnormal data.
6. The apparatus for alarm processing of abnormal data according to any one of claims 4 to 5, further comprising:
and the second closing module is configured to execute the steps of closing the abnormal data maintenance table when no abnormal data is associated in the abnormal data maintenance table and the abnormal data is not received any more within a second preset time.
7. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the alarm processing method of abnormal data according to any one of claims 1-3.
8. A storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the alarm processing method of abnormal data according to any one of claims 1-3.
CN202010923047.0A 2020-09-04 2020-09-04 Alarm processing method and device for abnormal data, electronic equipment and storage medium Active CN112181787B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010923047.0A CN112181787B (en) 2020-09-04 2020-09-04 Alarm processing method and device for abnormal data, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010923047.0A CN112181787B (en) 2020-09-04 2020-09-04 Alarm processing method and device for abnormal data, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN112181787A CN112181787A (en) 2021-01-05
CN112181787B true CN112181787B (en) 2023-12-19

Family

ID=73924138

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010923047.0A Active CN112181787B (en) 2020-09-04 2020-09-04 Alarm processing method and device for abnormal data, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112181787B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022638A (en) * 2007-03-12 2007-08-22 华为技术有限公司 Alarm reporting method and alarm device
CN101106478A (en) * 2007-08-06 2008-01-16 华为技术有限公司 Alert processing method and its device
CN101247254A (en) * 2007-02-16 2008-08-20 大唐移动通信设备有限公司 Method and device for suppression alarm windstorm
CN101355605A (en) * 2007-07-24 2009-01-28 ***通信集团公司 Method for processing network management alarm and alarm processor
CN104009854A (en) * 2013-02-21 2014-08-27 中兴通讯股份有限公司 Alarm processing method and apparatus, alarm associated information setting method
CN107690774A (en) * 2016-12-28 2018-02-13 深圳中兴力维技术有限公司 Alert processing method and device
CN108156037A (en) * 2017-12-29 2018-06-12 ***通信集团江苏有限公司 Alarm correlation analysis method, device, equipment and medium
CN111563524A (en) * 2020-03-18 2020-08-21 宁波送变电建设有限公司永耀科技分公司 Multi-station fusion system operation situation abnormity monitoring and alarm combining method

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247254A (en) * 2007-02-16 2008-08-20 大唐移动通信设备有限公司 Method and device for suppression alarm windstorm
CN101022638A (en) * 2007-03-12 2007-08-22 华为技术有限公司 Alarm reporting method and alarm device
CN101355605A (en) * 2007-07-24 2009-01-28 ***通信集团公司 Method for processing network management alarm and alarm processor
CN101106478A (en) * 2007-08-06 2008-01-16 华为技术有限公司 Alert processing method and its device
CN104009854A (en) * 2013-02-21 2014-08-27 中兴通讯股份有限公司 Alarm processing method and apparatus, alarm associated information setting method
CN107690774A (en) * 2016-12-28 2018-02-13 深圳中兴力维技术有限公司 Alert processing method and device
CN108156037A (en) * 2017-12-29 2018-06-12 ***通信集团江苏有限公司 Alarm correlation analysis method, device, equipment and medium
CN111563524A (en) * 2020-03-18 2020-08-21 宁波送变电建设有限公司永耀科技分公司 Multi-station fusion system operation situation abnormity monitoring and alarm combining method

Also Published As

Publication number Publication date
CN112181787A (en) 2021-01-05

Similar Documents

Publication Publication Date Title
CN104268055B (en) The monitoring method and device of a kind of program exception
CN107800783B (en) Method and device for remotely monitoring server
CN110727560A (en) Cloud service alarm method and device
CN114978883B (en) Network wakeup management method and device, electronic equipment and storage medium
CN110262955B (en) Application performance monitoring tool based on pinpoint
CN112181787B (en) Alarm processing method and device for abnormal data, electronic equipment and storage medium
CN110727563A (en) Cloud service alarm method and device for preset customer
TWI546746B (en) SOA service quality real - time analysis and alarm system and its method
CN111062503B (en) Power grid monitoring alarm processing method, system, terminal and storage medium
CN116860552A (en) Application program operation monitoring method and device, electronic equipment and storage medium
CN113220379B (en) Task processing method and device, electronic equipment and readable storage medium
CN113392079B (en) Distributed storage cluster log storage optimization method, system and terminal
CN115174350A (en) Operation and maintenance warning method, device, equipment and medium
CN104346233A (en) Fault recovery method and device for computer system
CN114398222A (en) Method for declaratively visually configuring Prometheus monitoring alarm
CN112069027A (en) Interface data processing method and device, electronic equipment and storage medium
CN113835916A (en) Ambari big data platform-based alarm method, system and equipment
CN113254313A (en) Monitoring index abnormality detection method and device, electronic equipment and storage medium
CN112162897A (en) Public intelligent equipment management method and system
CN110362464B (en) Software analysis method and equipment
CN107797915B (en) Fault repairing method, device and system
CN111756778A (en) Server disk cleaning script pushing method and device and storage medium
CN114385387B (en) Access information generation method and device and computer equipment
CN116074388B (en) Flow forwarding method and system based on log queue
KR20010019092A (en) Method for managing tdx exchange message in switching system

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
GR01 Patent grant
GR01 Patent grant