Abnormal monitoring method, computing device and computer readable storage medium
By obtaining and deploying the monitoring rules of the target application, real-time detection of operating status and outputting abnormal information, the problem of inactivity of internal monitoring in the existing technology is solved, timely monitoring and active early warning of applications are achieved, and user experience and application are improved stability.
Patent Information
- Application Number
- CN202411364194.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-28
- Publication Date
- 2025-01-07
AI Technical Summary
The prior art lacks real-time effectiveness in monitoring and proactive early warning of internal operation of applications, and cannot meet the needs of rapid development and high performance.
By obtaining the monitoring rules of the target application, deploying and updating the monitoring rules, detecting the operating status in real time, judging and outputting abnormal information, timely monitoring and active early warning of the target application.
It improves user experience, ensures the stability and performance of the application, reduces the risk of failure, and realizes timely monitoring and active early warning of the operation of the application.
Smart Images
Figure CN119271496A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to an abnormality monitoring method, a computing device, and a computer-readable storage medium. Background Art
[0002] With the rapid development of business and the continuous growth of digital needs, the number of users has increased rapidly. In order to ensure user experience, product performance and experience requirements are getting higher and higher, and the iteration speed is also accelerating. Therefore, it is imperative to establish a full-process, standardized, automated and intelligent monitoring and management system.
[0003] In existing solutions, the operating system, middleware, etc. are generally monitored, which lacks real-time and effective monitoring and active early warning of the internal operation of the application. Summary of the invention
[0004] The purpose of this application is to provide an abnormality monitoring method, a computing device and a computer-readable storage medium, which realize timely monitoring and active early warning of the operation status of the target application and improve the user experience.
[0005] To achieve the above objectives:
[0006] In a first aspect, an embodiment of the present application provides an abnormality monitoring method, which is applied to a client, comprising:
[0007] Obtaining target monitoring rules corresponding to a target application, and deploying the target monitoring rules in the target application;
[0008] Determine, according to the target monitoring rule, first abnormal information of the target application; and / or determine second abnormal information when the target monitoring rule is executed;
[0009] The first abnormality information and / or the second abnormality information is output.
[0010] In one embodiment, the step of acquiring a target monitoring rule corresponding to a target application and deploying the target monitoring rule in the target application includes:
[0011] Based on a preset time interval, obtaining a target monitoring rule corresponding to the target application;
[0012] If the target application does not have an initial monitoring rule, deploying the target monitoring rule into the target application;
[0013] If the target application is provided with an initial monitoring rule, the initial monitoring rule is updated according to the target monitoring rule.
[0014] In one embodiment, the target monitoring rule includes the operation type to be monitored and the first alarm condition.
[0015] The determining, according to the target monitoring rule, first abnormal information of the target application includes:
[0016] Acquire first operation information corresponding to each operation type in the target application;
[0017] Determining whether the target application is abnormal according to the first operation information and the first alarm condition;
[0018] If so, the first abnormal information of the target application is determined according to the judgment result and the operation information.
[0019] In one embodiment, the target monitoring rule includes a second alarm condition;
[0020] The determining of the second abnormal information when the target monitoring rule is executed includes:
[0021] Acquire second operation information corresponding to the target monitoring rule when it is running;
[0022] Determining whether the operating state of the target monitoring rule is abnormal according to the second operating information and the second alarm condition;
[0023] If so, the second abnormal information when the target monitoring rule is running is determined according to the judgment result and the second running information.
[0024] In one embodiment, the target monitoring rule includes a first alarm frequency, and / or a second alarm frequency;
[0025] The outputting the first abnormality information and / or the second abnormality information includes:
[0026] If the first abnormal information is determined, outputting the first abnormal information based on the first alarm frequency; and / or,
[0027] If the second abnormal information is determined, the second abnormal information is output based on the second alarm frequency.
[0028] In a second aspect, the present application provides an abnormality monitoring method, which is applied to a server, comprising:
[0029] Setting a target monitoring rule corresponding to the target application, and sending the target monitoring rule to the client; the target monitoring rule is used to monitor the first abnormal information corresponding to the target application in the client, and the second abnormal information of the operation of the target monitoring rule;
[0030] In response to receiving the first exception information and / or the second exception information, the first exception information and / or the second exception information are processed.
[0031] In one implementation, the processing of the second abnormal information includes:
[0032] According to the second abnormal information, sending an abnormal reason acquisition request to the client to obtain the abnormal reason for the abnormality of the running state of the target monitoring rule;
[0033] The operating parameters of the target monitoring rule are updated according to the abnormal cause.
[0034] In one embodiment, the method further comprises:
[0035] Detect the communication status with the client;
[0036] If the communication state is detected to be abnormal, a connection request is resent to the client to reconnect for communication.
[0037] In a third aspect, an embodiment of the present application provides a computing device, specifically comprising:
[0038] processor;
[0039] a memory for storing instructions executable by the processor;
[0040] Wherein, the processor is configured to execute the instructions to perform the abnormality monitoring method as described in the first aspect.
[0041] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the instructions in the computer-readable storage medium are executed by a processor of a computing device, the computing device is enabled to implement the abnormality monitoring method as described in the first aspect.
[0042] The abnormal monitoring method, computing device and computer-readable storage medium provided in the embodiments of the present application are applied to the client, including: obtaining the target monitoring rules corresponding to the target application, and deploying the target monitoring rules in the target application; determining the first abnormal information of the target application according to the target monitoring rules; and / or determining the second abnormal information when the target monitoring rules are running; outputting the first abnormal information and / or the second abnormal information. In this way, according to the target detection rules deployed in the target application, the first abnormal information and / or the second abnormal information are correspondingly determined, and an output reminder is performed, which can realize timely monitoring and active early warning of the operation of the target application, and improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] Figure 1 Schematic diagram of the process of the abnormal monitoring method provided by the embodiment of the present invention Figure 1 ;
[0044] Figure 2 Schematic diagram of the process of the abnormal monitoring method provided by the embodiment of the present invention Figure 1 ;
[0045] Figure 3 A flow chart of the abnormal monitoring method provided by an embodiment of the present invention;
[0046] Figure 4 A schematic diagram of the structure of a computing device provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0047] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0048] It should be noted that, in this article, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.
[0049] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of..." or "when..." or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising", "including" indicate that there are described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Thus, “A, B, or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A, B, and C.” An exception to this definition will occur only when a combination of elements, functions, steps, or operations are inherently mutually exclusive in some manner.
[0050] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0051] It should be noted that, in this article, step codes such as S101, S102, etc. are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the sequence. When implementing the step, those skilled in the art may execute S102 first and then S101, etc., but these should all be within the scope of protection of this application.
[0052] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0053] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.
[0054] See also Figure 1 The embodiment of the present application provides an abnormality monitoring method, which can be implemented in software and / or hardware. In this embodiment, the abnormality monitoring method is applied to a client as an example. The abnormality monitoring method provided in this embodiment includes:
[0055] Step S101: Obtain target monitoring rules corresponding to a target application, and deploy the target monitoring rules in the target application.
[0056] Optionally, after obtaining the target monitoring rules corresponding to the target application, the target monitoring rules are woven into the target application in an aspect-oriented programming (AOP) manner based on bytecode enhancement technology. The bytecode enhancement technology framework includes Javassist, ASM, ByteBuddy, etc. In this way, the monitoring function of the target application is determined based on the target monitoring rules without modifying the source code.
[0057] In one embodiment, obtaining a target monitoring rule corresponding to a target application and deploying the target monitoring rule in the target application includes:
[0058] Based on the preset time interval, obtain the target monitoring rules corresponding to the target application;
[0059] If the target application does not have an initial monitoring rule, deploy the target monitoring rule to the target application;
[0060] If the target application has an initial monitoring rule, the initial monitoring rule is updated to the target monitoring rule.
[0061] Optionally, if no monitoring rules are pre-set in the target application, the acquired target rules are directly deployed to the target application. If it is detected that the target application has an initial monitoring rule, then further compare whether there is a difference between the target monitoring rule and the initial monitoring rule. If there is a difference, the target monitoring rule directly replaces the initial monitoring rule, or based on the difference between the target monitoring rule and the initial monitoring rule, the initial monitoring rule is updated; if the target monitoring rule is consistent with the initial monitoring rule, the initial monitoring rule is directly used as the target monitoring rule of the target program. Here, the target monitoring rule may include any of the following: on the basis of the initial monitoring rule, some abnormal program problems in the initial monitoring rule are modified to generate the target monitoring rule; the monitoring content of the target application by the initial monitoring rule is modified to generate the target monitoring rule; the rules and programs for monitoring the target application are reset to generate the target monitoring rule; the target monitoring rule is consistent with the content of the initial monitoring rule. In this way, by obtaining the target monitoring rule of the target application in real time and adjusting the monitoring of the target application in real time, the accuracy and timeliness of the monitoring are ensured.
[0062] Here, the Network Time Protocol (NTP) can be used to synchronize the clocks of the client and server. In this way, by introducing a version number or timestamp, it can help identify the difference between the target monitoring rule and the initial monitoring rule, so as to determine whether the initial monitoring rule needs to be updated.
[0063] Step S102: determining first abnormal information of a target application according to a target monitoring rule; and / or determining second abnormal information when the target monitoring rule is executed.
[0064] Among them, the target monitoring rules are generally represented by Java running programs, which detect the environmental status of the target monitoring rules in real time, including the running status of key resources such as memory, threads, class loading, etc., and determine the second abnormal information when the target monitoring rules are running according to the detected running status.
[0065] Optionally, after the target monitoring rule is deployed to the target application, the running state of the target application is monitored in real time based on the target monitoring rule, and when an abnormality is detected in the target application, the first abnormality information of the target application is correspondingly determined. It is understandable that if the target application is in a normal state, the target application continues to be monitored without determining the first abnormality information. Similarly, if the running state of the target monitoring rule is normal, the running program of the target monitoring rule continues to be monitored.
[0066] In one embodiment, the target monitoring rule includes the operation type to be monitored and the first alarm condition.
[0067] Determine the first abnormal information of the target application according to the target monitoring rule, including:
[0068] Obtaining first operation information corresponding to each operation type in the target application;
[0069] Determining whether the target application is abnormal according to the first operation information and the first alarm condition;
[0070] If so, the first abnormal information of the target application is determined according to the judgment result and the operation information.
[0071] The operation types that need to be monitored include the target application's thread usage time, keywords, resource occupancy rate, monitoring path, etc. The first alarm condition includes the detection threshold, such as the resource occupancy rate warning threshold, thread usage time threshold, etc.
[0072] Optionally, the target application's thread usage time, keywords, resource occupancy rate, monitoring path and other operating parameters are obtained, and the obtained operating parameters are compared based on the first alarm condition of the target monitoring rule to determine whether the target application is abnormal. This can be specifically performed as follows: the target application's thread usage time is obtained, and the obtained thread usage time is compared with the thread usage time threshold. If the thread usage time is greater than the thread usage time threshold, the target application is determined to be abnormal; the target application's resource occupancy rate is obtained, and the obtained resource occupancy rate is compared with the resource occupancy rate threshold. If the target application's resource occupancy rate is greater than the resource occupancy rate threshold, the target application is determined to be abnormal. Here, the target application's keyword path, etc. can also be specifically monitored based on the first alarm condition.
[0073] It is understandable that due to different application scenarios or usage properties of different target applications, when monitoring the target application, the monitored operation type and the corresponding first alarm condition may also be different.
[0074] Optionally, after determining that the target application is abnormal, first abnormal information of the target application is generated based on the acquired operation information corresponding to the target application operation type and the detected abnormal information. In this way, the first abnormal information when the target application is abnormal can be determined immediately, thereby improving the stability and performance of the application and reducing the risk of failure.
[0075] In one embodiment, determining the second abnormal information when the target monitoring rule is executed includes:
[0076] Obtaining second operation information corresponding to the target monitoring rule when it is running;
[0077] According to the second operation information and the preset second alarm condition, determining whether the operation state of the target monitoring rule is abnormal;
[0078] If so, the second abnormal information when the target monitoring rule is running is determined according to the judgment result and the second running information.
[0079] The second operation information includes memory usage, thread stack information, etc. The second alarm condition includes a memory usage threshold, a thread usage threshold, etc. corresponding to the second operation information.
[0080] In this way, the second operation information of the target monitoring rule is detected in real time during operation, and the second operation information is compared with the second alarm condition to determine whether the operation status of the target monitoring rule is abnormal, including: detecting whether the memory usage of the target monitoring rule exceeds the memory usage threshold; detecting whether the thread usage rate of the target monitoring rule exceeds the thread usage threshold, etc. In this way, if any of the above abnormal conditions is met, or if two or more abnormal conditions are met at the same time, it can be determined that the state of the target monitoring rule during operation is abnormal, and the second operation information and the corresponding abnormal information are output accordingly, which are determined as the second abnormal information of the target monitoring rule. In this way, by real-time monitoring of the operation status of the target monitoring rule, it is helpful to maintain the stability and reliability of monitoring the target application.
[0081] For example, when it is detected that the target monitoring rule is running, the number of threads with a memory usage greater than 200 is greater than 85%, and it is determined that the state of the current target monitoring rule is abnormal when it is running.
[0082] Step S103: output the first abnormal information and / or the second abnormal information.
[0083] Optionally, if the first abnormal information of the target application is determined, that is, the running state of the target application is determined to be abnormal, the first abnormal information is output. If the second abnormal information of the target monitoring rule is determined, that is, the running state of the target monitoring rule is abnormal, the second abnormal information is output accordingly.
[0084] Here, after determining the first exception information and / or the second exception information, the determined first exception information and / or the second exception information are immediately output to the server. It can be understood that when outputting the first exception information and / or the second exception information, any of the following situations can be included: only outputting the first exception information; only outputting the second exception information; outputting the first exception information and the second exception information separately; outputting the first exception information and the second exception information at the same time. At the same time, since there is more than one target application and more than one corresponding target monitoring rules are deployed, the output first exception information can be multiple first exception information corresponding to multiple target applications, and the output second exception information can also be multiple second exception information corresponding to multiple deployed target monitoring rules.
[0085] In one embodiment, the target monitoring rule includes a first alarm frequency, and / or a second alarm frequency;
[0086] Outputting the first abnormal information and / or the second abnormal information includes:
[0087] If the first abnormal information is determined, the first abnormal information is output based on the first alarm frequency; and / or,
[0088] If the second abnormal information is determined, the second abnormal information is output based on the second alarm frequency.
[0089] Optionally, if the first abnormal information is determined, the first abnormal information is output to the server based on the set first alarm frequency, for example, once every 5 minutes, until the state of the target application returns to normal and the alarm is eliminated. Similarly, if the second abnormal information is determined, the second abnormal information is output to the server based on the second alarm frequency until the running state of the target monitoring rule returns to normal and the alarm is eliminated. Here, the first alarm frequency and the second high frequency frequency can be consistent.
[0090] In summary, in the abnormal monitoring method provided in the above embodiment, the first abnormal information and / or the second abnormal information is determined according to the target detection rule, and an output reminder is performed, thereby realizing timely monitoring and active warning of the operation status of the target application and improving the user experience.
[0091] Based on the same inventive concept as the above embodiments, refer to Figure 2 The embodiment of the present invention provides an abnormal monitoring method, which is applied to a server and specifically includes the following steps:
[0092] Step S201, set a target monitoring rule corresponding to a target application, and send the target monitoring rule to a client; the target monitoring rule is used to monitor first abnormal information corresponding to a target application in the client, and second abnormal information of the operation of the target monitoring rule.
[0093] Here, when the target monitoring rules corresponding to the target application of the device are used, any of the following scenarios may be included: due to different application scenarios of each target application or different attribute configurations of each target application, target monitoring rules are set for each target application; based on the abnormal state of the target monitoring rule when it is running, the running program is adjusted accordingly and determined as the target monitoring rule; in response to user needs, the monitoring strategy for monitoring the target application is adjusted accordingly and determined as the target monitoring rule. In this way, the target monitoring rules of the target application are adjusted in real time, which can more flexibly respond to the ever-changing operating environment and potential risks.
[0094] Step S202: In response to receiving the first abnormal information and / or the second abnormal information, process the first abnormal information and / or the second abnormal information.
[0095] Optionally, when the first exception information and / or the second exception information is received, the first exception information and / or the second exception information and the corresponding target application are output and displayed through enterprise WeChat, DingTalk, email or SMS, etc. At the same time, the first exception information and / or the second exception information is stored in the log center.
[0096] In one implementation, processing the second abnormal information includes:
[0097] According to the second abnormal information, a request for obtaining an abnormal reason is sent to the client to obtain the abnormal reason for the abnormal operation status of the target monitoring rule;
[0098] Update the operating parameters of the target monitoring rule based on the cause of the exception.
[0099] Optionally, the macroscopic operating conditions such as the running state, thread and stack information of the target monitoring rule can be determined according to the second exception information, but the specific reason for the abnormality of the target monitoring rule cannot be determined specifically. For example, even if it is known that the memory usage rate of the JVM is very high at a certain moment, without further thread and stack information, it is impossible to determine which object or which code caused the memory leak. Therefore, it is necessary to further send an exception cause acquisition request to the client based on the first exception information to specifically determine the reason for the abnormality in the running state of the target monitoring rule, such as determining the function call sequence of the thread during the execution process, as well as local variables and other information through specific stack information. By viewing the thread and stack information, the execution process of the thread can be understood, and potential deadlocks, long-term blocking and other problems can be discovered.
[0100] In one embodiment, the method further comprises:
[0101] Detect the communication status with the client;
[0102] If the communication status is detected to be abnormal, a connection request is resent to the client to reconnect and communicate.
[0103] Optionally, the communication status between the server and the client is detected in real time. Once an abnormality is found in the connection, such as timeout, disconnection or connection quality degradation, network jitter or server restart, the communication status is determined to be abnormal, and a connection request is resent to the client to reconnect and communicate.
[0104] Based on the same inventive concept as the above-mentioned embodiment, the embodiment of the present invention provides an abnormal monitoring method, including a server (taking TracerServer as an example) and a client (taking TracerClient as an example), TracerServer includes a registration center, an early warning center, a rule center, a connection center, a monitoring center, and a log center. The specific interaction between TracerServer and TracerClient is as follows: Figure 3 As shown, including:
[0105] 1. After TracerServer is started, monitoring rules can be configured in the rule center, including indicators, thresholds, alarm methods, and post-rule matching processing events. After the rules are configured, they are persistently stored and submitted to the cache middleware.
[0106] 2. After TracerClient is started, it automatically registers with the registration center. After registration, TracerServer establishes a connection with TracerClient for communication. Here, TracerClient sends heartbeat information to TracerServer regularly, matches the configured target monitoring rules according to the application name to be monitored (i.e. the application name of the target application), and pulls the corresponding target monitoring rules.
[0107] 3. TracerClient enhances the bytecode and weaves the target monitoring rules into the JVM (i.e. the target monitoring rules) in the form of code to build and run the Agent (a program that monitors and tracks specific applications). In this way, the target application is monitored and tracked based on the target monitoring rules. At the same time, TracerClient can also obtain the JVM status information including CPU usage, thread stack information, garbage collection status, thread execution time, etc.
[0108] 4. TracerClient starts a thread in the JVM, loads and runs the Agent, and then returns the current JVM status information (including CPU usage, thread stack information, etc.) to the external thread, which then passes the status information back to TracerServer.
[0109] 5. TracerServer will eventually receive two parts of monitoring data reported by TracerClient, one is the monitoring data of the target application used by the agent in the JVM, and the other is the running status information of the JVM itself. TracerServer can automatically notify the enterprise WeChat, DingTalk, email or SMS through the early warning center according to the configured thresholds and alarm methods. At the same time, the log information is stored in the log center.
[0110] 6. When the JVM's own running status is abnormal, you can view the relevant information in the JVM through the connection, quickly locate the problem, and quickly fix the bug through the code hot update capability.
[0111] 7. When you need to add monitoring strategies or adjust monitoring parameters, you only need to modify the relevant configuration in the rule center, and TracerClient will automatically pull and update it without restarting the application.
[0112] Here, the connection center can view the registration information of each application and the reporting status of monitoring data. If there is an abnormality, it can automatically notify you to reconnect.
[0113] Based on the same inventive concept as the above embodiments, an embodiment of the present invention provides a computing device, such as Figure 4 As shown, the computing device includes: a processor 310 and a memory 311 storing a computer program; wherein, Figure 4 The processor 310 shown in the figure is not used to indicate that the number of the processor 310 is one, but is only used to indicate the positional relationship of the processor 310 relative to other devices. In actual applications, the number of the processor 310 may be one or more; similarly, Figure 4 The memory 311 shown in the figure has the same meaning, that is, it is only used to refer to the position relationship of the memory 311 relative to other devices. In practical applications, the number of memories 311 can be one or more. When the processor 310 runs the computer program, the above-mentioned abnormality monitoring method is implemented.
[0114] The computing device may also include: at least one network interface 312. The various components in the computing device are coupled together via a bus system 313. It is understood that the bus system 313 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 313 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, the bus system 313 is not used in the example above. Figure 4 Various buses are labeled as bus system 313.
[0115] The memory 311 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. The nonvolatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 311 described in the embodiments of the present invention is intended to include but is not limited to these and any other suitable types of memories.
[0116] The memory 311 in the embodiment of the present invention is used to store various types of data to support the operation of the computing device. Examples of these data include: any computer program used to operate on the computing device, such as an operating system and an application; contact data; phone book data; messages; pictures; videos, etc. Among them, the operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application program may include various applications, such as a media player, a browser, etc., which are used to implement various application services. Here, the program that implements the method of the embodiment of the present invention may be included in the application program.
[0117] Based on the same inventive concept as the above-mentioned embodiment, this embodiment further provides a computer-readable storage medium, in which a computer program is stored. The computer-readable storage medium may be a ferromagnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); it may also be various devices including one or any combination of the above memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc. When the computer program stored in the computer-readable storage medium is executed by the processor, the abnormality monitoring method applied to the above-mentioned computing device is implemented. For the specific steps implemented when the computer program is executed by the processor, please refer to Figure 1 or Figure 2 The description of the illustrated embodiment will not be repeated here.
[0118] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0119] In this document, the terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion of elements other than those listed and may also include additional elements not expressly listed.
[0120] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
Claims
1. An abnormality monitoring method, applied to a client, characterized in that: include: Obtaining target monitoring rules corresponding to a target application, and deploying the target monitoring rules in the target application; Determining first abnormal information of the target application according to the target monitoring rule; and / or, determining second abnormal information when the target monitoring rule is executed; The first abnormality information and / or the second abnormality information is output.
2. The method according to claim 1, characterized in that The acquiring target monitoring rules corresponding to the target application and deploying the target monitoring rules in the target application includes: Based on a preset time interval, obtaining a target monitoring rule corresponding to the target application; If the target application does not have an initial monitoring rule, deploying the target monitoring rule into the target application; If the target application is provided with an initial monitoring rule, the initial monitoring rule is updated according to the target monitoring rule.
3. The method according to claim 1, characterized in that The target monitoring rule includes the operation type to be monitored and the first alarm condition, The determining, according to the target monitoring rule, first abnormal information of the target application includes: Acquire first operation information corresponding to each operation type in the target application; Determining whether the target application is abnormal according to the first operation information and the first alarm condition; If so, the first abnormal information of the target application is determined according to the judgment result and the operation information.
4. The method according to claim 1, characterized in that: The target monitoring rule package provides a second alarm condition; The determining of the second abnormal information when the target monitoring rule is executed includes: Acquire second operation information corresponding to the target monitoring rule when it is running; Determining whether the operating state of the target monitoring rule is abnormal according to the second operating information and the second alarm condition; If so, the second abnormal information when the target monitoring rule is running is determined according to the judgment result and the second running information.
5. The method according to claim 1, characterized in that The target monitoring rule includes a first alarm frequency and / or a second alarm frequency; The outputting the first abnormality information and / or the second abnormality information includes: If the first abnormal information is determined, outputting the first abnormal information based on the first alarm frequency; and / or, If the second abnormal information is determined, the second abnormal information is output based on the second alarm frequency.
6. An abnormality monitoring method, applied to a server, characterized in that: include: Setting a target monitoring rule corresponding to the target application, and sending the target monitoring rule to the client; the target monitoring rule is used to monitor the first abnormal information corresponding to the target application in the client, and the second abnormal information of the operation of the target monitoring rule; In response to receiving the first exception information and / or the second exception information, the first exception information and / or the second exception information are processed.
7. The method according to claim 6, characterized in that The processing of the second abnormal information includes: According to the second abnormal information, sending an abnormal reason acquisition request to the client to obtain the abnormal reason for the abnormality of the running state of the target monitoring rule; The operating parameters of the target monitoring rule are updated according to the abnormal cause.
8. The method according to claim 6, characterized in that The method further comprises: Detect the communication status with the client; If the communication state is detected to be abnormal, a connection request is resent to the client to reconnect for communication.
9. A computing device, characterized in that include: A processor and a memory for storing executable instructions; wherein the processor is configured to execute the instructions to implement the abnormality monitoring method according to any one of claims 1-8.
10. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the abnormality monitoring method according to any one of claims 1 to 8 is implemented.