CN113495820A - Method and device for collecting and processing abnormal information and abnormal monitoring system - Google Patents

Method and device for collecting and processing abnormal information and abnormal monitoring system Download PDF

Info

Publication number
CN113495820A
CN113495820A CN202010260028.4A CN202010260028A CN113495820A CN 113495820 A CN113495820 A CN 113495820A CN 202010260028 A CN202010260028 A CN 202010260028A CN 113495820 A CN113495820 A CN 113495820A
Authority
CN
China
Prior art keywords
information
abnormal
monitoring
abnormal information
target application
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.)
Granted
Application number
CN202010260028.4A
Other languages
Chinese (zh)
Other versions
CN113495820B (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 Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun 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 Jingdong Century Trading Co Ltd, Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN202010260028.4A priority Critical patent/CN113495820B/en
Publication of CN113495820A publication Critical patent/CN113495820A/en
Application granted granted Critical
Publication of CN113495820B publication Critical patent/CN113495820B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/302Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • 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
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3051Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • 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

Landscapes

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

Abstract

The invention discloses an abnormal information collecting and processing method and device and an abnormal monitoring system, and relates to the technical field of computers. One specific implementation of the method for collecting abnormal information includes: introducing a preset monitoring component into a client; when the target application generates an abnormal event, acquiring abnormal information corresponding to the abnormal event by using the monitoring component; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type; sending the acquired abnormal information to a monitoring background; after receiving the abnormal information, the monitoring background judges whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not, and gives an alarm when the quantity of the same type of abnormal information of the current target application meets the preset condition. The method and the device can acquire more comprehensive abnormal information, provide a path for abnormal recurrence, and filter the same type of abnormal information of the target application to avoid frequent alarm.

Description

Method and device for collecting and processing abnormal information and abnormal monitoring system
Technical Field
The invention relates to the technical field of computers, in particular to an abnormal information collecting and processing method and device and an abnormal monitoring system.
Background
With the continuous development of internet technology, Web applications (i.e., internet applications) become increasingly complex, which carry more and more business logic. In actual application, various anomalies often occur in the Web application, which may affect the user experience and cause loss to the service side. In order to find and repair abnormalities in time, technicians develop a variety of abnormality monitoring systems that collect and process abnormal information.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
the existing anomaly monitoring system can only collect a few types of anomaly information and cannot meet the actual requirements, and meanwhile, the existing system cannot provide a path and related information for anomaly recurrence. In addition, the existing system generally alarms when each piece of abnormal information is monitored, and such frequent alarms form obstacles to the problem finding and repairing.
Disclosure of Invention
In view of this, embodiments of the present invention provide an anomaly information collecting and processing method and apparatus, and an anomaly monitoring system, which can obtain more comprehensive anomaly information and provide a path for anomaly recurrence, and can also filter the same type of anomaly information of a target application to avoid frequent alarms.
To achieve the above object, according to one aspect of the present invention, there is provided an abnormality information collection method.
The abnormal information collection method of the embodiment of the invention is applied to a client, and comprises the following steps: introducing a preset monitoring component into a client; when the target application generates an abnormal event, acquiring abnormal information corresponding to the abnormal event by using the monitoring component; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type; sending the acquired abnormal information to a monitoring background; after receiving the abnormal information, the monitoring background judges whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not, and gives an alarm when the quantity of the same type of abnormal information of the current target application meets the preset condition.
Optionally, the timeline information comprises: context information, user behavior information, network request information and/or route skip information when an abnormal event occurs; and the step of acquiring the abnormal information corresponding to the abnormal event by using the monitoring component comprises the following steps: adding a first acquisition code in a page state change event related to user behavior in advance, and adding a second acquisition code in a page operation method related to route jump; when the page state change event is triggered, acquiring corresponding user behavior information according to the first acquisition code; and when the page operation method is triggered, acquiring corresponding route skipping information according to the second acquisition code.
Optionally, the abnormality information further includes: recording information generated by the monitoring component when the abnormal event occurs is utilized; the exception type includes at least one of: script exception, resource loading exception, Ajax loading exception, fetch request exception, jsonp request exception; the associated environmental information includes at least one of: client configuration information, current operating environment information, abnormal occurrence time, display screen size, window area size, current page height, current page address, current page source and client IP.
To achieve the above object, according to another aspect of the present invention, there is provided an abnormality information processing method.
The abnormal information processing method provided by the embodiment of the invention is applied to a monitoring background and comprises the following steps: receiving abnormal information which is sent by a client and corresponds to a target application; the abnormal information is acquired by utilizing a monitoring component introduced in advance by a client, and comprises abnormal detail information, associated environment information and timeline information; the exception detail information comprises an exception type; and judging whether the quantity of the same type abnormal information of the current target application meets a preset condition or not, and giving an alarm when the quantity of the same type abnormal information of the current target application meets the preset condition.
Optionally, the preset condition includes: greater than a preset threshold; wherein the preset threshold is preset for each application and each exception type; the threshold set for each application and each exception type includes a first type threshold corresponding to a first monitoring period and a second type threshold corresponding to a second monitoring period; the duration of the first monitoring period is longer than that of the second monitoring period.
Optionally, the determining whether the quantity of the same type of abnormal information of the current target application meets a preset condition, and giving an alarm when the quantity meets the preset condition includes: acquiring an abnormal type in the received abnormal information, and judging whether an abnormal information count corresponding to the target application and the abnormal type exists at present: if yes, judging whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the first monitoring period is larger than a corresponding first-type threshold value or not; or detecting whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the second monitoring period is greater than a corresponding second-class threshold value; alarming when the judgment result or the detection result is yes; otherwise, alarming.
To achieve the above object, according to still another aspect of the present invention, there is provided an abnormality information collecting apparatus.
The abnormal information collecting device of the embodiment of the invention is applied to the client and can comprise: the installation unit is used for introducing a preset monitoring component into the client; the acquisition unit is used for acquiring abnormal information corresponding to an abnormal event by using the monitoring component when the abnormal event occurs in the target application; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type; the reporting unit is used for sending the acquired abnormal information to the monitoring background; after receiving the abnormal information, the monitoring background judges whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not, and gives an alarm when the quantity of the same type of abnormal information of the current target application meets the preset condition.
To achieve the above object, according to still another aspect of the present invention, there is provided an abnormality information processing apparatus.
The abnormal information processing apparatus of the embodiment of the present invention may include: the receiving unit is used for receiving the abnormal information which is sent by the client and corresponds to the target application; the abnormal information is acquired by utilizing a monitoring component introduced in advance by a client, and comprises abnormal detail information, associated environment information and timeline information; the exception detail information comprises an exception type; and the warning unit is used for judging whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not and giving a warning when the quantity of the same type of abnormal information of the current target application meets the preset condition.
To achieve the above object, according to still another aspect of the present invention, an abnormality monitoring system is provided.
The abnormality monitoring system of the embodiment of the present invention may include: the monitoring component is arranged at the client side and the monitoring background at the server side; when the target application generates an abnormal event, the client acquires abnormal information corresponding to the abnormal event by using the monitoring component and sends the abnormal information to the monitoring background; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type; and the monitoring background receives the abnormal information and gives an alarm when judging that the quantity of the same type of abnormal information of the current target application meets a preset condition.
Optionally, after receiving the abnormal information, the monitoring background stores the abnormal information in a preset database; the system further comprises a monitoring foreground at the server side, and the monitoring foreground is used for analyzing the abnormal information stored in the database and displaying the analysis result.
To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.
An electronic device of the present invention includes: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the exception information collection method or the exception information processing method provided by the invention.
To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable storage medium.
A computer-readable storage medium of the present invention stores thereon a computer program that, when executed by a processor, implements an abnormality information collection method or an abnormality information processing method provided by the present invention.
According to the technical scheme of the invention, the embodiment of the invention has the following advantages or beneficial effects: after a pre-developed monitoring component is introduced into a client, the monitoring component can be utilized to acquire abnormal information and associated environment information of various common types and special types; by adding the acquisition code into the corresponding event of the original program, the time line information such as context, user behavior, network request, route jump and the like when an abnormality occurs can be acquired, and the associated environment information and the time line information can provide a path for the abnormal reproduction, so that the problem searching and repairing are facilitated. After the client reports the abnormal information to the monitoring background, the monitoring background can give an alarm when the same type of abnormal of the same application occurs for the first time and the occurrence frequency is greater than a threshold value, so that frequent alarms are avoided. In addition, the invention provides an anomaly monitoring system comprising a monitoring component, a monitoring background and a monitoring foreground, wherein the monitoring component is used for collecting and reporting anomaly information such as anomaly detail information, associated environment information, timeline information and the like in the application running process, the monitoring background is used for giving an alarm according to the quantity of the anomaly information and storing the anomaly information, and the monitoring foreground is used for realizing visual query and display of the anomaly information. Based on the abnormity monitoring system, a user can quickly find problems, locate the problems and solve the problems when abnormity occurs.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main steps of an abnormal information collection method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of the main steps of an abnormal information processing method according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart of the operation of the exception log receiving service in the embodiment of the present invention;
FIG. 4 is a schematic diagram of the components of an abnormal information collecting apparatus according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a part of an exception information handling apparatus according to an embodiment of the present invention;
FIG. 6 is a schematic diagram illustrating interaction of portions of an anomaly monitoring system in an embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 8 is a schematic structural diagram of an electronic device for implementing an abnormal information collecting method or an abnormal information processing method according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that the embodiments of the present invention and the technical features of the embodiments may be combined with each other without conflict.
Fig. 1 is a schematic diagram illustrating the main steps of an abnormal information collection method according to an embodiment of the present invention, which is applied to a client.
As shown in fig. 1, the method for collecting abnormal information according to the embodiment of the present invention may specifically be performed according to the following steps:
step S101: and introducing a preset monitoring component at the client.
In this step, the monitoring component is a SDK (Software Development Kit) developed in advance by the service side, which monitors and collects exception information of a target application installed on the client during running through code written in advance. Besides monitoring and collecting abnormal information, the monitoring component is also used for path arrangement and report of the abnormal information. Before use, the client needs to introduce the monitoring component from the server and install the monitoring component. The target application may be any client application program or may be a Web application such as various Web sites. In actual application, the monitoring component is bound with at least one target application of the client; when the bound target application is started, the monitoring component is started and executes a corresponding function; when an unbound application is launched, the monitoring component does not launch. The monitoring component provided by the embodiment of the invention can support various client platforms, such as windows, macOS, Linux, Android, iOS (the above five common client operating systems) and the like.
Step S102: when the target application generates an abnormal event, the monitoring component is utilized to acquire abnormal information corresponding to the abnormal event.
In this step, when the target application is started, the monitoring component is started accordingly, and monitors the running state of the target application. When an abnormal event (namely an error) occurs in the running process of the target application, the monitoring component executes predetermined processing logic to acquire corresponding abnormal information. In the embodiment of the invention, various abnormal information of common types and special types can be acquired by utilizing the monitoring component, and the coverage is higher. Preferably, each anomaly information obtained by the monitoring component may include anomaly detail information, associated environment information, and timeline information. The exception detail information may include an exception type, a file in which an exception occurs, a row number, a column number, and the like. The type of anomaly may include at least one of: script exceptions, resource load exceptions, Ajax (Asynchronous JavaScript And XML, JavaScript is a scripting language, XML is extensible markup language), load exceptions, fetch request exceptions (fetch is a program interface based on a program, And a program is a constructor), jsonnp request exceptions (json is a pattern of json, which is a data format), unhandled rejection (indicating unhandled discard; if a program is discarded in one polling of an event loop And the program does not bind an error handler, the exception will occur).
In the monitoring script, the collection of various abnormality detail information is achieved in the following manner. For script exceptions, window error events (an event used to detect front end exceptions) can be used to monitor specific error information; for resource loading exceptions, addEvent Listener (a kind of listening function) may be used to monitor and resolve the resource that failed loading in the callback function.
For Ajax load exceptions, hook functions can be monitored in xmlhttrequest. Fetch request exceptions, a browser native Fetch request can be handled using window. For unhandled projection, an addEventListener may be used to bind a listener for unhandled projection events to monitor for the occurrence of exceptions.
Preferably, the monitoring component can also be used for acquiring the associated environment information when the abnormity occurs. The associated environment information is external environment information when an exception occurs, and can be used for reproducing an exception path so as to quickly locate and solve the problem, and the associated environment information comprises at least one of the following: client configuration information (including hardware configuration information), current operating environment information, abnormal occurrence time, display screen size, window area size, current page height, current page link address, current page source (i.e. refer information in HTTP request header, HTTP indicates hypertext transfer protocol), and client IP address (IP indicates Internet protocol).
Preferably, the timeline information of the occurrence of the abnormality can be acquired by using the preset logic of the monitoring component. The time line information is related information before and after the abnormity occurs, and can reflect the operation path of a user when the abnormity occurs, so that a complete abnormity reproduction path can be provided, the problem can be rapidly positioned, and the problem can be solved in an auxiliary manner. The timeline information includes at least one of: context information (such as external variables on which the current page depends) when the abnormal event occurs, user behavior information (such as click behavior), network request information and route jump information.
In the embodiment of the present invention, the user behavior information may be obtained by the following method: adding a first acquisition code in a page state change event related to user behavior in advance by using a monitoring component, and adding a second acquisition code in a page operation method related to route jump; when the page state change event is triggered, acquiring corresponding user behavior information according to the first acquisition code; and when the page operation method is triggered, acquiring corresponding route skipping information according to the second acquisition code. Illustratively, the page state change event may be a post event that is triggered when the user clicks back or forward on the browser. The page operation method can be a pushState method or a ReplaceState method, the pushState method can directly change a page link address under the condition that a browser does not request data from a server, and the ReplaceState method is used for modifying the history.
In some embodiments, the recording information when the abnormality occurs may also be acquired by the monitoring component. For example, when an abnormality occurs in the running process of the Web application, the monitoring component may call a page recording tool to record a current page for a short time and generate a video file. The abnormality can be reproduced more intuitively by recording the information.
Step S103: and sending the acquired abnormal information to a monitoring background.
In this step, the acquired abnormal information may be sent to a monitoring background at the server by using the monitoring component. After receiving the abnormal information, the monitoring background executes a preset alarm mechanism, that is, determines whether the number of the same type of abnormal information (i.e., the abnormal information of the same type as the received abnormal information) of the current target application meets a preset condition (e.g., whether the number of the same type as the received abnormal information) or not (e.g., whether the number of the same type as the received abnormal information is greater than a preset threshold value) and alarms when the number of the same type of abnormal information meets the preset condition. The monitoring background is also responsible for storing the abnormal information into a database, managing projects (corresponding to the projects and the applications), managing users, setting a system and the like. By the mode, timely alarming of abnormal information and quantity filtering of the same type of abnormal information can be achieved (namely the same type of abnormal information applied to the same application is only alarmed once when the abnormal information occurs for multiple times), and frequent alarming is avoided.
Fig. 2 is a schematic diagram of main steps of an abnormal information processing method in an embodiment of the present invention, where the method is applied to a monitoring background deployed on a server.
As shown in fig. 2, the exception information processing method according to the embodiment of the present invention may perform the following steps:
step S201: and receiving exception information which is sent by the client and corresponds to the target application. In this step, the monitoring background receives the exception information of the target application sent by the client, and as described above, the exception information may include exception detail information, associated environment information, and timeline information.
Step S202: and judging whether the quantity of the same type abnormal information of the current target application meets a preset condition or not, and giving an alarm when the quantity of the same type abnormal information of the current target application meets the preset condition.
In this step, the monitoring background executes a preset alarm mechanism after receiving the above-mentioned abnormal information of the target application. Specifically, the monitoring background first checks the type of the exception information. In practical application, the monitoring background may extract data representing the exception type from the exception information, perform hash processing on the data to obtain a corresponding hash value, and finally compare the hash value with a hash value corresponding to the exception type stored in advance to determine the exception type corresponding to the exception information.
After the abnormal type of the abnormal information is determined, the monitoring background determines whether to alarm or not by judging whether the quantity of the abnormal information of the same type of the target application meets a preset condition (namely an alarm rule). In an actual scene, the time scale for counting the amount of the abnormal information may be various, for example, a first monitoring period and a second monitoring period with different durations may be set for counting, and the duration of the first monitoring period is longer than that of the second monitoring period. Illustratively, the first monitoring period may be days and the second monitoring period may be minutes. That is, a new first monitoring period starts when each day starts (from zero), and a new second monitoring period starts when each minute starts (from zero seconds), the amount of abnormal information counted in the first monitoring period may be referred to as the total amount of abnormal information, and the amount of abnormal information counted in the second monitoring period may be referred to as the frequency of occurrence of abnormal information.
In some embodiments, the determining whether the number of the same type of the target application abnormal information meets the preset condition may be determining whether the number is greater than a preset threshold, and the threshold may include a first type threshold corresponding to the first monitoring period and a second type threshold corresponding to the second monitoring period. In a specific scenario, the worker may set the first type threshold and the second type threshold in advance for each anomaly type of each application (which may also be referred to as a project). For example, the staff sets a first threshold value of 100 and a second threshold value of 10 for the script exception of the website a, so that when the total number of exceptions of the website on a certain day exceeds 100 or the frequency (i.e. the number of exceptions in a certain minute) exceeds 10, the monitoring background alarms.
In this step, after determining the exception type of the received exception information, the monitoring background first determines whether an exception information count corresponding to the target application and the exception type currently exists. Wherein the exception information count is determined by a counter provided in the cache system (e.g., Redis) and stored in the cache system, and the counter may count for each exception type of each application. The count may represent the number of abnormal information corresponding to the first monitoring period and the second monitoring period before the above-mentioned abnormal information is received. Generally, the count of the exception information is a positive integer, and if a certain application does not have a certain type of exception information in the first monitoring period and the second monitoring period, the corresponding count of the exception information does not exist in the cache system.
If the monitoring background judges that the abnormal information count corresponding to the target application and the abnormal type (the abnormal type of the received abnormal information) does not exist at present, the monitoring background shows that the type of the abnormal occurs in the first statistical period and the second statistical period, the received abnormal information is the first abnormal, and then the monitoring background can give an alarm to enable a worker to know the abnormal information in time. If the monitoring background judges that the abnormal information count corresponding to the target application and the abnormal type currently exists, judging whether the total abnormal information amount (which can be understood to be equal to the abnormal information count of the first monitoring period plus 1) corresponding to the target application and the abnormal type in the first monitoring period is larger than a corresponding first threshold, or detecting whether the total abnormal information amount (which can be understood to be equal to the abnormal information count of the second monitoring period plus 1) corresponding to the target application and the abnormal type in the second monitoring period is larger than a corresponding second threshold. If the judgment result (namely, the result of judging whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the first monitoring period is greater than the first-type threshold value) or the detection result (namely, the result of detecting whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the second monitoring period is greater than the second-type threshold value) is yes, the total quantity of the abnormal information exceeds the threshold value or the frequency exceeds the threshold value, and then an alarm is given. Illustratively, the alert mode includes at least one of: short message alarm, WeChat alarm, mail alarm, IM (Instant Messaging) alarm.
It can be understood that, in the above alarm mechanism, the monitoring background may use the amount of abnormal information in the first monitoring period or the second monitoring period alone to determine whether to alarm, that is, use the total amount or frequency of abnormal information alone to determine whether to alarm. After the alarm mechanism is executed, the monitoring background may store the received abnormal information in a preset database (e.g., Mysql) for subsequent reading and analysis.
In an actual scene, the monitoring background also has the functions of project management, user management, system setting and the like. Project management includes turning on or off an alarm switch for each project, setting a first type threshold and a second type threshold, setting project members, and the like. The user management includes setting worker information and the like. The system settings include interface settings, language settings, and the like. In the embodiment of the invention, the abnormal information can be reported and stored in the form of an abnormal log. In order to prevent reporting of abnormal logs of multiple users, multiple projects and high concurrency, the receiving, alarm judging and storing of the abnormal logs can be executed by an abnormal log receiving service which is independent from a monitoring background, and the functions of project management, user management, system setting and the like are realized by the monitoring background.
Fig. 3 is a schematic workflow diagram of an exception log receiving service in an embodiment of the present invention. As shown in fig. 3, after the exception log receiving service receives the exception information, the exception type data therein is first hashed in step S301. Step S302, judging whether the same type of abnormity exists in the items according to the hash value: if yes, go to step S304; otherwise, the process proceeds to step S303. Step S303 stores the abnormality information in the database and executes step S307. In step S304, the frequency or the total amount of the abnormal information is acquired in the Redis counter. Step S305, judging whether the frequency or the total quantity of the abnormal information meets the alarm rule: if yes, go to step S307; otherwise, step S306 is executed. In step S306, no processing is performed, that is, no alarm is performed, but the abnormal information needs to be counted and stored. And step S307, alarming.
According to the technical scheme of the embodiment of the invention, after the client introduces the pre-developed monitoring component, the monitoring component can be utilized to obtain abnormal information and associated environment information of various common types and special types; by adding the acquisition code into the corresponding event of the original program, the time line information such as context, user behavior, network request, route jump and the like when an abnormality occurs can be acquired, and the associated environment information and the time line information can provide a path for the abnormal reproduction, so that the problem searching and repairing are facilitated. After the client reports the abnormal information to the monitoring background, the monitoring background can give an alarm when the same type of abnormal of the same application occurs for the first time and the occurrence frequency is greater than a threshold value, so that frequent alarms are avoided. In addition, the invention provides an anomaly monitoring system comprising a monitoring component, a monitoring background and a monitoring foreground, wherein the monitoring component is used for collecting and reporting anomaly information such as anomaly detail information, associated environment information, timeline information and the like in the application running process, the monitoring background is used for giving an alarm according to the quantity of the anomaly information and storing the anomaly information, and the monitoring foreground is used for realizing visual query and display of the anomaly information. Based on the abnormity monitoring system, a user can quickly find problems, locate the problems and solve the problems when abnormity occurs.
It should be noted that, for the convenience of description, the foregoing method embodiments are described as a series of acts, but those skilled in the art will appreciate that the present invention is not limited by the order of acts described, and that some steps may in fact be performed in other orders or concurrently. Moreover, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no acts or modules are necessarily required to implement the invention.
To facilitate a better implementation of the above-described aspects of embodiments of the present invention, the following also provides relevant means for implementing the above-described aspects.
Referring to fig. 4, an abnormal information collecting apparatus 400 according to an embodiment of the present invention is applied to a client, and includes: an installation unit 401, an acquisition unit 402 and a reporting unit 403.
The installation unit 401 may be configured to introduce a preset monitoring component at the client; the acquisition unit 402 may be configured to, when an exception occurs in the target application, acquire exception information corresponding to the exception by using the monitoring component; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type; the reporting unit 403 may be configured to send the acquired abnormal information to the monitoring background; after receiving the abnormal information, the monitoring background judges whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not, and gives an alarm when the quantity of the same type of abnormal information of the current target application meets the preset condition.
In an embodiment of the present invention, the timeline information may include: context information, user behavior information, network request information and/or route skip information when an abnormal event occurs; the acquisition unit 402 may be further configured to: adding a first acquisition code in a page state change event related to user behavior in advance, and adding a second acquisition code in a page operation method related to route jump; when the page state change event is triggered, acquiring corresponding user behavior information according to the first acquisition code; and when the page operation method is triggered, acquiring corresponding route skipping information according to the second acquisition code.
As a preferable aspect, the abnormality information may further include: recording information generated by the monitoring component when the abnormal event occurs is utilized; the exception type includes at least one of: script exception, resource loading exception, Ajax loading exception, fetch request exception, jsonp request exception; the associated environmental information includes at least one of: client configuration information, current operating environment information, abnormal occurrence time, display screen size, window area size, current page height, current page address, current page source and client IP.
Fig. 5 is a schematic diagram of a component of an exception information processing apparatus according to an embodiment of the present invention.
As shown in fig. 5, the application of the abnormal information processing apparatus 500 according to the embodiment of the present invention in the monitoring background may include: a receiving unit 501 and an alarm unit 502.
The receiving unit 501 may be configured to receive exception information corresponding to a target application, which is sent by a client; the abnormal information is acquired by utilizing a monitoring component introduced in advance by a client, and comprises abnormal detail information, associated environment information and timeline information; the exception detail information comprises an exception type; the alarm unit 502 may be configured to determine whether the quantity of the same type of abnormal information of the current target application meets a preset condition, and alarm when the quantity meets the preset condition.
Preferably, the preset condition may include: greater than a preset threshold; wherein the preset threshold is preset for each application and each exception type; the threshold set for each application and each exception type includes a first type threshold corresponding to a first monitoring period and a second type threshold corresponding to a second monitoring period; the duration of the first monitoring period is longer than that of the second monitoring period.
Furthermore, in the embodiment of the present invention, the alarm unit 502 may further be configured to: acquiring an abnormal type in the received abnormal information, and judging whether an abnormal information count corresponding to the target application and the abnormal type exists at present: if yes, judging whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the first monitoring period is larger than a corresponding first-type threshold value or not; or detecting whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the second monitoring period is greater than a corresponding second-class threshold value; alarming when the judgment result or the detection result is yes; otherwise, alarming.
According to the technical scheme of the embodiment of the invention, after the client introduces the pre-developed monitoring component, the monitoring component can be utilized to obtain abnormal information and associated environment information of various common types and special types; by adding the acquisition code into the corresponding event of the original program, the time line information such as context, user behavior, network request, route jump and the like when an abnormality occurs can be acquired, and the associated environment information and the time line information can provide a path for the abnormal reproduction, so that the problem searching and repairing are facilitated. After the client reports the abnormal information to the monitoring background, the monitoring background can give an alarm when the same type of abnormal of the same application occurs for the first time and the occurrence frequency is greater than a threshold value, so that frequent alarms are avoided. In addition, the invention provides an anomaly monitoring system comprising a monitoring component, a monitoring background and a monitoring foreground, wherein the monitoring component is used for collecting and reporting anomaly information such as anomaly detail information, associated environment information, timeline information and the like in the application running process, the monitoring background is used for giving an alarm according to the quantity of the anomaly information and storing the anomaly information, and the monitoring foreground is used for realizing visual query and display of the anomaly information. Based on the abnormity monitoring system, a user can quickly find problems, locate the problems and solve the problems when abnormity occurs.
Fig. 6 is an interaction diagram of parts of the anomaly monitoring system in the embodiment of the present invention. As shown in fig. 6, the abnormality monitoring system according to the embodiment of the present invention may include: the monitoring system comprises a monitoring component installed at a client and a monitoring background at a server.
In specific application, when an abnormal event occurs in a target application, a client acquires abnormal information corresponding to the abnormal event by using the monitoring component (step S601) and reports the abnormal information to a monitoring background (step S602); the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type; the monitoring background receives the reported abnormal information and gives an alarm when the quantity of the abnormal information of the same type of the current target application is judged to meet the preset condition (step S603). After executing the alarm mechanism, the monitoring background may store the exception information in a preset database (step S604). The abnormal information collection based on the monitoring component, the specific data in the abnormal information, the obtaining method and the alarm mechanism of the monitoring background are all introduced in the foregoing, and are not repeated here.
As a preferred solution, the anomaly monitoring system may further include a monitoring foreground at the server, which is used for analyzing the anomaly information stored in the database and displaying the analysis result. In practical application, the monitoring foreground may call a database query interface of the monitoring background to read the abnormal information and other related information (step S605), so as to present information such as application configuration information, project members, abnormal quantity, abnormal trend and the like to the staff (step S606).
In the technical scheme of the embodiment of the invention, a monitoring component for collecting and reporting abnormal information is developed, and a monitoring background for receiving, analyzing, storing and inquiring the abnormal information and a monitoring foreground for displaying the abnormal information are established. In a specific scenario, a user embeds a monitoring component in an application, and after the application runs, the monitoring component runs along with the application, and starts to collect abnormal information. And after the collection and the arrangement of the abnormal information are finished, reporting to an abnormal log receiving service, verifying, counting and storing the received abnormal data by the service, and triggering an alarm notification service to alarm workers if the received abnormal data accord with a preset alarm rule, thereby realizing a quick and timely alarm mechanism and enabling the workers to find problems in the shortest time. After receiving the alarm, the staff can check the specific abnormal trend of the application and the specific data of certain abnormal information in the monitoring foreground. On the basis, the staff can reproduce the abnormal path according to a series of associated environment information, timeline information and the like in the process from the corresponding operation of the user to the occurrence of the abnormal process, so that the problem can be conveniently and quickly positioned, and the problem can be solved.
Fig. 7 shows an exemplary system architecture 700 of an exception information collection method, an exception information processing method, an exception information collection apparatus, or an exception information processing apparatus to which embodiments of the present invention may be applied.
As shown in fig. 7, the system architecture 700 may include terminal devices 701, 702, 703, a network 704, a monitoring background 705, and a monitoring foreground 706 (this architecture is merely an example, and components included in a specific architecture may be adjusted according to application specific situations). Network 704 is used to provide a medium for communication links between end devices 701, 702, 703 and monitoring back 705 and monitoring front 706. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use end devices 701, 702, 703 to interact with a monitoring back-end 705, a monitoring front-end 706 over a network 704, to receive or send messages, etc. Various client applications and monitoring components may be installed on the terminal devices 701, 702, 703.
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like. The terminal devices 701, 702, and 703 may send the abnormal information obtained by using the monitoring component to the monitoring background 705, and the monitoring background 705 may alarm after receiving the abnormal information and determining that the abnormal information meets the alarm rule. The monitoring foreground 706 may obtain the abnormal information by calling a query interface provided by the monitoring background and visually display the abnormal information to the terminal devices 701, 702, and 703.
It should be noted that the abnormal information collecting method provided by the embodiment of the present invention is generally executed by the terminal devices 701, 702, and 703, and the abnormal information processing method is generally executed by the server 705; accordingly, the abnormality information collection means is generally provided in the terminal devices 701, 702, 703, and the abnormality information processing means is generally provided in the server 705.
It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. Monitoring back-end 705 and monitoring front-end 706 may be respectively disposed on the same server as independent services.
The invention also provides the electronic equipment. The electronic device of the embodiment of the invention comprises: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the exception information collection method or the exception information processing method provided by the invention.
Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use in implementing an electronic device of an embodiment of the present invention. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data necessary for the operation of the computer system 800 are also stored. The CPU801, ROM 802, and RAM803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted into the storage section 808 as necessary.
In particular, the processes described in the main step diagrams above may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the main step diagram. In the above-described embodiment, the computer program can be downloaded and installed from a network via the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the central processing unit 801, performs the above-described functions defined in the system of the present invention.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present invention may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor comprises an installation unit, a collection unit and a reporting unit. Where the names of the units do not in some cases constitute a limitation of the unit itself, for example, the mounting unit may also be described as a "unit providing a monitoring component to the acquisition unit".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to perform steps comprising: introducing a preset monitoring component into a client; when the target application generates an abnormal event, acquiring abnormal information corresponding to the abnormal event by using the monitoring component; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type; sending the acquired abnormal information to a monitoring background; after receiving the abnormal information, the monitoring background judges whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not, and gives an alarm when the quantity of the same type of abnormal information of the current target application meets the preset condition. Or receiving abnormal information which is sent by the client and corresponds to the target application; the abnormal information is acquired by utilizing a monitoring component introduced in advance by a client, and comprises abnormal detail information, associated environment information and timeline information; the exception detail information comprises an exception type; and judging whether the quantity of the same type abnormal information of the current target application meets a preset condition or not, and giving an alarm when the quantity of the same type abnormal information of the current target application meets the preset condition.
According to the technical scheme of the embodiment of the invention, after the client introduces the pre-developed monitoring component, the monitoring component can be utilized to obtain abnormal information and associated environment information of various common types and special types; by adding the acquisition code into the corresponding event of the original program, the time line information such as context, user behavior, network request, route jump and the like when an abnormality occurs can be acquired, and the associated environment information and the time line information can provide a path for the abnormal reproduction, so that the problem searching and repairing are facilitated. After the client reports the abnormal information to the monitoring background, the monitoring background can give an alarm when the same type of abnormal of the same application occurs for the first time and the occurrence frequency is greater than a threshold value, so that frequent alarms are avoided. In addition, the invention provides an anomaly monitoring system comprising a monitoring component, a monitoring background and a monitoring foreground, wherein the monitoring component is used for collecting and reporting anomaly information such as anomaly detail information, associated environment information, timeline information and the like in the application running process, the monitoring background is used for giving an alarm according to the quantity of the anomaly information and storing the anomaly information, and the monitoring foreground is used for realizing visual query and display of the anomaly information. Based on the abnormity monitoring system, a user can quickly find problems, locate the problems and solve the problems when abnormity occurs.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (12)

1. An abnormal information collection method applied to a client, the method comprising:
introducing a preset monitoring component into a client;
when the target application generates an abnormal event, acquiring abnormal information corresponding to the abnormal event by using the monitoring component; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type;
sending the acquired abnormal information to a monitoring background; after receiving the abnormal information, the monitoring background judges whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not, and gives an alarm when the quantity of the same type of abnormal information of the current target application meets the preset condition.
2. The method of claim 1, wherein the timeline information comprises: context information, user behavior information, network request information and/or route skip information when an abnormal event occurs; and the step of acquiring the abnormal information corresponding to the abnormal event by using the monitoring component comprises the following steps:
adding a first acquisition code in a page state change event related to user behavior in advance, and adding a second acquisition code in a page operation method related to route jump;
when the page state change event is triggered, acquiring corresponding user behavior information according to the first acquisition code;
and when the page operation method is triggered, acquiring corresponding route skipping information according to the second acquisition code.
3. The method according to claim 1 or 2,
the abnormality information further includes: recording information generated by the monitoring component when the abnormal event occurs is utilized;
the exception type includes at least one of: script exception, resource loading exception, Ajax loading exception, fetch request exception, jsonp request exception;
the associated environmental information includes at least one of: client configuration information, current operating environment information, abnormal occurrence time, display screen size, window area size, current page height, current page address, current page source and client IP.
4. An abnormal information processing method is applied to a monitoring background, and is characterized by comprising the following steps:
receiving abnormal information which is sent by a client and corresponds to a target application; the abnormal information is acquired by utilizing a monitoring component introduced in advance by a client, and comprises abnormal detail information, associated environment information and timeline information; the exception detail information comprises an exception type;
and judging whether the quantity of the same type abnormal information of the current target application meets a preset condition or not, and giving an alarm when the quantity of the same type abnormal information of the current target application meets the preset condition.
5. The method according to claim 4, wherein the preset conditions include: greater than a preset threshold; wherein,
the preset threshold is preset for each application and each exception type;
the threshold set for each application and each exception type includes a first type threshold corresponding to a first monitoring period and a second type threshold corresponding to a second monitoring period;
the duration of the first monitoring period is longer than that of the second monitoring period.
6. The method of claim 5, wherein the step of judging whether the quantity of the same type abnormal information of the current target application meets a preset condition and giving an alarm when the quantity of the same type abnormal information meets the preset condition comprises the following steps:
acquiring an abnormal type in the received abnormal information, and judging whether an abnormal information count corresponding to the target application and the abnormal type exists at present:
if yes, judging whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the first monitoring period is larger than a corresponding first-type threshold value or not; or detecting whether the total quantity of the abnormal information corresponding to the target application and the abnormal type in the second monitoring period is greater than a corresponding second-class threshold value; alarming when the judgment result or the detection result is yes;
otherwise, alarming.
7. An abnormal information collecting device applied to a client, the device comprising:
the installation unit is used for introducing a preset monitoring component into the client;
the acquisition unit is used for acquiring abnormal information corresponding to an abnormal event by using the monitoring component when the abnormal event occurs in the target application; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type;
the reporting unit is used for sending the acquired abnormal information to the monitoring background; after receiving the abnormal information, the monitoring background judges whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not, and gives an alarm when the quantity of the same type of abnormal information of the current target application meets the preset condition.
8. An abnormal information processing device applied to a monitoring background, the device comprising:
the receiving unit is used for receiving the abnormal information which is sent by the client and corresponds to the target application; the abnormal information is acquired by utilizing a monitoring component introduced in advance by a client, and comprises abnormal detail information, associated environment information and timeline information; the exception detail information comprises an exception type;
and the warning unit is used for judging whether the quantity of the same type of abnormal information of the current target application meets a preset condition or not and giving a warning when the quantity of the same type of abnormal information of the current target application meets the preset condition.
9. An anomaly monitoring system, said system comprising: the monitoring component is arranged at the client side and the monitoring background at the server side; wherein,
when the target application generates an abnormal event, the client acquires abnormal information corresponding to the abnormal event by using the monitoring component and sends the abnormal information to the monitoring background; the abnormal information comprises abnormal detail information, associated environment information and timeline information, and the abnormal detail information comprises an abnormal type;
and the monitoring background receives the abnormal information and gives an alarm when judging that the quantity of the same type of abnormal information of the current target application meets a preset condition.
10. The system of claim 9,
after receiving the abnormal information, the monitoring background stores the abnormal information in a preset database;
the system further comprises a monitoring foreground at the server side, and the monitoring foreground is used for analyzing the abnormal information stored in the database and displaying the analysis result.
11. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.
CN202010260028.4A 2020-04-03 2020-04-03 Anomaly information collecting and processing method and device and anomaly monitoring system Active CN113495820B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010260028.4A CN113495820B (en) 2020-04-03 2020-04-03 Anomaly information collecting and processing method and device and anomaly monitoring system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010260028.4A CN113495820B (en) 2020-04-03 2020-04-03 Anomaly information collecting and processing method and device and anomaly monitoring system

Publications (2)

Publication Number Publication Date
CN113495820A true CN113495820A (en) 2021-10-12
CN113495820B CN113495820B (en) 2024-06-18

Family

ID=77995324

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010260028.4A Active CN113495820B (en) 2020-04-03 2020-04-03 Anomaly information collecting and processing method and device and anomaly monitoring system

Country Status (1)

Country Link
CN (1) CN113495820B (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114281038A (en) * 2021-12-15 2022-04-05 中粮包装(天津)有限公司 Production site abnormal problem linkage alarm method, device and system and storage medium
CN115328743A (en) * 2022-10-13 2022-11-11 深圳市华曦达科技股份有限公司 Android device abnormity early warning processing method and system and readable storage medium
CN115378925A (en) * 2022-07-29 2022-11-22 广州博冠信息科技有限公司 Abnormal request capturing method and device, electronic equipment and storage medium
CN115426278A (en) * 2022-08-31 2022-12-02 长春嘉诚信息技术股份有限公司 Web application real-time anomaly analysis method and system
WO2023093394A1 (en) * 2021-11-26 2023-06-01 中兴通讯股份有限公司 Log-based anomaly monitoring method, system, and apparatus, and storage medium
CN118035049A (en) * 2024-02-29 2024-05-14 朴道征信有限公司 Application interface abnormality warning method, device, electronic equipment and medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103887886A (en) * 2014-04-14 2014-06-25 杭州昊美科技有限公司 Power network detection system and method based on sensor network
WO2019223062A1 (en) * 2018-05-22 2019-11-28 平安科技(深圳)有限公司 Method and system for processing system exceptions
CN110597694A (en) * 2019-08-09 2019-12-20 深圳木成林科技有限公司 Method and terminal for monitoring front-end page

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103887886A (en) * 2014-04-14 2014-06-25 杭州昊美科技有限公司 Power network detection system and method based on sensor network
WO2019223062A1 (en) * 2018-05-22 2019-11-28 平安科技(深圳)有限公司 Method and system for processing system exceptions
CN110597694A (en) * 2019-08-09 2019-12-20 深圳木成林科技有限公司 Method and terminal for monitoring front-end page

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
谭玉茹;吴琦;李婷婷;赵伟;程小东;: "用于计量异常事件分析系统的数据模拟算法", 国网技术学院学报, no. 01, 28 February 2016 (2016-02-28) *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023093394A1 (en) * 2021-11-26 2023-06-01 中兴通讯股份有限公司 Log-based anomaly monitoring method, system, and apparatus, and storage medium
CN114281038A (en) * 2021-12-15 2022-04-05 中粮包装(天津)有限公司 Production site abnormal problem linkage alarm method, device and system and storage medium
CN115378925A (en) * 2022-07-29 2022-11-22 广州博冠信息科技有限公司 Abnormal request capturing method and device, electronic equipment and storage medium
CN115426278A (en) * 2022-08-31 2022-12-02 长春嘉诚信息技术股份有限公司 Web application real-time anomaly analysis method and system
CN115328743A (en) * 2022-10-13 2022-11-11 深圳市华曦达科技股份有限公司 Android device abnormity early warning processing method and system and readable storage medium
CN115328743B (en) * 2022-10-13 2023-01-06 深圳市华曦达科技股份有限公司 Android device abnormity early warning processing method and system and readable storage medium
CN118035049A (en) * 2024-02-29 2024-05-14 朴道征信有限公司 Application interface abnormality warning method, device, electronic equipment and medium

Also Published As

Publication number Publication date
CN113495820B (en) 2024-06-18

Similar Documents

Publication Publication Date Title
CN113495820B (en) Anomaly information collecting and processing method and device and anomaly monitoring system
CN109067610B (en) Monitoring method and device
CN107896172B (en) Monitoring fault processing method and device, storage medium and electronic equipment
CN111385148A (en) Service alarm method, device, computer equipment and storage medium
CN113448795B (en) Method, apparatus and computer program product for obtaining system diagnostic information
CN113760634A (en) Data processing method and device
CN112445860B (en) Method and device for processing distributed transaction
US11121912B2 (en) Method and apparatus for processing information
CN112860504A (en) Monitoring method and device, computer storage medium and electronic equipment
US9594622B2 (en) Contacting remote support (call home) and reporting a catastrophic event with supporting documentation
CN111371586B (en) Log data transmission method, device and equipment
CN113778800B (en) Error information processing method, device, system, equipment and storage medium
CN113094268B (en) Test method, test device, test equipment and test medium
CN112783730B (en) Interface monitoring method, device, medium and electronic equipment
CN115202973A (en) Application running state determining method and device, electronic equipment and medium
CN109960659B (en) Method and device for detecting application program
CN114091702A (en) Event monitoring method and device, electronic equipment and storage medium
US10296967B1 (en) System, method, and computer program for aggregating fallouts in an ordering system
CN114968696A (en) Index monitoring method, electronic equipment and chip system
CN113743842A (en) Multi-source data difference warning method and device
CN111290873A (en) Fault processing method and device
CN112783677A (en) Method and device for monitoring service abnormity
CN115499292B (en) Alarm method, device, equipment and storage medium
CN112671822B (en) Service request processing method, device, storage medium, server and system
CN115934461A (en) Service system monitoring method, device, medium and equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant