Error report event processing method and device

Abstract

The invention discloses an error reporting event processing method and device, and relates to the technical field of computers. The method comprises the steps of determining a to-be-processed target event in error reporting events based on event attribute information; wherein the event attribute information is set by a user; determining whether the target event needs to be processed or not based on event triggering parameters of the target event, wherein the triggering parameters are used for representing the triggered degree of the target event; if it is determined that the target event needs to be processed, the processing operation is executed on the target event, and the processing operation comprises pausing a behavior corresponding to the target event. The method and the device are used for realizing an error event processing function.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method and device for processing an error event. Background Art

[0002] In a computer system, its operation generally relies on basic services or third-party services. However, in actual use, there may be abnormal situations such as errors due to network and firmware compatibility reasons.

[0003] At present, in the process of handling error events, various error events in the system are generally monitored and handled manually. However, in actual applications, the manual method relies too much on the experience of the monitoring personnel. This leads to the situation that once the monitoring personnel are negligent or lack experience, some error events may be triggered but not handled in time even though the situation requires handling, thus affecting the timeliness of the error event handling process. Summary of the invention

[0004] The embodiments of the present application provide a method and device for processing an error event, the main purpose of which is to solve the problem of poor timeliness in the current processing of error events.

[0005] In order to solve the above technical problems, the embodiments of the present application provide the following technical solutions:

[0006] In a first aspect, the present application provides a method for processing an error event, the method comprising:

[0007] Based on the event attribute information, determine the target event to be processed in the error event;

[0008] Determining whether the target event needs to perform a processing operation based on an event trigger parameter of the target event, wherein the trigger parameter is used to characterize the degree to which the target event is triggered;

[0009] If it is determined that processing is required, the processing operation is performed on the target event, and the processing operation includes pausing the execution logic corresponding to the target event.

[0010] In a second aspect, the present application further provides a device for processing an error event, comprising:

[0011] A first determining unit, configured to determine a target event to be processed in the error reporting event based on the event attribute information;

[0012] A second determining unit, configured to determine whether the target event needs to perform a processing operation based on an event trigger parameter of the target event, wherein the trigger parameter is used to characterize the degree to which the target event is triggered;

[0013] The execution unit is used to execute the processing operation on the target event if it is determined that processing is required, and the processing operation includes pausing the execution logic corresponding to the target event.

[0014] In a third aspect, an embodiment of the present application provides a storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the error event processing method described in any one of the first aspects.

[0015] In a fourth aspect, an embodiment of the present application provides a device for processing an error event, the device comprising a storage medium; and one or more processors, the storage medium being coupled to the processor, the processor being configured to execute program instructions stored in the storage medium; when the program instructions are executed, the method for processing an error event described in any one of the first aspects is executed.

[0016] By means of the above technical solution, the technical solution provided by this application has at least the following advantages:

[0017] The present application provides a method and device for processing an error event. The present application can first determine the target event to be processed in the error event based on the event attribute information; then, determine whether the target event needs to perform a processing operation based on the event trigger parameter of the target event, and the trigger parameter is used to characterize the degree to which the target event is triggered; finally, if it is determined that processing is required, the processing operation is performed on the target event, and the processing operation includes pausing the execution logic corresponding to the target event, thereby realizing the processing function of the error event. Compared with the prior art, in the present application, since the processing of the error event no longer relies on manual monitoring, it can be automatically monitored and processed based on the event attribute information set by the user. In this process, it is based on the trigger parameter characterizing the degree to which the target event is triggered. In this way, as long as the trigger degree of the target event is relatively frequent, it will be automatically processed according to the method of the present application, which avoids the problem that it is difficult to timely process certain target events that need to be processed due to negligence or lack of experience in the manual monitoring process, ensures the timeliness of the processing of the error event, and solves the problem of poor timeliness in the prior art when processing the error event.

[0018] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] By reading the detailed description below with reference to the accompanying drawings, the above and other purposes, features and advantages of the exemplary embodiments of the present application will become easy to understand. In the accompanying drawings, several embodiments of the present application are shown in an exemplary and non-limiting manner, and the same or corresponding reference numerals represent the same or corresponding parts, wherein:

[0020] Figure 1 A flow chart of a method for processing an error event provided by an embodiment of the present application is shown;

[0021] Figure 2 A flowchart of another method for processing an error event provided by an embodiment of the present application is shown;

[0022] Figure 3 A block diagram of a device for processing an error event provided by an embodiment of the present application is shown;

[0023] Figure 4 A block diagram showing the composition of another device for processing error events provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0024] The exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0025] It should be noted that, unless otherwise specified, the technical terms or scientific terms used in this application should have the common meanings understood by technicians in the field to which this application belongs.

[0026] The present application embodiment provides a method for processing an error event, which is applied to an electronic device. Figure 1 As shown, the method includes 101-103.

[0027] 101. Based on the event attribute information, determine the target event to be processed in the error reporting event.

[0028] In this embodiment, the error event can be understood as the error information recorded in the system log. Since the causes of the error events contained in the system log are different, the threat levels to the computer system are also different, so the attribute information corresponding to different error events is also different. Specifically, in this step, when the user needs to determine which errors need to be processed, it can be set through instructions, that is, event attribute information. After the user has set the event attribute information, the method of this step can be used to match and identify multiple different error events based on the event attribute information, so as to determine the error event corresponding to the event attribute information as the target event to be processed.

[0029] It should be noted that the method of setting the event attribute information by the user in this embodiment and the content and quantity of the event attribute information are not limited here, and the user can select based on the actual situation. For example, the process of setting the time attribute information by the user can be based on a preset interactive interface, by clicking different options in the interface, each option can involve an attribute of the error event, such as trigger period, trigger position, duration, error port, etc. The user can select based on the parameters set under each attribute, thus realizing the process of the user setting the event attribute information.

[0030] For example, when the user selects port 11 under the error port in the preset interactive interface, the event attribute information set by the user is "port 11". In this way, when determining the target event to be processed among multiple error events, analysis is performed based on the port. As long as the error event is generated at port 11, the error event is the target event that the user wants to process.

[0031] In addition, the carrier of the method described in this embodiment may be a device deployed in any type of computer system. Of course, if the computer system is specifically a distributed system, then the device may be deployed in an electronic device where any node in the distributed system is located.

[0032] 102. Determine whether the target event needs to perform a processing operation based on an event trigger parameter of the target event.

[0033] The trigger parameter is used to characterize the degree to which the target event is triggered.

[0034] When the target event has been determined in the above steps, the method of this step can be used to determine whether the target event needs to be processed. In one example, the event trigger parameter can be used to determine whether the target event needs to be processed. The event trigger parameter can be understood as a kind of information that can reflect the degree to which the target event is triggered. If the triggering degree is relatively frequent, it means that the target event is always triggered, which is likely to affect the normal operation of the computer system, so the target event needs to be processed. On the contrary, if the triggering program is not frequent, it means that the target event is not always triggered, so its impact on the normal operation of the computer system may be small, or the user believes that this degree of impact is not harmful to the computer system, so there is no need to process it. Of course, in this embodiment, the specific forms of the event trigger parameter include but are not limited to the following, such as trigger frequency, trigger duration, trigger number and trigger interval, etc., which are not limited here and can be selected based on actual needs.

[0035] 103. If it is determined that processing is required, the processing operation is performed on the target event.

[0036] The processing operation includes pausing the execution logic corresponding to the target event.

[0037] Based on the description of the above steps, when it is determined that the target event needs to be processed, it means that the target event has a great impact on the normal operation of the computer system, and it needs to be processed in time to avoid subsequent impacts. Since the target event is an error event, its representation means that a certain behavior in the system is abnormal. In an example, the processing operation in this step is actually to suspend the execution logic of the target event, which fundamentally solves the cause of the error, thereby avoiding the target event from being triggered again, and ensuring that the computer system will not generate an error event due to the behavior, so that the system can operate normally.

[0038] The present embodiment provides a method for processing error events. Compared with the prior art, in the embodiment of the present application, since the processing of error events no longer relies on manual monitoring, but can be automatically monitored and processed based on event attribute information set by the user, this process is based on trigger parameters that characterize the degree to which the target event is triggered. When it is determined based on the trigger parameters that the trigger degree of the target event is relatively frequent, it will be automatically processed according to the method of the present application. This avoids the problem of difficulty in timely processing certain target events that need to be processed due to negligence or lack of experience during manual monitoring, ensures the timeliness of the processing of error events, and solves the problem of poor timeliness in the prior art when processing error events.

[0039] To explain in more detail below, the present application embodiment provides another method for processing an error event, which is applied to an electronic device. Figure 2 As shown, the method includes 201-205.

[0040] 201. Based on the event attribute information, determine a target event to be processed in the error reporting event.

[0041] The event attribute information is set by the user.

[0042] In this embodiment, the event attribute information includes at least the error type and error identifier of the target event, and the error identifier is used to distinguish different subtypes under the error type.

[0043] Since there are many types of error events, in order to facilitate the distinction, in this embodiment, a two-level division method is specifically adopted, that is, the type and sub-type are divided, that is, the error type is divided as a "major category", and the error identification is divided as a "sub-category". Then the user also needs to set it in this way during the process of setting the event attribute information, that is, after setting the error type, it is also necessary to set the error identification corresponding to the error type. Specifically, the specific method of the event attribute information can be set in a key-value pair manner, such as "xy", where x represents the error type and y represents the error identification. Here, the setting method for the event attribute information includes but is not limited to the above-mentioned method, and the user can select it based on the needs. It should be noted that in some embodiments, the division of the error type can be but is not limited to the above-mentioned two-level division, and can also be divided into a multi-level division method, for example, it can be divided based on the structural hierarchy of the system deployed in this embodiment. For example, when the error type corresponding to the error that occurs is "hardware-communication class-interactive interface-first class interface", it means that there is an XX error in the first class interface of the interactive interface of the communication class hardware of the hardware part.

[0044] 202. Determine whether there is a matching event record table in the multiple event record tables stored in the internal cache according to the error type and the error identifier.

[0045] Each event record table stored in the internal cache is marked with a corresponding error type and error identifier.

[0046] In this embodiment, the error events are stored in the form of an event record table, such as ConcurrentHashMap, which is a hash table that supports high-concurrency updates and queries and can record event triggering conditions in any computer system including distributed systems. Since the error events are recorded in the form of an event record table, when determining the triggering condition of the target event, it is also necessary to query in a table manner.

[0047] In addition, in the present embodiment, each time record table is marked with the error identification and error type of the corresponding error event. In this way, when determining the situation in which the target event is triggered, it is possible to query whether there is a matching event record table based on the error type and error identification of the target event determined in the aforementioned steps. If there is a matching event record table, it means that the event record table records the situation in which the target event is triggered. Conversely, if there is no matching event record table, it means that the target event has not been recorded before, that is, it has not been triggered.

[0048] Based on the judgment result, when it is determined that there is no matching event record table, step 203A may be executed; otherwise, when it is determined that there is a matching event record table, step 203B may be executed.

[0049] 203A. If there is no matching event record table, then a new event record table corresponding to the error type and the error identifier is added to the internal cache, and the newly added event record table is a target event record table of the target event.

[0050] When it is determined that there is no matching event record table, it means that the target event has not been triggered before, so the table of the target event has not been recorded. Therefore, it is necessary to add a table corresponding to the target event in the internal cache, that is, the target event record table, so as to facilitate subsequent recording when the target event is triggered.

[0051] 203B: If a matching event record table exists, determine that a target event record table of the target event exists in the internal cache.

[0052] When it is determined that there is a matching event record table, it means that the target event has been triggered before and recorded in the internal cache. Then the table that matches the error type and error identifier of the target event is the target event record table. Then after this step 203B, it is necessary to continue to execute step 204 for subsequent judgment.

[0053] 204. When it is determined that a target event record table of the target event exists in the internal cache, determine the trigger quantity corresponding to the target event in the trigger period based on the target event record table, and determine whether the trigger quantity exceeds a first threshold.

[0054] The target event record table is used to record the process of triggering the target event.

[0055] In some embodiments, the event triggering parameters characterizing the degree to which the target event is triggered can be determined based on a triggering period and the number of times the period is triggered. In some specific embodiments, the event triggering parameters can specifically include a triggering period and a corresponding number of triggers.

[0056] Based on this, determining whether the target event needs to perform a processing operation based on the event triggering parameters of the target event can be performed according to step 204 during the specific execution process.

[0057] When it is determined that there is a target event record table in the internal cache, it means that the target event has been triggered and recorded. Then, when determining its triggering situation, it is necessary to judge based on the number of triggers in a certain period of time. The period can be set based on user needs, that is, the trigger period, such as 1 minute before the current moment, or 24 hours on the same day, etc. There is no limit on the length of the trigger period, and the user can select it based on actual needs. After determining the number of triggers corresponding to the trigger period, it can be determined based on the first threshold whether the target event needs to be processed, that is, by determining whether the number of triggers exceeds the first threshold to judge the frequency of the target event triggering. If it exceeds, it means that it is often triggered, otherwise it means that it is not often triggered.

[0058] In some cases, the triggering conditions recorded in the target event record table are recorded separately according to time periods. In this case, the target event record table records the triggering records of the target event in different time periods.

[0059] Thus, in this step, the trigger quantity corresponding to the target event in the trigger period is determined based on the target event record table, and it is determined whether the trigger quantity exceeds the first threshold. In the judgment process, it is also necessary to consider whether there is a trigger record corresponding to the trigger period.

[0060] Based on this, when executing this step, the judgment can be made according to the following process S1-S3:

[0061] S1. Determine in the target event record table whether there is a trigger record corresponding to the trigger period.

[0062] S2. If so, count the number of triggers based on the trigger records corresponding to the trigger period, and determine whether the number of triggers exceeds a first threshold.

[0063] S3. If it is determined that there is no trigger record corresponding to the trigger period, a trigger record corresponding to the trigger period is added.

[0064] When it is determined that there is a trigger record for the trigger period, it means that the target event has been triggered in this period, and then the trigger count can be calculated based on the trigger record of the period. Otherwise, it means that the target event has not been triggered in the trigger period, and then a trigger record corresponding to the period needs to be added so that the trigger count can be calculated based on the trigger record when the target event is subsequently triggered. This avoids the problem of missing the target event after it is triggered when the internal cache does not record the trigger record of the trigger period.

[0065] Furthermore, in some cases, the user may also need to know the triggering situation of the target event in the previous period of time. In this regard, the triggering situation can be divided into two aspects. One is the trend change of the triggering of the target event, and the other is whether a large number of target events have been triggered before the triggering period. Based on this, after the above steps S1-S3, the method of this embodiment may also include:

[0066] S4. Based on the trigger records, count the historical trigger quantity of the target event in each time period before the trigger period, and determine the trigger change trend of the target event based on the historical trigger quantity; the trigger change trend includes any one of increase, decrease and stability.

[0067] S5. When it is determined that there is a number of historical triggers exceeding the first threshold, generate an abnormal history record based on the number of historical triggers exceeding the first threshold and the corresponding time period, and issue an alarm based on the trigger change trend and the historical abnormal record.

[0068] Through step S4, the triggering situation of the target event in each period before the triggering period can be counted to obtain the historical triggering number, and based on the historical triggering numbers corresponding to multiple periods, the previous triggering situation of the target event can be obtained, that is, the triggering change trend. Through the triggering change trend, the user can know the overall change of the triggering of the target event, which is conducive to the subsequent investigation and cause analysis. And in step S5, by determining the number of historical triggers that exceed the first threshold and recording the corresponding period, the user can know whether there have been a large number of target event triggers before the triggering period set by the user, so that the user can know the earliest period of the problem during the subsequent investigation and attribution, which is conducive to quickly determining the cause of the problem and improving the efficiency of subsequent maintenance.

[0069] Furthermore, after step S5, a related alarm operation may be further performed based on the trigger change trend, so as to inform the target personnel of the occurrence of the current error event. Based on this, this step may also include:

[0070] If the trigger change trend is decreasing, an alarm is issued through a first alarm operation; the first alarm operation is used to issue an alarm through a system built-in information channel;

[0071] If the trigger change trend is stable, an alarm is issued through a second alarm operation; the second alarm operation is used to use a system external information channel through a preset interactive interface to alarm the target person, and the system external information channel includes at least any one or more combinations of emails, text messages and phone calls;

[0072] If the trigger change trend is increasing, the second alarm operation is continuously performed according to a preset period and stopped after receiving feedback from the target person.

[0073] In this way, when the trigger change trend is decreasing, issuing an alarm through the system's built-in information channel can ensure that the target personnel can be informed of the current error event based on the system's built-in information channel, and can ensure that the user can promptly be informed of the triggering situation of the current error event. The system's built-in information channel includes but is not limited to the internal communication channel of the server deployed by the method described in this embodiment, or the internal communication software of the company where the target personnel is located, etc., which is not limited here and can be selected based on actual needs.

[0074] When the trigger change trend is stable, it means that the error event is continuously occurring. Then, the second alarm operation is used to issue an alarm using any method or combination of email, text message, phone call, etc. This can ensure that when the target personnel is not at their workstations, they can also be informed of the current error event through the system's external information channel. This is beneficial in certain special cases, so that the target personnel can also be informed of the error event and can intervene in it in a timely manner.

[0075] When the trigger change trend is increasing, it means that the error event corresponding to the alarm not only exists, but also has a tendency to intensify. At this time, the second alarm operation can be continuously executed in a periodic manner, and the target person can be continuously alarmed by email, text message and / or phone. The alarm will not be stopped until the feedback from the target person is received. This can ensure that the alarm can be known to the target person in time. Even if the target person fails to notice the alarm in time for a certain time, he can be prompted through subsequent continuous alarms, thereby avoiding the situation where the target person misses the alarm, which is conducive to the timely intervention of subsequent error events.

[0076] Furthermore, in some cases, in order to relieve the pressure of the memory cache, only a part of the trigger quantity is recorded in the memory cache, and when the internal cache records a certain number, it will be handed over to the external cache to record the rest. In this case, the trigger quantity may include a first quantity and a second quantity; wherein the first quantity is the number of target events triggered in the target event record table in the internal cache during the trigger period, and the second quantity is the number of target events triggered in the external cache during the trigger period.

[0077] Based on this, before determining whether the trigger quantity exceeds the first threshold, the method further includes: A1-A3.

[0078] A1. Determine whether the first number exceeds a second threshold.

[0079] The second threshold is smaller than the first threshold.

[0080] A2. When it is determined that the first quantity exceeds the second threshold and it is determined that the target event has been recorded in the target event record table in the external cache, the second quantity is obtained, and a trigger quantity is determined based on the first quantity and the second quantity.

[0081] A3. Reset the first number of the target events in the internal cache during the trigger period to zero.

[0082] In this embodiment, the triggering of the target event is recorded by the internal cache and the external cache respectively. After recording a certain number of triggering information, the internal cache is handed over to the external cache for recording. The external cache can be specifically a cluster cache, that is, a Redis cache, wherein Redis (Remote Dictionary Server), that is, a remote dictionary service, is a remote service dedicated to providing external dedicated caches such as distributed systems. In this way, when determining whether the number of triggers exceeds the first threshold in this step, it is first necessary to determine whether the number recorded by the current internal cache exceeds the threshold value, that is, the second threshold, based on step A1. It should be noted that in a preferred manner, the second threshold is not only less than the first threshold, but also set according to a certain proportion of the first threshold, such as 1 / 100, 10 / 100, 50 / 100 of the first threshold. The proportion is set according to actual needs and is not limited here. This shows that in the process of recording the target event, if the number of recorded triggers reaches 1 / 100 of the first threshold, the subsequent recording is performed by the external cache. For this reason, when step A2 determines that the first number exceeds the second threshold, it means that the number of the current target event triggered has exceeded the threshold value of the internal cache record, then it is very likely that the corresponding trigger number (second number) is also recorded in the external cache, so it is necessary to count the sum of the first number and the second number as the trigger number, and use this to determine whether it exceeds the first threshold, which avoids the problem of missing the second number recorded in the external cache and causing inaccurate judgment results. At the same time, after determining the trigger number based on the first number and the second number, the first number of the internal cache can also be reset to zero, which avoids the problem of repeated judgments leading to subsequent redundant processing operations.

[0083] In addition, in some cases, the number of triggers recorded in the internal cache may just reach the second threshold, but no further triggering occurs. In this case, the target event record table of the target event may not be recorded in the external cache. Based on this, after step A1, the method further includes:

[0084] A4. When it is determined that the first number exceeds the second threshold value, and it is determined that the target event is not recorded in the target event record table in the external cache, a target event record table of the target event is added to the external cache. The target event record table of the external cache is used to record when the target event is triggered again during the trigger period.

[0085] Since the target event record table is not recorded in the external cache, it means that the number of target events triggered previously has reached the threshold value of the internal cache (the second threshold value). In order to avoid the problem of omissions caused by subsequent re-triggering of the target event, in this embodiment, the newly added target event record table can be found in the external cache based on step A4. In this way, if the target event is triggered again subsequently, it can be recorded based on the target event record table of the external cache, thereby avoiding subsequent omissions of records and affecting the final timely execution of processing operations.

[0086] 205. If it is determined that the first threshold is exceeded, perform the processing operation on the target event.

[0087] Based on the above step description, it can be known that in this embodiment, the trigger time period and the corresponding trigger quantity are used as the basis to judge whether the target event needs to be processed. If it is determined that it needs to be processed, the processing operation is performed on the target event, and the execution can be specifically performed as in step 205.

[0088] Specifically, in this step, performing the processing operation on the target event includes:

[0089] Generate a to-be-processed task based on the target event, and send the to-be-processed task to a task processing queue, wherein the to-be-processed task is marked with task information, and the task information is determined based on event attribute information of the target event;

[0090] Based on the task processing queue, a corresponding processing operation is selected for the to-be-processed task according to the task information, wherein each type of task information corresponds to a processing operation, and the processing operation also includes a custom operation set based on processing requirements.

[0091] When it is determined that the number of triggers exceeds the first threshold, it means that the number of target events triggered as a whole has exceeded the warning value, which means that the trigger frequency of the target event is too high and may affect the system. At this time, it is necessary to generate the corresponding pending task based on the method of this step and send it to the task processing queue. The pending task in the queue marks the characteristics of the task, that is, the task information, and the task information is determined based on the event attribute information, so it can reflect the error type and error identification actually involved in the pending task, so as to facilitate the subsequent selection of the appropriate processing method based on its error type and error identification. For example, the task information can be "target event A, error type (XY), processing method: abort, trigger time 20240815". Of course, in actual applications, the task information can also add other relevant information of the target event, which is not limited here, but ensure that the task information contains the content involved in the event attribute information, so that it is conducive to the subsequent analysis of the relevant personnel to understand the type of problem corresponding to each target event based on the task information.

[0092] Of course, the processing operation of the present embodiment can be to suspend the behavior corresponding to the target event, so that the behavior of triggering the target event is interrupted, and the error will not be triggered again, and the normal operation of the system will not be affected. At the same time, the processing operation of the present embodiment also includes a user-defined operation set on this basis, that is to say, not only can the behavior of the target event be suspended, but also other operation behaviors can be performed based on the custom operation, which is conducive to more flexible processing based on user needs when processing the target event. In addition, in the present embodiment, the custom operation is actually an operation set by the user based on needs, which can be other operations performed on the basis of suspending or suspending the execution logic corresponding to the target event, such as giving an alarm, or generating a processing log. Of course, it can also be a further control of suspending or suspending behavior, such as suspending the execution logic of the target event-pause time 1 hour. The operation content specifically involved in the custom operation is not specifically limited here, and can be set based on the actual needs of the user.

[0093] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an embodiment of the present application further provides a storage medium, wherein the storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the above-mentioned error event processing method.

[0094] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an embodiment of the present application also provides a device for processing error events, the device comprising a storage medium; and one or more processors, the storage medium is coupled to the processor, and the processor is configured to execute program instructions stored in the storage medium; when the program instructions are run, the above-mentioned method for processing error events is executed.

[0095] Furthermore, as a response to the above Figure 1 and Figure 2 In order to realize the method shown in the figure, another embodiment of the present application also provides a device for processing an error event. The embodiment of the device for processing an error event corresponds to the aforementioned method embodiment. For ease of reading, the embodiment of the device for processing an error event will no longer repeat the details of the aforementioned method embodiment one by one, but it should be clear that the device in this embodiment can correspond to all the contents of the aforementioned method embodiment. The main purpose of the device for processing an error event is to solve the problem of poor timeliness in the current error event processing process, specifically as follows Figure 3 As shown, the error event processing device includes:

[0096] The first determining unit 31 may be used to determine a target event to be processed in the error reporting event based on the event attribute information;

[0097] The second determining unit 32 may be used to determine whether the target event needs to perform a processing operation based on the event triggering parameter of the target event determined by the first determining unit 31, wherein the triggering parameter may be used to characterize the degree to which the target event is triggered;

[0098] The execution unit 33 may be configured to execute the processing operation on the target event if the second determination unit 32 determines that processing is required, wherein the processing operation includes pausing the behavior corresponding to the target event.

[0099] Further, such as Figure 4 As shown, the event trigger parameters specifically include a trigger period and a corresponding trigger quantity;

[0100] The second determining unit 32 may also be configured to determine the trigger quantity corresponding to the target event in the trigger period based on the target event record table when it is determined that the target event record table exists in the internal cache, and determine whether the trigger quantity exceeds a first threshold; wherein the target event record table may be used to record the process in which the target event is triggered;

[0101] The execution unit 33 may also be configured to execute the processing operation on the target event if the second determination unit 32 determines that the first threshold is exceeded.

[0102] Further, such as Figure 4 As shown, the event attribute information includes at least the error type and error identifier of the target event, and the error identifier can be used to distinguish different subtypes under the same error type;

[0103] The device also includes:

[0104] The third determining unit 34 may be used to determine whether there is a matching event record table among the multiple event record tables stored in the internal cache, based on the error type and the error identifier determined by the first determining unit 31; wherein each event record table stored in the internal cache is marked with a corresponding error type and error identifier;

[0105] The fourth determining unit 35 may be configured to determine that a target event record table of the target event exists in the internal cache if the third determining unit 34 determines that a matching event record table exists;

[0106] The first adding unit 36 ​​can be used to add an event record table corresponding to the error type and the error identifier in the internal cache if the third determining unit 34 determines that there is no matching event record table, and the newly added event record table is the target event record table of the target event.

[0107] Further, such as Figure 4 As shown, the target event record table records the triggering records of the target event in different time periods;

[0108] The second determination unit 32 can also be used to determine whether there is a trigger record corresponding to the trigger time period in the target event record table; and, if so, count the number of triggers based on the trigger records corresponding to the trigger time period, and determine whether the number of triggers exceeds a first threshold.

[0109] Further, such as Figure 4 As shown, the device also includes:

[0110] The second adding unit 37 may be configured to add a trigger record corresponding to the trigger period if the second determining unit 32 determines that there is no trigger record corresponding to the trigger period.

[0111] Further, such as Figure 4 As shown, the trigger quantity includes a first quantity and a second quantity; the first quantity is the quantity of the target events in the target event record table in the internal cache that are triggered during the trigger period; the second quantity is the quantity of the target events recorded in the external cache that are triggered during the trigger period;

[0112] The device also includes:

[0113] The fifth determination unit 38 can be used to determine whether the first quantity exceeds a second threshold, wherein the second threshold is less than the first threshold; the first quantity is the number of target events in the target event record table in the internal cache that are triggered during the trigger period; and, when it is determined that the first quantity exceeds the second threshold and it is determined that the target event has been recorded in the target event record table in the external cache, the second quantity is obtained, and the trigger quantity is determined based on the first quantity and the second quantity; and, the trigger quantity of the target event in the internal cache during the trigger period is reset to zero.

[0114] Further, such as Figure 4 As shown, the device also includes:

[0115] The third adding unit 39 can be used to add a target event record table of the target event in the external cache when the fifth determining unit 38 determines that the first number exceeds the second threshold and determines that the target event is not recorded in the target event record table in the external cache. The target event record table of the external cache is used to record when the target event is triggered again during the trigger period.

[0116] Further, such as Figure 4 As shown, the execution unit 33 can also be specifically used to generate a task to be processed based on the target event, and send the task to be processed to a task processing queue, wherein task information is marked in the task to be processed, and the task information is determined based on the event attribute information of the target event; and, based on the task processing queue, a corresponding processing operation is selected for the task to be processed according to the task information, wherein each type of task information corresponds to a processing operation, and the processing operation also includes a custom operation that can be set based on processing requirements.

[0117] Further, such as Figure 4 As shown, the device also includes:

[0118] The trend determination unit 40 may be used to count the number of historical triggers of the target event in each period before the trigger period based on the trigger record determined by the second unit 32, and determine the trigger change trend of the target event based on the number of historical triggers; the trigger change trend includes any one of increasing, decreasing and stable;

[0119] The alarm unit 41 can be used to generate an abnormal history record based on the historical trigger number exceeding the first threshold and the corresponding time period when it is determined that there is a historical trigger number exceeding the first threshold, and to issue an alarm based on the trigger change trend obtained by the trend determination unit 40 and the historical abnormal record.

[0120] The embodiment of the present application provides a method and device for processing error events. Compared with the prior art, in the embodiment of the present application, since the processing of error events no longer relies on manual monitoring, but can be automatically monitored and processed based on event attribute information set by the user, this process is based on trigger parameters that characterize the degree to which the target event is triggered. In this way, as long as the degree of triggering of the target event is relatively frequent, it will be automatically processed according to the method of the present application. This avoids the problem of difficulty in timely processing certain target events that need to be processed due to negligence or lack of experience during manual monitoring, ensures the timeliness of the processing of error events, and solves the problem of poor timeliness in the prior art when processing error events.

[0121] An embodiment of the present application provides a storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the above-mentioned method for processing the error event.

[0122] The storage medium may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM, and the memory includes at least one storage chip.

[0123] An embodiment of the present application also provides a device for processing an error event, the device comprising a storage medium; and one or more processors, the storage medium is coupled to the processor, and the processor is configured to execute program instructions stored in the storage medium; when the program instructions are executed, the above-mentioned method for processing the error event is executed.

[0124] An embodiment of the present application provides a device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented: based on event attribute information, determining a target event to be processed in an error event; wherein the event attribute information is set by a user; determining whether a processing operation needs to be performed on the target event based on an event trigger parameter of the target event, wherein the trigger parameter is used to characterize the degree to which the target event is triggered; if it is determined that processing is required, performing the processing operation on the target event, wherein the processing operation includes pausing the behavior corresponding to the target event.

[0125] Furthermore, the event trigger parameters specifically include a trigger period and a corresponding trigger quantity;

[0126] The determining whether the target event needs to perform a processing operation based on the event trigger parameter of the target event includes:

[0127] When it is determined that there is a target event record table of the target event in the internal cache, determining the trigger quantity corresponding to the target event in the trigger period based on the target event record table, and determining whether the trigger quantity exceeds a first threshold; wherein the target event record table is used to record the process of the target event being triggered;

[0128] If it is determined that processing is required, performing the processing operation on the target event includes:

[0129] If it is determined that the first threshold is exceeded, the processing operation is performed on the target event.

[0130] Furthermore, the event attribute information includes at least an error type and an error identifier of the target event, and the error identifier is used to distinguish different subtypes under the error type;

[0131] When it is determined that the target event record table of the target event exists in the internal cache, before determining the trigger quantity corresponding to the target event in the trigger period based on the target event record table, the method further includes:

[0132] In the multiple event record tables stored in the internal cache, determining whether there is a matching event record table according to the error type and the error identifier; wherein each event record table stored in the internal cache is marked with a corresponding error type and error identifier;

[0133] If there is a matching event record table, determining that a target event record table of the target event exists in the internal cache;

[0134] If there is no matching event record table, then a new event record table corresponding to the error type and the error identifier is added to the internal cache, and the newly added event record table is the target event record table of the target event.

[0135] Furthermore, the target event record table records the triggering records of the target event in different time periods;

[0136] The determining, based on the target event record table, the trigger quantity corresponding to the target event in the trigger period, and determining whether the trigger quantity exceeds a first threshold, includes:

[0137] Determining whether there is a trigger record corresponding to the trigger period in the target event record table;

[0138] If so, the trigger quantity is counted based on the trigger record corresponding to the trigger period, and it is determined whether the trigger quantity exceeds a first threshold.

[0139] Furthermore, after determining whether there is a trigger record corresponding to the trigger period in the target event record table, the method further includes:

[0140] If it is determined that there is no trigger record corresponding to the trigger period, a trigger record corresponding to the trigger period is added.

[0141] Further, after counting the trigger quantity based on the trigger records corresponding to the trigger period and determining whether the trigger quantity exceeds a first threshold, the method further includes:

[0142] Based on the trigger records, the number of historical triggers of the target event in each period before the trigger period is counted, and the trigger change trend of the target event is determined based on the historical trigger number; the trigger change trend includes any one of the three types of increase, decrease and stability;

[0143] When it is determined that there is a number of historical triggers exceeding the first threshold, an abnormal history record is generated based on the number of historical triggers exceeding the first threshold and the corresponding time period, and an alarm is issued based on the trigger change trend and the historical abnormal record.

[0144] Furthermore, the trigger quantity includes a first quantity and a second quantity; the first quantity is the quantity of the target events in the target event record table in the internal cache that are triggered during the trigger period; the second quantity is the quantity of the target events recorded in the external cache that are triggered during the trigger period;

[0145] Before determining whether the trigger quantity exceeds a first threshold, the method further includes:

[0146] Determine whether the first number exceeds a second threshold, wherein the second threshold is less than the first threshold; the first number is the number of the target events in the target event record table in the internal cache that are triggered during the trigger period;

[0147] When it is determined that the first number exceeds the second threshold, and it is determined that the target event has been recorded in the target event record table in the external cache, the second number is obtained, and a trigger number is determined based on the first number and the second number;

[0148] Performing a zeroing operation on a first number of the target events in the internal cache during the trigger period;

[0149] Further, after determining whether the first quantity exceeds the second threshold, the method further includes:

[0150] When it is determined that the first number exceeds the second threshold and it is determined that the target event is not recorded in the target event record table in the external cache, a target event record table of the target event is added to the external cache, and the target event record table of the external cache is used to record when the target event is triggered again during the trigger period.

[0151] Further, the performing the processing operation on the target event includes:

[0152] Generate a to-be-processed task based on the target event, and send the to-be-processed task to a task processing queue, wherein the to-be-processed task is marked with task information, and the task information is determined based on event attribute information of the target event;

[0153] Based on the task processing queue, a corresponding processing operation is selected for the to-be-processed task according to the task information, wherein each type of task information corresponds to a processing operation, and the processing operation also includes a custom operation set based on processing requirements.

[0154] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing program code that initializes the following method steps: based on event attribute information, determining a target event to be processed in an error event; wherein the event attribute information is set by a user; determining whether a processing operation needs to be performed on the target event based on an event trigger parameter of the target event, wherein the trigger parameter is used to characterize the degree to which the target event is triggered; if it is determined that processing is required, performing the processing operation on the target event, wherein the processing operation includes pausing the behavior corresponding to the target event.

[0155] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0156] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0157] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0158] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0159] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0160] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0161] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0162] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0163] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0164] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for processing an error event, characterized in that: The method comprises: Based on the event attribute information, determine the target event to be processed in the error event; Determining whether the target event needs to perform a processing operation based on an event trigger parameter of the target event, wherein the trigger parameter is used to characterize the degree to which the target event is triggered; If it is determined that processing is required, the processing operation is performed on the target event, and the processing operation includes pausing the execution logic corresponding to the target event.

2. The method according to claim 1, characterized in that The event trigger parameters include a trigger period and a corresponding trigger quantity; The determining whether the target event needs to perform a processing operation based on the event trigger parameter of the target event includes: When it is determined that there is a target event record table of the target event in the internal cache, determining the trigger quantity corresponding to the target event in the trigger period based on the target event record table, and determining whether the trigger quantity exceeds a first threshold; wherein the target event record table is used to record the process of the target event being triggered; If it is determined that processing is required, performing the processing operation on the target event includes: If it is determined that the first threshold is exceeded, the processing operation is performed on the target event.

3. The method according to claim 2, characterized in that The event attribute information includes at least the error type and error identifier of the target event, and the error identifier is used to distinguish different subtypes under the error type; When it is determined that the target event record table of the target event exists in the internal cache, before determining the trigger quantity corresponding to the target event in the trigger period based on the target event record table, the method further includes: In the multiple event record tables stored in the internal cache, determining whether there is a matching event record table according to the error type and the error identifier; wherein each event record table stored in the internal cache is marked with a corresponding error type and error identifier; If there is a matching event record table, determining that a target event record table of the target event exists in the internal cache; If there is no matching event record table, then a new event record table corresponding to the error type and the error identifier is added to the internal cache, and the newly added event record table is the target event record table of the target event.

4. The method according to claim 2, characterized in that: The target event record table in the internal cache records the triggering records of the target event in different time periods; The determining, based on the target event record table, the trigger quantity corresponding to the target event in the trigger period, and determining whether the trigger quantity exceeds a first threshold, includes: Determining whether there is a trigger record corresponding to the trigger period in the target event record table; If so, the trigger quantity is counted based on the trigger record corresponding to the trigger period, and it is determined whether the trigger quantity exceeds a first threshold.

5. The method according to claim 4, characterized in that After counting the number of triggers based on the trigger records corresponding to the trigger period and determining whether the number of triggers exceeds a first threshold, the method further includes: Based on the trigger records, the number of historical triggers of the target event in each period before the trigger period is counted, and the trigger change trend of the target event is determined based on the historical trigger number; the trigger change trend includes any one of the three types of increase, decrease and stability; When it is determined that there is a number of historical triggers exceeding the first threshold, an abnormal history record is generated based on the number of historical triggers exceeding the first threshold and the corresponding time period, and an alarm is issued based on the trigger change trend and the historical abnormal record.

6. The method according to claim 4, characterized in that The trigger quantity includes a first quantity and a second quantity; the first quantity is the quantity of target events in the target event record table in the internal cache that are triggered during the trigger period; the second quantity is the quantity of target events recorded in the external cache that are triggered during the trigger period; Before determining whether the trigger quantity exceeds a first threshold, the method further includes: determining whether the first number exceeds a second threshold, wherein the second threshold is less than the first threshold; When it is determined that the first number exceeds the second threshold, and it is determined that the target event has been recorded in the target event record table in the external cache, the second number is obtained, and a trigger number is determined based on the first number and the second number; A first number of the target events in the internal cache during the trigger period is reset to zero.

7. The method according to claim 6, characterized in that After determining whether the first quantity exceeds the second threshold, the method further includes: When it is determined that the first number exceeds the second threshold and it is determined that the target event is not recorded in the target event record table in the external cache, a target event record table of the target event is added to the external cache, and the target event record table of the external cache is used to record when the target event is triggered again during the trigger period.

8. The method according to claim 6, characterized in that The performing the processing operation on the target event comprises: Generate a to-be-processed task based on the target event, and send the to-be-processed task to a task processing queue, wherein the to-be-processed task is marked with task information, and the task information is determined based on event attribute information of the target event; Based on the task processing queue, a corresponding processing operation is selected for the to-be-processed task according to the task information, wherein each type of task information corresponds to a processing operation, and the processing operation also includes a custom operation set based on processing requirements.

9. A device for processing an error event, characterized in that: The device comprises: A first determining unit, configured to determine a target event to be processed in the error reporting event based on the event attribute information; A second determining unit, configured to determine whether the target event needs to perform a processing operation based on an event trigger parameter of the target event, wherein the trigger parameter is used to characterize the degree to which the target event is triggered; an execution unit, configured to execute the processing operation on the target event if it is determined that processing is required, wherein the processing operation includes pausing the execution logic corresponding to the target event; Alternatively, the device includes a storage medium; and one or more processors, the storage medium is coupled to the processor, and the processor is configured to execute program instructions stored in the storage medium; when the program instructions are executed, the method for processing an error event described in any one of claims 1 to 8 is executed.

10. A storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the method for processing an error event according to any one of claims 1 to 8.

Images