CN107423194B - Front-end abnormal alarm processing method, device and system - Google Patents
Front-end abnormal alarm processing method, device and system Download PDFInfo
- Publication number
- CN107423194B CN107423194B CN201710523342.5A CN201710523342A CN107423194B CN 107423194 B CN107423194 B CN 107423194B CN 201710523342 A CN201710523342 A CN 201710523342A CN 107423194 B CN107423194 B CN 107423194B
- Authority
- CN
- China
- Prior art keywords
- log
- alarm
- abnormal
- maintenance system
- server
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the specification provides a front-end abnormal alarm processing method, device and system. The method comprises the following steps: the front end captures page abnormity and sends an abnormal log corresponding to the page abnormity to a log maintenance system; the log maintenance system receives the abnormal log and writes the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed to the log maintenance system belongs; the alarm server acquires the log file at regular time and judges whether the set alarm condition is met or not according to the log file; and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
Description
Technical Field
The embodiment of the specification belongs to the technical field of computer data processing, and particularly relates to a front-end abnormal alarm processing method, device and system.
Background
The front-end abnormity warning technology is a mechanism for capturing and reporting information of current page code abnormal operation at a user browser end, so that page maintenance personnel can find abnormity in time and solve abnormity quickly.
The common front-end alarm technology in the existing scheme is mainly to bury an anomaly as a point in a public table by a point burying technology, and use a server deployed in a background to specially and regularly salvage all buried points to obtain data of the buried points. And then data cleaning is carried out on the buried point data, abnormal points with specific identifications are screened out, and further alarm processing is carried out. The current front-end alarm mechanism needs a background to cooperate with a deployment server to perform data acquisition and clear codes of abnormal work of a target system, and front-end operators generally need to learn a buried point deployment service and a learning API to perform data scanning, cleaning and other work. Therefore, there is a need in the art for a front-end exception alert handling method with lower labor cost.
Disclosure of Invention
Embodiments of the present disclosure provide a front-end abnormal alarm processing method, device, and system, which provide a low-cost and lightweight manner for collecting and alarming data front-end abnormal alarm data, and can implement operations such as data scanning, cleaning, and alarm that can be completed in an accessed background alarm service, thereby reducing labor cost.
The method, the device and the system for processing the front-end abnormal alarm provided by the embodiment of the specification are realized in the following modes:
a front-end abnormal alarm processing method comprises the following steps:
the front end captures page abnormity and sends an abnormal log corresponding to the page abnormity to a log maintenance system;
the log maintenance system receives the abnormal log and writes the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed to the log maintenance system belongs;
the alarm server acquires the log file at regular time and judges whether the set alarm condition is met or not according to the log file;
and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
A front-end abnormal alarm processing method comprises the following steps:
receiving an abnormal log sent by a front end;
writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed into the log maintenance system belongs;
and sending the log file to the alarm server based on the received log acquisition instruction of the alarm server so that the alarm server sends corresponding alarm information when determining that an alarm condition is reached based on the log file.
A front-end abnormal alarm processing method comprises the following steps:
acquiring a log file from a log maintenance system at regular time, wherein the log file comprises abnormal logs based on a received front end and a corresponding system identifier, and the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs;
judging whether a set alarm condition is reached or not according to the log file;
and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
A front-end abnormal alarm processing method comprises the following steps:
receiving an abnormal log sent by a front end, and writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which the front end accessed into the log maintenance system belongs;
judging whether set alarm conditions are met or not according to the log file;
and if so, sending out alarm information corresponding to the system to which the front end belongs.
A front-end abnormal alarm processing system comprises a log maintenance server and a background alarm server,
the log maintenance server is used for receiving an abnormal log sent by the front end; the log file is also used for writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed into the log maintenance system belongs;
the alarm server is used for acquiring log files from the log maintenance server at regular time; the log file is also used for judging whether a set alarm condition is met or not according to the log file; and sending out alarm information corresponding to the system to which the front end belongs when the alarm condition is met.
A front-end exception alert handling apparatus, the apparatus comprising:
the log receiving module is used for receiving the abnormal log sent by the front end;
the log recording module is used for writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed to the log maintenance system belongs;
and the log sending module is used for sending the log file to the alarm server based on the received log obtaining instruction of the alarm server so that the alarm server sends corresponding alarm information when determining that the alarm condition is reached based on the log file.
A front-end exception alert handling apparatus, the apparatus comprising:
the log acquisition module is used for acquiring a log file from a log maintenance system at regular time, wherein the log file comprises abnormal logs based on a received front end and a corresponding system identifier, and the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs;
the judging module is used for judging whether a set alarm condition is reached or not according to the log file;
and the alarm module is used for sending alarm information corresponding to the system to which the front end belongs by the alarm server if the alarm information meets the requirement.
A front-end exception alert handling apparatus, the apparatus comprising:
the log recording module is used for receiving an abnormal log sent by a front end and writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which the front end accessed into the log maintenance system belongs;
the judging module is used for judging whether the set alarm condition is met or not according to the log file;
and the alarm module is used for sending out alarm information corresponding to the system to which the front end belongs when the alarm condition is met.
A front-end exception alert handling apparatus comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor performing:
receiving an abnormal log sent by a front end;
writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed into the log maintenance system belongs;
and sending the log file to the alarm server based on the received log acquisition instruction of the alarm server so that the alarm server sends corresponding alarm information when determining that an alarm condition is reached based on the log file.
A front-end exception alert handling apparatus comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor performing:
acquiring a log file from a log maintenance system at regular time, wherein the log file comprises abnormal logs based on a received front end and a corresponding system identifier, and the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs;
judging whether a set alarm condition is reached or not according to the log file;
and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
A front-end exception alert handling apparatus comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor performing:
receiving an abnormal log sent by a front end, and writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which the front end accessed into the log maintenance system belongs;
judging whether set alarm conditions are met or not according to the log file;
and if so, sending out alarm information corresponding to the system to which the front end belongs.
According to the front-end abnormal alarm processing method, the front-end abnormal alarm processing device and the front-end abnormal alarm processing system provided by one or more embodiments of the specification, the data volume magnitude of the processed abnormal log is far smaller than that of the data volume magnitude processed by the buried point, so that the complexity of data scanning and cleaning automatically performed by the server is greatly reduced, meanwhile, operations such as data scanning, cleaning and alarming can be completed in the accessed background alarm service, the workload of operators participating in the front-end abnormal alarm can be greatly reduced, and the labor cost is reduced.
Drawings
In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in one or more embodiments of the present specification, and other drawings can be obtained by those skilled in the art without inventive exercise.
FIG. 1 is a flow chart illustrating an embodiment of a front-end exception alarm handling method described in this specification;
FIG. 2 is a schematic diagram of a process comparing one embodiment of the method provided herein with conventional practice;
FIG. 3 is a process diagram in the context of another embodiment of the method provided by the present specification;
fig. 4 is a schematic flowchart of an embodiment of a front-end exception warning processing method provided in this specification;
fig. 5 is a schematic flowchart of an embodiment of a front-end exception warning processing method provided in this specification;
FIG. 6 is a flow chart illustrating another embodiment of a front-end exception alert handling method provided in the present specification;
fig. 7 is a schematic block diagram of an embodiment of a front-end exception warning processing apparatus provided in this specification;
fig. 8 is a schematic block diagram of an embodiment of a front-end exception warning processing apparatus provided in this specification;
fig. 9 is a schematic block diagram of an embodiment of a front-end exception warning processing apparatus according to the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of one or more embodiments of the present specification, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from the embodiments of one or more embodiments of the present disclosure without making any creative effort shall fall within the protection scope of the embodiments of the present disclosure.
Fig. 1 is a schematic flowchart of an embodiment of a front-end abnormal alarm processing method described in this specification. Although the present specification provides the method steps or apparatus structures as shown in the following examples or figures, more or less steps or modules may be included in the method or apparatus structures based on conventional or non-inventive efforts. In the case of steps or structures where no causal relationship is logically necessary, the order of execution of the steps or the modular structure of the apparatus is not limited to the order of execution or the modular structure shown in one or more of the embodiments or figures of this specification. When the described method or module structure is applied to a device, a server or an end product in practice, the method or module structure according to the embodiment or the figures may be executed sequentially or in parallel (for example, in a parallel processor or multi-thread processing environment, or even in an implementation environment including distributed processing and server clustering).
Specifically, an embodiment of a front-end abnormal alarm processing method provided in this specification is shown in fig. 1, where the method may include:
s2: the front end captures page abnormity and sends an abnormal log corresponding to the page abnormity to a log maintenance system;
s4: the log maintenance system receives the abnormal log and writes the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed to the log maintenance system belongs;
s6: the alarm server acquires the log file at regular time and judges whether the set alarm condition is met or not according to the log file;
s8: and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
The front end in this embodiment generally refers to an application page running on the client side of the user, such as a page applied in an intelligent terminal, a page of a browser, and the like. For a website, it generally means that the foreground part of the website mainly includes the presentation layer and the structural layer of the website. In general, the development design, test, and the like of the front end are realized by the foreground code of the website, including the design languages HTML, CSS, JavaScript/ajax, and the like.
FIG. 2 is a schematic diagram comparing the processing of one embodiment of the method provided in the present specification with conventional practice. As shown in fig. 2, the conventional method requires a lot of manpower, including point burying, data pulling, data cleaning, processing summary, alarm, etc. The improved scheme of one or more embodiments of the present specification may only need 4 steps, wherein 1, 2, and 3 steps may be configured by an operator in a background monitoring service (background alarm server). The front-end page can capture the exception, and an exception log can be generated after exception information is obtained. The front end can then send the exception log to the background, which records the exception log. The rest of the work can be automatically completed by the background alarm server. As can be seen from fig. 2, the method provided by this embodiment greatly simplifies the flow steps of the front-end alarm mechanism, and operations such as data scanning, cleaning, and alarming can be completed in the accessed background alarm service, so that the workload of the operator participating in the front-end abnormal alarm can be greatly reduced, and the labor cost can be reduced.
The background can be a processing device which is separately arranged and used for recording the abnormal log, such as an abnormal log recording server. In other embodiments, the alarm notification device may also be an abnormal logging device disposed on the background alarm server.
Fig. 3 is a schematic diagram of a processing procedure in the context of another embodiment of the method provided in this specification. The specific processing procedure of the front-end abnormal alarm mechanism implemented in this embodiment may include:
an intermediate system of a log maintenance system is established, the system can be a server, can also be a distributed system or a server cluster, can receive an abnormal log sent by a front end by using a JSONP technology, and can maintain the abnormal log of the front end. The background alarm server can periodically fish the log of the intermediate system. This simplifies the system handling of front-end exception alarms. The front end needs to do work mainly by configuring abnormal alarm conditions in advance, capturing the abnormality and then sending a JSONP request according to the format convention of a journal transfer maintenance system. At this time, the internal system of the background alarm server does not need to be changed for invading the original system. The front-end page can capture the exception, and an exception log can be generated after exception information is obtained. The front end can then send the exception log to a set log maintenance system, which records the log in the background. The background server periodically fetches the log folder from the log maintenance system, and judges whether to send out an alarm or not based on the log file and the set alarm condition.
As shown in fig. 3, the operator may save the alarm condition of the access system in the log maintenance system in advance, and write the alarm condition into the log monitoring service. A log file is then maintained, which may specifically include writing an exception log and a system name to the log file each time the exception log is received. For security reasons, the log maintenance system may generate a string of identification codes from the system name as an identification of the access to the alarm service (referred to herein as a system identifier) when configuring the alarm condition. If the error information contained in the front-end abnormal log is received, but the system identifier identification code of the abnormal log is invalid, the abnormal log can be represented as that the abnormal log is not a log required to be maintained by the log maintenance system, and the abnormal log can not be recorded in a log file, and then the abnormal log is discarded at the moment. Specifically, the abnormal logs generated by the front end under which systems need to be maintained and other related configuration information about alarm triggering, statistics, recording modes and the like can be set through the alarm configuration information. The configuration information can be synchronized to the background alarm server, so that the background alarm server updates alarm conditions, the latest alarm strategy is timely validated, and compared with the conventional method of compiling page codes to adjust parameters or modify codes to be redeployed and the like, the method can greatly improve the convenience of alarm information configuration, modification and maintenance, thereby further improving the timeliness and the processing efficiency of alarms. Therefore, in another embodiment of the method, the method may further include:
s10: and providing alarm configuration information, wherein the alarm configuration information is used for synchronizing to the alarm server so as to update the alarm condition in the alarm server.
The following describes the implementation of the mechanism in detail by taking a log analysis product system of a certain front-end product application APP as an example. The log monitoring and alarm related information may first need to be configured, and the following table 1 is a schematic table of alarm configuration information in this embodiment:
table 1 log monitoring and alarm configuration information table
The front end can capture the exception by using window. The log maintenance system records the data into the log when receiving the front-end request. The format of the recorded exception log may be as follows:
in other embodiments, the alarm condition for triggering the background alarm server to alarm may be set according to the configuration right of the used alarm server. For example, an alarm may be issued when an abnormal log meeting a certain condition exceeds a set threshold, or an alarm may be issued when a serious abnormality is found. In the method provided in one or more embodiments of the present specification, the alarm condition may include at least one of:
s602: within the set recording time, the number of the abnormal logs reaching the alarm level exceeds a preset alarm threshold;
s604: an exception log of priority alarm levels is detected.
Compared with the front-end abnormal alarm mechanism in a point burying mode in the prior art, the implementation scheme provided by one or more embodiments of the specification can monitor which front-end abnormal alarms through alarm information configuration without specially deploying tasks for scanning the abnormality. The mechanism in the prior art needs to scan a large amount of data, and the useful data proportion is extremely small, but the implementation scheme provided by one or more embodiments of the specification can only need to scan a specific log, so that the alarm aging difference caused by different orders of magnitude is greatly reduced. In addition, if the mechanism in the prior art needs to change, such as an alarm threshold value, a notification list and the like, either the mechanism writes a page to call parameters by itself or changes codes to redeploy, and the operation and interaction are very complicated. One or more embodiments of the present disclosure may only need to modify the corresponding configuration in the intermediate log maintenance system, and the implementation may take effect in real time, which is simpler and more efficient.
The above-mentioned front end, log maintenance system, and the multiple test terminal of the background alarm server, which are accessed to the front end abnormal alarm service, interactively describe implementation manners of one or more embodiments of the present specification. For single-sided server processing, one or more embodiments of the present specification provide a front-end exception alert processing method that may be used in an intermediate system, such as the log maintenance system described above. Fig. 4 is a schematic flowchart of an embodiment of a front-end abnormal alarm processing method provided in this specification, and specifically as shown in fig. 4, the method may include:
s20: receiving an abnormal log sent by a front end;
s22: writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed into the log maintenance system belongs;
s24: and sending the log file to the alarm server based on the received log acquisition instruction of the alarm server so that the alarm server sends corresponding alarm information when determining that an alarm condition is reached based on the log file.
As can be seen from the foregoing description of the multi-side interactive embodiment, for an intermediate system like a log maintenance system, the method may further include:
s26: and providing alarm configuration information, wherein the alarm configuration information is used for synchronizing to the alarm server so as to update the alarm condition in the alarm server.
Similarly, the alarm condition may also be set to include at least one of the following:
s242: within the set recording time, the number of the abnormal logs reaching the alarm level exceeds a preset alarm threshold;
s244: an exception log of priority alarm levels is detected.
Similarly, for single-side server processing, one or more embodiments of the present specification provide a front-end exception alert processing method that may be used, for example, on the side of the background alert server described above. Fig. 5 is a schematic flowchart of an embodiment of a front-end abnormal alarm processing method provided in one or more embodiments of the present specification, and specifically as shown in fig. 5, the method may include:
s30: acquiring a log file from a log maintenance system at regular time, wherein the log file comprises abnormal logs based on a received front end and a corresponding system identifier, and the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs;
s32: judging whether a set alarm condition is reached or not according to the log file;
s34: and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
Correspondingly, the method may further include:
s36: providing alarm configuration information, wherein the alarm configuration information comprises at least one alarm condition for triggering an alarm, and the alarm condition comprises:
within the set recording time, the number of the abnormal logs reaching the alarm level exceeds a preset alarm threshold;
an exception log of priority alarm levels is detected.
In another embodiment of the method, after sending the warning message, the method may further include:
s38: and pushing the notification message which sends the alarm information to a preset alarm receiver.
In a specific implementation scenario, the log maintenance system may only need to receive log data and store the log data. Data scanning, cleaning, alarming and other operations can be completed in the existing background alarm service. Greatly reduces the labor cost and improves the timeliness of alarming.
The above embodiment describes that the exception log sent by the front end can be recorded by the intermediate system, and then regularly retrieved by the background alarm server. In another or more embodiments of the method provided in this specification, the abnormal log generated by the front end may be directly sent to the background alarm server, and the background alarm server directly records and stores the abnormal log, and then, according to the alarm configuration information, by automatically monitoring and screening the abnormal log, automatic data processing and alarm sending are implemented. Specifically, as shown in fig. 6, fig. 6 is a schematic flowchart of another embodiment of a front-end abnormal alarm processing method provided in this specification, where one or more embodiments of the front-end abnormal alarm processing method provided in this specification may include:
s40: receiving an abnormal log sent by a front end, and writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which the front end accessed into the log maintenance system belongs;
s42: judging whether set alarm conditions are met or not according to the log file;
s44: and if so, sending out alarm information corresponding to the system to which the front end belongs.
One or more embodiments of the present disclosure provide a front-end abnormal alarm processing method, which may collect and count front-end abnormalities by using a mature background alarm mechanism, and perform an alarm under a real-time or quasi-real-time requirement. One or more embodiments of the present disclosure may use a log system with a mature background, and may be implemented through a simple and fast alarm configuration through an existing operating interface equipped with a UI, so as to save hardware costs such as deploying a dedicated site-embedding server. The magnitude of the abnormal log processed in one or more embodiments of the present specification is far smaller than the magnitude of the data volume of the buried point, so the complexity of data scanning and cleaning automatically performed by the server is also greatly reduced, and the real-time performance or quasi-real-time performance of the front-end alarm is greatly improved in one or more embodiments of the present specification.
Based on the front-end abnormal alarm processing method, one or more embodiments of the present specification further provide a front-end abnormal alarm processing apparatus. The apparatus may include a system (including a distributed system), software (applications), modules, components, servers, clients, quantum computers, etc. that use the methods described in one or more embodiments of the present disclosure, in conjunction with any necessary apparatus to implement the hardware. Based on the same innovative conception, one or more embodiments of the present specification provide apparatuses as described in the following embodiments. Since the implementation scheme of the apparatus for solving the problem is similar to that of the method, reference may be made to the implementation of the foregoing method for the specific apparatus in one or more embodiments of the present disclosure, and repeated details are not described herein. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated. Specifically, fig. 7 is a schematic block structure diagram of an embodiment of a front-end abnormal alarm processing apparatus provided in this specification, and as shown in fig. 7, the apparatus may include:
the log receiving module 101 may be configured to receive an exception log sent by a front end;
a log recording module 102, configured to write the exception log and a corresponding system identifier into a log file, where the system identifier is generated based on a system name of a system to which a front end accessing the log maintenance system belongs;
the log sending module 103 may be configured to send the log file to the alarm server based on a received log obtaining instruction of the alarm server, so that the alarm server sends corresponding alarm information when determining that an alarm condition is reached based on the log file.
The specific implementation of the apparatus may be the log maintenance system described in the above method embodiment, and may be a single log maintenance server, or a server cluster and other devices.
One or more embodiments of the present specification further provide another front-end exception alert processing apparatus, which may be used in the background alert server in the above-described method embodiments, for example, and which may be coupled to/embedded in an existing background alert server. Specifically, as shown in fig. 8, a schematic block structure diagram of an embodiment of a front-end abnormal alarm processing apparatus provided in this specification may include:
the log obtaining module 201 may be configured to obtain a log file from a log maintenance system at regular time, where the log file includes an exception log generated based on a received front end and a corresponding system identifier, and the system identifier includes a system name generated based on a system to which the front end accessing the log maintenance system belongs;
the judging module 202 may be configured to judge whether a set alarm condition is reached according to the log file;
the alarm module 203 may send out alarm information corresponding to the system to which the front end belongs when the alarm condition is satisfied.
Of course, as described in the foregoing method, the front-end abnormal log may also be directly sent to the processing device of the background alarm server, and the background directly records and periodically performs the fishing process. Fig. 9 is a schematic block diagram of an embodiment of a front-end exception warning processing apparatus provided in this specification. Therefore, in another embodiment of a front-end abnormal alarm processing apparatus provided in one or more embodiments of the present specification, the method may include:
the log recording module 301 may be configured to receive an exception log sent by a front end, and write the exception log and a corresponding system identifier into a log file, where the system identifier is generated based on a system name of a system to which the front end accessing the log maintenance system belongs;
the judging module 302 may be configured to judge whether a set alarm condition is met according to the log file;
the alarm module 303 may be configured to send alarm information corresponding to a system to which the front end belongs when the alarm condition is satisfied.
The front-end exception alarm processing method provided in one or more embodiments of the present specification may be implemented in a computer by a processor executing corresponding program instructions, for example, implemented in a PC using a c + + language of a windows operating system, or implemented in other application design languages such as Linux, android, and iOS systems, and implemented in processing logic based on a quantum computer. Specifically, one or more embodiments of the present specification provide a front-end exception alert processing apparatus, which may include a processor and a memory for storing processor-executable instructions, where the processor executes the instructions to implement:
receiving an abnormal log sent by a front end;
writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed into the log maintenance system belongs;
and sending the log file to the alarm server based on the received log acquisition instruction of the alarm server so that the alarm server sends corresponding alarm information when determining that an alarm condition is reached based on the log file.
One or more embodiments of the present specification provide a front-end exception alert processing apparatus, which may include a processor and a memory for storing processor-executable instructions, where the processor executes the instructions to implement:
acquiring a log file from a log maintenance system at regular time, wherein the log file comprises abnormal logs based on a received front end and a corresponding system identifier, and the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs;
judging whether a set alarm condition is reached or not according to the log file;
and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
One or more embodiments of the present specification provide a front-end exception alert processing apparatus, which may include a processor and a memory for storing processor-executable instructions, where the processor executes the instructions to implement:
receiving an abnormal log sent by a front end, and writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which the front end accessed into the log maintenance system belongs;
judging whether set alarm conditions are met or not according to the log file;
and if so, sending out alarm information corresponding to the system to which the front end belongs.
It should be noted that the apparatus described above according to one or more embodiments of the present disclosure may also include other embodiments according to the description of the related method embodiments. The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.
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.
In one or more embodiments of the present disclosure, a straight front-end exception alarm processing apparatus isolates communication requests, data storage, data reading and writing, and the like of different blockchain networks by using a network identifier of a blockchain network, so that multiple network nodes in a multiple blockchain network can simultaneously join different blockchain networks, thereby implementing a data processing capability of simultaneously processing multiple blockchain networks. By using one or more embodiments of the present specification, the complexity of the system in the operation and maintenance of multiple network nodes can be effectively reduced, the complexity difficulty of the operation and maintenance of the service system participating in the whole network in the nodes and the system interaction can be reduced, and the data processing capability, the system stability and the reliability of the multiple block chain network can be improved.
The device or the method can be used in front-end abnormity alarm processing systems of a plurality of service systems, each service system can comprise a plurality of front ends, each front end can send the generated abnormity log to the abnormity alarm processing system when abnormity occurs, and the front-end error information can be simply, conveniently, lightweight and low-cost acquired in real time or quasi-real time. In particular, one or more embodiments of the present disclosure provide a front-end abnormal alarm processing system, which may include a log maintenance server, a background alarm server,
the log maintenance server can be used for receiving an abnormal log sent by the front end; the log file is also used for writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed into the log maintenance system belongs;
the alarm server can be used for acquiring log files from the log maintenance server at regular time; the log file is also used for judging whether a set alarm condition is met or not according to the log file; and sending out alarm information corresponding to the system to which the front end belongs when the alarm condition is met.
It should be noted that the above-mentioned device or system may also include other implementation manners according to the description of the method embodiment, and specific implementation manners may refer to the description of the method embodiment, which is not described in detail herein.
One or more embodiments of the present disclosure provide a method, an apparatus, and a system for processing a front-end abnormal alarm, which collect and count front-end abnormal alarms by using a mature background alarm mechanism, and perform an alarm under a real-time or quasi-real-time requirement. One or more embodiments of the present disclosure may use a log system with a mature background, and may be implemented through a simple and fast alarm configuration through an existing operating interface equipped with a UI, so as to save hardware costs such as deploying a dedicated site-embedding server. The magnitude of the abnormal log processed in one or more embodiments of the present specification is far smaller than the magnitude of the data volume of the buried point, so the complexity of data scanning and cleaning automatically performed by the server is also greatly reduced, and the real-time performance or quasi-real-time performance of the front-end alarm is greatly improved in one or more embodiments of the present specification.
Although the description of data setting, acquisition, interaction, calculation, judgment, etc., such as logging manner, alarm configuration data field, timed retrieval of logs, alarm information notification, etc., are mentioned in the context of one or more embodiments of the present description, one or more embodiments of the present description are not limited to compliance with industry communication standards, standard blockchain data storage, computer processing and storage rules, or the description of one or more embodiments of the present description. Certain industry standards, or implementations modified slightly from those described using custom modes or examples, may also achieve the same, equivalent, or similar, or other, contemplated implementations of the above-described examples. The embodiments using these modified or transformed data acquisition, storage, judgment, processing, etc. may still fall within the scope of the alternative embodiments of the present description.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Although one or more embodiments of the present description provide method operational steps as described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive approaches. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more embodiments of the present specification, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a plurality of sub-modules or a combination of sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, embodiments of one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description of the specification, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
The above description is merely exemplary of one or more embodiments of the present disclosure and is not intended to limit the scope of one or more embodiments of the present disclosure. Various modifications and alterations to one or more embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of the claims of the present specification.
Claims (14)
1. A front-end abnormal alarm processing method comprises the following steps:
the front end captures page abnormity and sends an abnormal log corresponding to the page abnormity to a log maintenance system;
the log maintenance system receives the abnormal log and writes the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which a front end accessed to the log maintenance system belongs; providing alarm configuration information, wherein the alarm configuration information is used for synchronizing to an alarm server so as to update an alarm condition in the alarm server; when an alarm condition is configured, an identification code generated according to a system name is used as a system identifier for accessing an alarm service, and if error information contained in an abnormal log of a front end is received but the system identifier identification code of the abnormal log is invalid, the abnormal log is not a log required to be maintained by a log maintenance system and is not required to be recorded in a log file;
the alarm server acquires the log file at regular time and judges whether the set alarm condition is met or not according to the log file;
and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
2. A front-end abnormal alarm processing method comprises the following steps:
receiving an abnormal log sent by a front end;
writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier comprises system name generation of a system to which a front end of an access log maintenance system belongs;
providing alarm configuration information, wherein the alarm configuration information is used for synchronizing to an alarm server so as to update an alarm condition in the alarm server; when an alarm condition is configured, an identification code generated according to a system name is used as a system identifier for accessing an alarm service, and if error information contained in an abnormal log of a front end is received but the system identifier identification code of the abnormal log is invalid, the abnormal log is not a log required to be maintained by a log maintenance system and is not required to be recorded in a log file;
and sending the log file to the alarm server based on the received log acquisition instruction of the alarm server so that the alarm server sends corresponding alarm information when determining that an alarm condition is reached based on the log file.
3. A front-end exception alarm handling method according to claim 2, said alarm condition comprising at least one of:
within the set recording time, the number of the abnormal logs reaching the alarm level exceeds a preset alarm threshold;
an exception log of priority alarm levels is detected.
4. A front-end abnormal alarm processing method comprises the following steps:
acquiring a log file from a log maintenance system at regular time, wherein the log file comprises an abnormal log generated based on a received front end and a corresponding system identifier, the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs, and if the log maintenance system receives error information contained in the abnormal log of the front end but the system identifier identification code of the abnormal log is invalid, the abnormal log is not a log required to be maintained by the log maintenance system and is not recorded in the log file;
judging whether a set alarm condition is reached or not according to the log file, wherein the alarm condition comprises an updated alarm condition after alarm configuration information provided by a log maintenance system is synchronized to an alarm server;
and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
5. The front-end exception alarm handling method according to claim 4, the method further comprising:
providing alarm configuration information, wherein the alarm configuration information comprises at least one alarm condition for triggering an alarm, and the alarm condition comprises:
within the set recording time, the number of the abnormal logs reaching the alarm level exceeds a preset alarm threshold;
an exception log of priority alarm levels is detected.
6. The front-end abnormal alarm processing method according to claim 4, after sending the alarm information, the method further comprises:
and pushing the notification message which sends the alarm information to a preset alarm receiver.
7. A front-end abnormal alarm processing method comprises the following steps:
receiving an abnormal log sent by a front end, writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier comprises system name generation based on a system to which the front end of an access log maintenance system belongs, and enabling the log maintenance system not to be a log required to be maintained by the log maintenance system if the log maintenance system receives error information contained in the abnormal log of the front end but the system identifier identification code of the abnormal log is invalid, and not to be recorded in the log file;
judging whether set alarm conditions are met or not according to the log file; the alarm condition comprises an updated alarm condition after alarm configuration information provided by the log maintenance system is synchronized to the alarm server;
and if so, sending out alarm information corresponding to the system to which the front end belongs.
8. A front-end abnormal alarm processing system comprises a log maintenance server and a background alarm server,
the log maintenance server is used for receiving an abnormal log sent by the front end; the system identifier is generated based on the system name of the system to which the front end of the access log maintenance system belongs; providing alarm configuration information, wherein the alarm configuration information is used for synchronizing to an alarm server so as to update an alarm condition in the alarm server; when an alarm condition is configured, an identification code generated according to a system name is used as a system identifier for accessing an alarm service, and if error information contained in an abnormal log of a front end is received but the system identifier identification code of the abnormal log is invalid, the abnormal log is not a log required to be maintained by a log maintenance system and is not required to be recorded in a log file;
the alarm server is used for acquiring log files from the log maintenance server at regular time; the log file is also used for judging whether a set alarm condition is met or not according to the log file; and sending out alarm information corresponding to the system to which the front end belongs when the alarm condition is met.
9. A front-end exception alert handling apparatus, the apparatus comprising:
the log receiving module is used for receiving the abnormal log sent by the front end;
the log recording module is used for writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which the front end of the access log maintenance system belongs; and if the log maintenance system receives error information contained in the abnormal log at the front end, but the system identifier identification code of the abnormal log is invalid, the abnormal log is not a log required to be maintained by the log maintenance system and is not recorded in a log file;
and the log sending module is used for sending the log file to the alarm server based on a received log obtaining instruction of the alarm server so as to enable the alarm server to send corresponding alarm information when determining that an alarm condition is reached based on the log file, wherein the alarm condition comprises an updated alarm condition after alarm configuration information provided by a log maintenance system is synchronized to the alarm server.
10. A front-end exception alert handling apparatus, the apparatus comprising:
the log obtaining module is used for obtaining a log file from the log maintenance system at regular time, wherein the log file comprises an abnormal log generated based on a received front end and a corresponding system identifier, the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs, and if the log maintenance system receives error information contained in the abnormal log of the front end but the system identifier identification code of the abnormal log is invalid, the abnormal log is not a log required to be maintained by the log maintenance system and is not recorded in the log file;
the judging module is used for judging whether a set alarm condition is reached according to the log file, wherein the alarm condition comprises an updated alarm condition after alarm configuration information provided by a log maintenance system is synchronized to an alarm server;
and the alarm module is used for sending alarm information corresponding to the system to which the front end belongs by the alarm server if the alarm information meets the requirement.
11. A front-end exception alert handling apparatus, the apparatus comprising:
the log recording module is used for receiving an abnormal log sent by a front end, writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier is generated based on a system name of a system to which the front end accessed to the log maintenance system belongs, and enabling the log maintenance system not to be a log required to be maintained by the log maintenance system if the log maintenance system receives error information contained in the abnormal log of the front end but the system identifier identification code of the abnormal log is invalid, and not to be recorded in the log file;
the judging module is used for judging whether set alarm conditions are met or not according to the log file, wherein the alarm conditions comprise updated alarm conditions after alarm configuration information provided by a log maintenance system is synchronized to an alarm server;
and the alarm module is used for sending out alarm information corresponding to the system to which the front end belongs when the alarm condition is met.
12. A front-end exception alert handling apparatus comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor performing:
receiving an abnormal log sent by a front end;
writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier comprises system name generation based on a system to which a front end of an access log maintenance system belongs, and enabling the log maintenance system not to be a log required to be maintained by the log maintenance system if the log maintenance system receives error information contained in the abnormal log of the front end but the system identifier identification code of the abnormal log is invalid, and not to be recorded in the log file;
and sending the log file to the alarm server based on a received log acquisition instruction of the alarm server so that the alarm server sends corresponding alarm information when determining that an alarm condition is reached based on the log file, wherein the alarm condition comprises an updated alarm condition after alarm configuration information provided by a log maintenance system is synchronized to the alarm server.
13. A front-end exception alert handling apparatus comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor performing:
acquiring a log file from a log maintenance system at regular time, wherein the log file comprises an abnormal log generated based on a received front end and a corresponding system identifier, the system identifier comprises a system name generated based on a system to which the front end accessed into the log maintenance system belongs, and if the log maintenance system receives error information contained in the abnormal log of the front end but the system identifier identification code of the abnormal log is invalid, the abnormal log is not a log required to be maintained by the log maintenance system and is not recorded in the log file;
judging whether a set alarm condition is reached or not according to the log file, wherein the alarm condition comprises an updated alarm condition after alarm configuration information provided by a log maintenance system is synchronized to an alarm server;
and if so, the alarm server sends out alarm information corresponding to the system to which the front end belongs.
14. A front-end exception alert handling apparatus comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor performing:
receiving an abnormal log sent by a front end, writing the abnormal log and a corresponding system identifier into a log file, wherein the system identifier comprises system name generation based on a system to which the front end of an access log maintenance system belongs, and enabling the log maintenance system not to be a log required to be maintained by the log maintenance system if the log maintenance system receives error information contained in the abnormal log of the front end but the system identifier identification code of the abnormal log is invalid, and not to be recorded in the log file;
judging whether set alarm conditions are met or not according to the log file, wherein the alarm conditions comprise updated alarm conditions after alarm configuration information provided by a log maintenance system is synchronized to an alarm server;
and if so, sending out alarm information corresponding to the system to which the front end belongs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710523342.5A CN107423194B (en) | 2017-06-30 | 2017-06-30 | Front-end abnormal alarm processing method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710523342.5A CN107423194B (en) | 2017-06-30 | 2017-06-30 | Front-end abnormal alarm processing method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107423194A CN107423194A (en) | 2017-12-01 |
| CN107423194B true CN107423194B (en) | 2021-01-22 |
Family
ID=60426314
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710523342.5A Active CN107423194B (en) | 2017-06-30 | 2017-06-30 | Front-end abnormal alarm processing method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107423194B (en) |
Families Citing this family (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108768747B (en) * | 2018-06-19 | 2021-04-06 | 嘉兴云切供应链管理有限公司 | Platform server for maintaining block chain network |
| CN109190384B (en) * | 2018-07-26 | 2022-02-22 | 百色学院 | Multi-center block chain fusing protection system and method |
| CN109359084A (en) * | 2018-08-27 | 2019-02-19 | 深圳壹账通智能科技有限公司 | Abnormality diagnostic method, device, equipment and storage medium in the processing of block chain information |
| CN109284267A (en) * | 2018-09-26 | 2019-01-29 | 深圳壹账通智能科技有限公司 | Blog management method and terminal device based on abnormal monitoring |
| CN111078513B (en) * | 2018-10-22 | 2024-02-27 | 杭州海康威视数字技术股份有限公司 | Log processing method, device, equipment, storage medium and log alarm system |
| CN110347565B (en) * | 2019-05-24 | 2022-06-03 | 平安科技（深圳）有限公司 | Application program abnormity analysis method and device and electronic equipment |
| CN112054915B (en) * | 2019-06-06 | 2023-10-03 | 阿里巴巴(中国)网络技术有限公司 | Processing method, device and system for client exception pre-warning and computing equipment |
| CN110601894B (en) * | 2019-09-18 | 2023-07-25 | 中国工商银行股份有限公司 | Alarm processing method and device, electronic equipment and readable storage medium |
| CN112700343A (en) * | 2019-10-23 | 2021-04-23 | 中国石油天然气股份有限公司 | Operation monitoring method and system based on oil gas Internet of things |
| CN111143164A (en) * | 2019-12-18 | 2020-05-12 | 银清科技有限公司 | Operation data processing method and device based on block chain |
| CN113364602A (en) * | 2020-03-03 | 2021-09-07 | 阿里巴巴集团控股有限公司 | Method, device and storage medium for triggering page fault alarm |
| CN111414269A (en) * | 2020-03-17 | 2020-07-14 | 深圳市朱墨科技有限公司 | Log alarm method, device, storage medium and equipment |
| CN111897834A (en) * | 2020-08-12 | 2020-11-06 | 网易（杭州）网络有限公司 | Log searching method and device and server |
| CN112015618A (en) * | 2020-08-17 | 2020-12-01 | 杭州指令集智能科技有限公司 | Abnormity warning method and device |
| CN112084097B (en) * | 2020-09-25 | 2024-05-14 | 中国建设银行股份有限公司 | Disk alarm method and device |
| CN112306812A (en) * | 2020-11-11 | 2021-02-02 | 武汉悦学帮网络技术有限公司 | Log processing method and device, computer equipment and storage medium |
| CN113312241A (en) * | 2021-06-29 | 2021-08-27 | 中国农业银行股份有限公司 | Abnormal alarm method, access log generation method and operation and maintenance system |
| CN113760658A (en) * | 2021-09-02 | 2021-12-07 | 山东派盟网络科技有限公司 | Monitoring method, device and equipment |
| CN114157553B (en) * | 2021-12-08 | 2024-06-18 | 深圳前海微众银行股份有限公司 | Data processing method, device, equipment and storage medium |
| CN115426278A (en) * | 2022-08-31 | 2022-12-02 | 长春嘉诚信息技术股份有限公司 | Web application real-time anomaly analysis method and system |
| CN115221529B (en) * | 2022-09-14 | 2022-12-27 | 杭州天谷信息科技有限公司 | Method and system for injecting abnormity of front-end webpage |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981943A (en) * | 2012-10-29 | 2013-03-20 | 新浪技术（中国）有限公司 | Method and system for monitoring application logs |
| US8677188B2 (en) * | 2007-06-20 | 2014-03-18 | Microsoft Corporation | Web page error reporting |
| CN104978529A (en) * | 2015-03-10 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Exception handling method, exception handling system and exception handling server for webpage front end |
| CN105471932A (en) * | 2014-08-06 | 2016-04-06 | 腾讯科技（深圳）有限公司 | Front-end application monitoring method, front-end application and front-end application monitoring system |
| CN106100936A (en) * | 2016-08-10 | 2016-11-09 | 乐视控股（北京）有限公司 | Webpage method for monitoring performance and device and the webserver, client |
| CN106383776A (en) * | 2016-08-30 | 2017-02-08 | 北京北信源软件股份有限公司 | Monitoring and self-healing method and apparatus for distributed search cluster system |
-
2017
- 2017-06-30 CN CN201710523342.5A patent/CN107423194B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8677188B2 (en) * | 2007-06-20 | 2014-03-18 | Microsoft Corporation | Web page error reporting |
| CN102981943A (en) * | 2012-10-29 | 2013-03-20 | 新浪技术（中国）有限公司 | Method and system for monitoring application logs |
| CN105471932A (en) * | 2014-08-06 | 2016-04-06 | 腾讯科技（深圳）有限公司 | Front-end application monitoring method, front-end application and front-end application monitoring system |
| CN104978529A (en) * | 2015-03-10 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Exception handling method, exception handling system and exception handling server for webpage front end |
| CN106100936A (en) * | 2016-08-10 | 2016-11-09 | 乐视控股（北京）有限公司 | Webpage method for monitoring performance and device and the webserver, client |
| CN106383776A (en) * | 2016-08-30 | 2017-02-08 | 北京北信源软件股份有限公司 | Monitoring and self-healing method and apparatus for distributed search cluster system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107423194A (en) | 2017-12-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107423194B (en) | Front-end abnormal alarm processing method, device and system | |
| KR102483025B1 (en) | Operational maintenance systems and methods | |
| CN107832196B (en) | Monitoring device and monitoring method for abnormal content of real-time log | |
| US20180365085A1 (en) | Method and apparatus for monitoring client applications | |
| US11294754B2 (en) | System and method for contextual event sequence analysis | |
| US20180322419A1 (en) | Model Driven Modular Artificial Intelligence Learning Framework | |
| US10983855B2 (en) | Interface for fault prediction and detection using time-based distributed data | |
| US8489941B2 (en) | Automatic documentation of ticket execution | |
| CN105743730A (en) | Method and system used for providing real-time monitoring for webpage service of mobile terminal | |
| CN103490941A (en) | Real-time monitoring on-line configuration method in cloud computing environment | |
| CN111459692B (en) | Method, apparatus and computer program product for predicting drive failure | |
| CN105471932A (en) | Front-end application monitoring method, front-end application and front-end application monitoring system | |
| US10372572B1 (en) | Prediction model testing framework | |
| Ramadas et al. | Patterns for things that fail | |
| CN108365982A (en) | Unit exception adjustment method, device, equipment and storage medium | |
| US11263072B2 (en) | Recovery of application from error | |
| CN106339372B (en) | Method and device for optimizing search engine | |
| CN110311806A (en) | A kind of mobile applications interface operating lag diagnostic method, system and terminal | |
| CN112783789B (en) | Adaptation test method, device and computer readable storage medium | |
| CN109710487A (en) | A kind of monitoring method and device | |
| CN112799910A (en) | Hierarchical monitoring method and device | |
| US10411959B1 (en) | Data analytics for the internet of things | |
| US11416187B2 (en) | Information processing system, information processing apparatus, and non-transitory computer readable medium | |
| CN110430093B (en) | Data processing method and device and computer readable storage medium | |
| US20240144558A1 (en) | Generating video streams to depict bot performance during an automation run |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: Greater Cayman, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |