CN115981857B - Fault analysis system - Google Patents
Fault analysis system Download PDFInfo
- Publication number
- CN115981857B CN115981857B CN202211669173.3A CN202211669173A CN115981857B CN 115981857 B CN115981857 B CN 115981857B CN 202211669173 A CN202211669173 A CN 202211669173A CN 115981857 B CN115981857 B CN 115981857B
- Authority
- CN
- China
- Prior art keywords
- fault analysis
- fault
- rule
- analysis
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The present disclosure relates to a fault analysis system. The fault analysis system comprises a fault analysis server and at least two fault analysis machines; the fault analysis server is used for responding to a fault analysis request, generating a fault analysis task according to fault data in the fault analysis request and distributing the fault analysis task to any one of the at least two fault analysis machines, wherein the fault analysis task comprises the fault data; the fault analysis machine is used for responding to the fault analysis task received from the fault analysis server, obtaining at least one fault analysis rule, executing the fault analysis task according to the at least one fault analysis rule, obtaining a fault analysis result corresponding to the fault analysis task, and transmitting the fault analysis result back to the fault analysis server.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a fault analysis system.
Background
In the related art, fault analysis is performed by a manual analysis mode, and the efficiency of the fault analysis is low.
Disclosure of Invention
The present disclosure provides a fault analysis system comprising a fault analysis server and at least two fault analysis machines;
the fault analysis server is used for responding to a fault analysis request, generating a fault analysis task according to fault data in the fault analysis request and distributing the fault analysis task to any one of the at least two fault analysis machines, wherein the fault analysis task comprises the fault data;
the fault analysis machine is used for responding to the fault analysis task received from the fault analysis server, obtaining at least one fault analysis rule, executing the fault analysis task according to the at least one fault analysis rule, obtaining a fault analysis result corresponding to the fault analysis task, and transmitting the fault analysis result back to the fault analysis server.
The fault analysis system is provided with a fault analysis server and at least two fault analysis machines, the fault analysis server is used for responding to a fault analysis request, generating a fault analysis task according to fault data in the fault analysis request, distributing the fault analysis task to any fault analysis machine in the at least two fault analysis machines, wherein the fault analysis task comprises the fault data, the fault analysis machine is used for responding to the fault analysis task received from the fault analysis server, acquiring at least one fault analysis rule, executing the fault analysis task according to the at least one fault analysis rule, obtaining a fault analysis result corresponding to the fault analysis task, and returning the fault analysis result to the fault analysis server, so that automatic fault analysis can be realized, the problem can be quickly positioned, the maintenance efficiency can be improved, the user experience can be improved, the quality of software and hardware can be improved, and a data base can be provided for quick updating iteration of a product.
In one possible implementation, the fault analyzer is specifically configured to:
at least one fault analysis rule is obtained from a preset fault analysis rule base.
In this implementation manner, the fault analysis machine obtains at least one fault analysis rule from a preset fault analysis rule base in response to receiving the fault analysis task from the fault analysis server, and executes the fault analysis task according to the at least one fault analysis rule to obtain a fault analysis result corresponding to the fault analysis task, so that fault data can be subjected to fault analysis based on the latest fault analysis rule, and a more accurate fault analysis result can be obtained.
In one possible implementation, the fault analyzer is specifically configured to:
and acquiring all fault analysis rules from the fault analysis rule base.
In this implementation manner, the fault analysis machine obtains all fault analysis rules from a preset fault analysis rule base in response to receiving the fault analysis task from the fault analysis server, and executes the fault analysis task according to all fault analysis rules in the fault analysis rule base to obtain a fault analysis result corresponding to the fault analysis task, so that more complete fault analysis can be implemented on fault data based on all fault analysis rules, and more accurate fault analysis results can be obtained.
In one possible implementation of the present invention,
the fault analysis rule base is arranged in the fault analysis server.
In this implementation, by providing the failure analysis rule base in the failure analysis server, the failure analysis rule base can be managed by the failure analysis server.
In one possible implementation, the fault analyzer is specifically configured to:
transmitting the at least one fault analysis rule to a modulator engine module;
and matching the fault data with the at least one fault analysis rule through the debugger engine module.
In this implementation, the at least one fault analysis rule is sent to the modulator engine module by the fault analysis machine, and the fault data is matched with the at least one fault analysis rule by the debugger engine module, so that the more accurate fault analysis result can be obtained by executing the matching of the fault analysis rule by using the capability provided by the debugger engine module.
In one possible implementation, the fault analyzer is specifically configured to:
respectively matching the fault data with the at least one fault analysis rule to obtain at least one matching score corresponding to the at least one fault analysis rule one by one;
And generating a fault analysis result corresponding to the fault analysis task according to the at least one matching score.
In this implementation manner, the at least one matching score corresponding to the at least one fault analysis rule is obtained by respectively matching the fault data with the at least one fault analysis rule, and the fault analysis result corresponding to the fault analysis task can be generated according to the at least one matching score, so that the matching degree of the fault data and the fault analysis rule is quantified based on the matching score, and a more accurate fault analysis result can be obtained
In one possible implementation, the fault analyzer is specifically configured to:
matching the fault data with the fault analysis rules to obtain the matching degree between the fault data and the fault analysis rules for any one of the at least one fault analysis rule;
and determining a matching score corresponding to the fault analysis rule according to the matching degree, wherein the matching score is positively correlated with the matching degree.
In this implementation manner, the fault analysis machine matches the fault data with the fault analysis rule by matching any one of the at least one fault analysis rule to obtain a matching degree between the fault data and the fault analysis rule, and determines a matching score corresponding to the fault analysis rule according to the matching degree, where the matching score is positively correlated with the matching degree, so that it can be determined that a more accurate matching score is obtained.
In one possible implementation, the fault analyzer is specifically configured to:
determining a fault analysis rule corresponding to a matching score which is greater than or equal to a preset score in the at least one matching score as a target fault analysis rule;
and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule.
In this implementation manner, the fault analysis machine determines the fault analysis rule corresponding to the matching score greater than or equal to the preset score in the at least one matching score as a target fault analysis rule, and generates the fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule, so that a more accurate fault analysis result can be obtained.
In one possible implementation, the fault analyzer is specifically configured to:
and responding to the condition that only one target fault analysis rule exists, and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule, wherein the fault analysis result comprises the fault type.
In this implementation manner, in the case that only one of the matching scores corresponding to the fault analysis rules is greater than or equal to the preset score, only one of the fault analysis rules may be determined as the target fault analysis rule, and the fault analysis result corresponding to the fault analysis task may be generated according to the fault type corresponding to the target fault analysis rule, where the fault analysis result includes the fault type, so that interference of unnecessary information (for example, the fault type corresponding to the fault analysis rule other than the target fault analysis rule, etc.) on the user's checking of the fault analysis result may be reduced, and thus the time for the user to check the fault analysis result may be saved.
In one possible implementation, the fault analyzer is specifically configured to:
and responding to the number of the target fault analysis rules being greater than or equal to 2, and generating a fault analysis result corresponding to the fault analysis task according to the fault types corresponding to all the target fault analysis rules, wherein the fault analysis result comprises the fault types corresponding to each target fault analysis rule and the matching scores corresponding to each target fault analysis rule.
In this implementation manner, when the number of fault analysis rules with the matching score greater than or equal to the preset score is greater than or equal to 2, the fault analysis rules with the matching score greater than or equal to the preset score are respectively determined to be target fault analysis rules, and the fault types corresponding to the target fault analysis rules and the matching scores corresponding to the target fault analysis rules are provided for the user through the fault analysis results, so that a more complete and accurate fault analysis result can be provided for the user.
In one possible implementation, the fault analysis server is specifically configured to:
acquiring at least two busy and idle state information corresponding to the at least two fault analyzers one by one;
Determining a fault analysis machine with the minimum load in the at least fault analysis machines according to the at least two busy and idle state information;
and distributing the fault analysis task to the fault analysis machine with the minimum load.
In the implementation mode, the fault analysis server determines the fault analysis machine with the minimum load in the at least fault analysis machine according to at least two pieces of busy and idle state information corresponding to the at least two fault analysis machines one by one, and distributes the fault analysis task to the fault analysis machine with the minimum load, so that load balancing of the fault analysis machine can be realized, and the processing efficiency of the fault analysis task is improved.
In one possible implementation, the fault analysis server is specifically configured to:
numbering the fault analysis tasks;
and distributing the fault analysis task to any fault analysis machine in the at least two fault analysis machines based on the number.
In this implementation, the failure analysis server can pair the failure analysis tasks by numbering the failure analysis tasks and distributing the failure analysis tasks to any one of the at least two failure analysis machines based on the number 5
The fault analysis task is better managed.
In one possible implementation, the fault analysis server is further configured to:
and displaying the fault analysis result in response to receiving the fault analysis result.
In this implementation, 0 thus enables a user to learn about the failure analysis result in time by displaying the failure analysis result in response to receiving the failure analysis result.
In one possible implementation, the fault analysis server is specifically configured to:
and responding to the fault analysis result to comprise at least two fault types, and displaying the at least two fault types according to the sequence from high to low of the matching scores corresponding to the at least two fault types.
In this implementation, the at least two fault types are displayed according to the order of the matching scores corresponding to the 5 at least two fault types from high to low by responding to the fault analysis result to include the at least two fault types, thereby
Manual analysis can be facilitated.
In one possible implementation, the fault analysis server is specifically configured to:
and responding to the fault analysis result to comprise at least two fault types, and displaying the at least two fault types and the matching scores thereof according to the sequence from high to low of the matching scores corresponding to the at least two fault types.
0 in this implementation, by including at least two fault types in response to the fault analysis results, according to the
And displaying the at least two fault types and the matching scores thereof according to the sequence from high to low of the matching scores corresponding to the at least two fault types, so that manual analysis can be facilitated.
In one possible implementation, the fault analysis server is further configured to:
and responding to the received fault analysis result, and returning the fault 5-fault analysis result to the target equipment sending the fault analysis request.
In the implementation manner, the fault analysis server returns the fault analysis result to the target device sending the fault analysis request by responding to the received fault analysis result, so that a user corresponding to the target device can conveniently know the fault analysis result in time.
In one possible implementation, the fault analysis server is further configured to: and 0, updating the fault analysis rule base in response to a rule updating request.
In this implementation, the failure analysis server updates the failure analysis rule base by responding to the rule update request, thereby enabling to improve the accuracy of failure analysis.
In one possible implementation, the rule update request is for at least one of: adding fault analysis rules, deleting fault analysis rules and changing fault analysis rules.
5 in this implementation, by modifying the cause in response to the request for adding, deleting, or modifying the failure analysis rules
And updating the fault analysis rule base according to a rule updating request of at least one of the fault analysis rules, so that the accuracy of the follow-up fault analysis can be improved.
In one possible implementation, the fault analysis server is further configured to:
and returning all fault analysis rules in the fault analysis rule base in response to the rule searching request.
In the implementation manner, the fault analysis server returns all fault analysis rules in the fault analysis rule base by responding to the rule searching request, so that a user can conveniently know the latest condition of all fault analysis rules in the fault analysis rule base in time.
In one possible implementation, the fault analysis system further includes:
and the target equipment is used for generating a fault analysis request according to the fault data and sending the fault analysis request to the fault analysis server, wherein the fault analysis request comprises the fault data.
In the implementation manner, the target device generates a fault analysis request according to the fault data and sends the fault analysis request to the fault analysis server, wherein the fault analysis request comprises the fault data, so that the driving and hardware problems (such as the driving and hardware problems in a Windows system) can be automatically processed under a large-scale mass production scene, and the maintenance efficiency can be greatly improved.
In one possible implementation of the present invention,
the fault data includes: dumping the file;
the target device is specifically configured to: and generating a fault analysis request according to the dump file in response to the dump file existing in the preset directory.
In the implementation manner, the target device responds to the dump file in the preset catalog, and generates a fault analysis request according to the dump file, so that the fault analysis request can be automatically generated, and the fault analysis flow is automatically triggered.
In one possible implementation, the target device is further configured to:
and checking whether the dump file exists in the preset directory according to a preset period.
In the implementation manner, the target device checks whether the dump file exists in the preset catalog according to a preset period, so that abnormal information can be acquired regularly.
In the embodiment of the disclosure, a fault analysis server and at least two fault analysis machines are set in a fault analysis system, the fault analysis server is used for responding to a fault analysis request, generating a fault analysis task according to fault data in the fault analysis request, distributing the fault analysis task to any fault analysis machine in the at least two fault analysis machines, wherein the fault analysis task comprises the fault data, the fault analysis machine is used for responding to the fault analysis task received from the fault analysis server, acquiring at least one fault analysis rule, executing the fault analysis task according to the at least one fault analysis rule, obtaining a fault analysis result corresponding to the fault analysis task, and returning the fault analysis result to the fault analysis server, so that automatic fault analysis can be realized, the problem can be quickly positioned, the maintenance efficiency can be improved, the quality of software and hardware can be improved, and a data basis can be provided for realizing quick updating and iteration of products.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the technical aspects of the disclosure.
Fig. 1 shows a block diagram of a fault analysis system provided by an embodiment of the present disclosure.
Fig. 2 illustrates another block diagram of a fault analysis system provided by an embodiment of the present disclosure.
Fig. 3 shows a block diagram of an electronic device 1900 provided by an embodiment of the disclosure.
Detailed Description
Various exemplary embodiments, features and aspects of the disclosure will be described in detail below with reference to the drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Although various aspects of the embodiments are illustrated in the accompanying drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.
Furthermore, numerous specific details are set forth in the following detailed description in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements, and circuits well known to those skilled in the art have not been described in detail in order not to obscure the present disclosure.
Fig. 1 shows a block diagram of a fault analysis system provided by an embodiment of the present disclosure. As shown in fig. 1, the fault analysis system includes a fault analysis server 100 and at least two fault analysis machines 200; the fault analysis server 100 is configured to generate a fault analysis task according to fault data in a fault analysis request in response to the fault analysis request, and distribute the fault analysis task to any one of the at least two fault analysis machines 200, where the fault analysis task includes the fault data; the fault analyzer 200 is configured to obtain at least one fault analysis rule in response to receiving the fault analysis task from the fault analysis server 100, execute the fault analysis task according to the at least one fault analysis rule, obtain a fault analysis result corresponding to the fault analysis task, and return the fault analysis result to the fault analysis server 100.
In the disclosed embodiment, the failure analysis system includes a failure analysis server 100 and at least two failure analysis machines 200. The failure analysis server 100 may be also referred to as an automatic analysis server or an automatic failure analysis device, and is not limited herein. The fault analysis server 100 may. The failure analyzer 200 may also be referred to as an automatic analyzer or the like, and is not limited herein. All of the failure analyzers 200 may constitute a failure analyzer cluster.
In the embodiment of the present disclosure, the fault analysis server 100 may receive a fault analysis request from a remote device, where the fault analysis request may carry fault data to be analyzed. The failure analysis server 100 may generate a failure analysis task from failure data in the failure analysis request in response to the failure analysis request. The failure analysis server 100 may distribute a failure analysis task to one failure analysis machine 200 of the at least two failure analysis machines 200 to cause the failure analysis machine 200 to perform the failure analysis task.
In one possible implementation, the fault analysis server 100 may include a task distribution module that may perform task validation and numbering according to fault data, and may perform task distribution according to busy states of at least two fault analysis machines 200 to achieve load balancing.
In the embodiment of the present disclosure, the fault analysis machine 200 may perform the fault analysis task according to at least one fault analysis rule in response to receiving the fault analysis task, so as to obtain a fault analysis result corresponding to the fault analysis task, and return the fault analysis result to the fault analysis server 100.
In one possible implementation, the fault analyzer 200 is specifically configured to: at least one fault analysis rule is obtained from a preset fault analysis rule base.
In this implementation, a fault analysis rule base may be preset, where the fault analysis rule base may include at least one fault analysis rule. For example, the fault analysis rule base may include a plurality of fault analysis rules. Wherein the fault analysis rules may represent rules for analyzing fault data.
As an example of this implementation, the fault analysis machine 200 may obtain at least one fault analysis rule from the fault analysis rule base through foreground software.
In this implementation manner, the fault analysis machine 200 obtains at least one fault analysis rule from a preset fault analysis rule base in response to receiving the fault analysis task from the fault analysis server 100, and executes the fault analysis task according to the at least one fault analysis rule to obtain a fault analysis result corresponding to the fault analysis task, so that fault data can be subjected to fault analysis based on the latest fault analysis rule, and a more accurate fault analysis result can be obtained.
As an example of this implementation, the fault analyzer 200 is specifically configured to: and acquiring all fault analysis rules from the fault analysis rule base.
In this example, the fault analysis machine 200 obtains the fault analysis result corresponding to the fault analysis task by acquiring all fault analysis rules from a preset fault analysis rule base in response to receiving the fault analysis task from the fault analysis server 100 and executing the fault analysis task according to all fault analysis rules in the fault analysis rule base, thereby enabling more complete fault analysis on fault data based on all fault analysis rules, and enabling more accurate fault analysis results.
As another example of this implementation, the fault analyzer 200 may obtain one fault analysis rule at a time from the fault analysis rule base, and may not obtain the remaining fault analysis rules from the fault analysis rule base in response to the matching score corresponding to any one fault analysis rule reaching a preset score (e.g., 100%).
As an example of this implementation, the failure analysis rule base is provided in the failure analysis server 100. In this example, by providing the failure analysis rule base in the failure analysis server 100, the failure analysis rule base can be managed by the failure analysis server 100.
As another example of this implementation, the failure analysis rule base is provided in a server other than the failure analysis server 100.
In another possible implementation, the fault analysis machine 200 may store the fault analysis rules locally without having to obtain the fault analysis rules from a fault analysis rule base each time a fault analysis task is received. In this implementation, the fault analysis server 100 may update the fault analysis rules in response to the fault analysis rules in the fault analysis rule base, and send the updated fault analysis rules to each fault analysis machine 200, so that each fault analysis machine 200 performs fault analysis on the fault data based on the latest fault analysis rules, thereby obtaining a more accurate fault analysis result.
In one possible implementation, the fault analyzer 200 is specifically configured to: transmitting the at least one fault analysis rule to a modulator engine module; and matching the fault data with the at least one fault analysis rule through the debugger engine module.
For example, the debugger engine may be dbgengine. Dll, which is not limited herein. Wherein dbgengine. Dll is debug software provided by Windows, and has the capability of fault data processing.
In this implementation, the fault analysis rules may be sent to the modulator engine module of the back-end. The modulator engine module can analyze the fault data by adopting the analysis command to obtain a data analysis result, and match the data analysis result with the fault analysis rule.
As one example of this implementation, the fault analysis machine 200 may include an execution module that may send the at least one fault analysis rule to a modulator engine module and match the fault data with the at least one fault analysis rule via the debugger engine module.
In this implementation, the at least one fault analysis rule is sent to the modulator engine module by the fault analysis engine 200, and the fault data is matched with the at least one fault analysis rule by the debugger engine module, so that the matching of the fault analysis rule is performed by using the capability provided by the debugger engine module, and a more accurate fault analysis result can be obtained.
In one possible implementation, the fault analyzer 200 is specifically configured to: respectively matching the fault data with the at least one fault analysis rule to obtain at least one matching score corresponding to the at least one fault analysis rule one by one; and generating a fault analysis result corresponding to the fault analysis task according to the at least one matching score.
In this implementation manner, the higher the matching score corresponding to any one fault analysis rule, the more the fault data is matched with the fault analysis rule, that is, the higher the probability that the fault data belongs to the fault type corresponding to the fault analysis rule. If the fault data is completely matched with any fault analysis rule, the matching score may be a full score.
In this implementation manner, the at least one matching score corresponding to the at least one fault analysis rule is obtained by respectively matching the fault data with the at least one fault analysis rule, and the fault analysis result corresponding to the fault analysis task can be generated according to the at least one matching score, so that the matching degree of the fault data and the fault analysis rule is quantified based on the matching score, and a more accurate fault analysis result can be obtained.
As an example of this implementation, the fault analyzer 200 is specifically configured to: matching the fault data with the fault analysis rules to obtain the matching degree between the fault data and the fault analysis rules for any one of the at least one fault analysis rule; and determining a matching score corresponding to the fault analysis rule according to the matching degree, wherein the matching score is positively correlated with the matching degree.
For example, the matching degree may have a value range of [0,1], and the matching score may have a value range of [0,100].
Of course, the person skilled in the art can flexibly set the range of the matching degree and the matching score according to the actual application scene requirement, and the method is not limited herein.
In this example, the fault analysis machine 200 obtains a matching degree between the fault data and the fault analysis rule by matching the fault data with the fault analysis rule for any one of the at least one fault analysis rule, and determines a matching score corresponding to the fault analysis rule according to the matching degree, wherein the matching score is positively correlated with the matching degree, thereby enabling determination of obtaining a more accurate matching score.
As an example of this implementation, the fault analyzer 200 is specifically configured to: determining a fault analysis rule corresponding to a matching score which is greater than or equal to a preset score in the at least one matching score as a target fault analysis rule; and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule.
In this example, the number of target failure analysis rules may be at least one. That is, the fault data may match at least one fault analysis rule. That is, the fault data may belong to at least one fault type. Accordingly, the fault analysis results may include at least one fault type.
In this example, the fault analyzer 200 determines a fault analysis rule corresponding to a matching score greater than or equal to a preset score from among the at least one matching score as a target fault analysis rule, and generates a fault analysis result corresponding to the fault analysis task according to a fault type corresponding to the target fault analysis rule, thereby enabling more accurate fault analysis results.
In one example, the fault analyzer 200 is specifically configured to: and responding to the condition that only one target fault analysis rule exists, and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule, wherein the fault analysis result comprises the fault type.
In this example, in a case where there is and only one of the matching scores corresponding to the fault analysis rules is greater than or equal to the preset score, only the fault analysis rule may be determined as the target fault analysis rule, and the fault analysis result corresponding to the fault analysis task may be generated according to the fault type corresponding to the target fault analysis rule, where the fault analysis result includes the fault type, so that interference of unnecessary information (for example, the fault type corresponding to the fault analysis rule other than the target fault analysis rule, etc.) on the user's viewing of the fault analysis result may be reduced, and thus the time for the user to view the fault analysis result may be saved.
In another example, the fault analyzer 200 is specifically configured to: and responding to the condition that only one target fault analysis rule exists, and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule, wherein the fault analysis result comprises the fault type and the matching score corresponding to the target fault analysis rule.
In one example, the fault analyzer 200 is specifically configured to: and responding to the number of the target fault analysis rules being greater than or equal to 2, and generating a fault analysis result corresponding to the fault analysis task according to the fault types corresponding to all the target fault analysis rules, wherein the fault analysis result comprises the fault types corresponding to each target fault analysis rule and the matching scores corresponding to each target fault analysis rule.
In this example, in the case where the number of the fault analysis rules having the matching score greater than or equal to the preset score is greater than or equal to 2, the fault analysis rules having the matching score greater than or equal to the preset score are respectively determined as the target fault analysis rules, and the fault types corresponding to the target fault analysis rules and the matching scores corresponding to the target fault analysis rules are provided to the user through the fault analysis results, so that a more complete and accurate fault analysis result can be provided to the user.
In another example, the fault analyzer 200 is specifically configured to: and responding to the number of the target fault analysis rules being greater than or equal to 2, and generating a fault analysis result corresponding to the fault analysis task according to the fault types corresponding to all the target fault analysis rules, wherein the fault analysis result comprises the fault types corresponding to each target fault analysis rule.
As another example of this implementation, the fault analyzer 200 is specifically configured to: determining a fault analysis rule corresponding to the highest matching score in the at least one matching score as a target fault analysis rule; and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule.
In another possible implementation, the fault analyzer 200 is specifically configured to: respectively matching the fault data with the at least one fault analysis rule to obtain at least one matching degree corresponding to the at least one fault analysis rule one by one; and generating a fault analysis result corresponding to the fault analysis task according to the at least one matching degree.
In one possible implementation, the fault analysis server 100 is specifically configured to: acquiring at least two busy/idle state information corresponding to the at least two fault analyzers 200 one by one; determining a fault analyzer 200 with the least load among the at least fault analyzers 200 according to the at least two busy state information; the fault analysis task is distributed to the fault analysis machine 200 with the smallest load.
In this embodiment, the busy/idle state information corresponding to any one of the fault analyzers 200 may be any information that can indicate the busy/idle state of the fault analyzer 200.
In this implementation manner, the fault analysis server 100 determines, according to at least two pieces of busy state information corresponding to the at least two fault analysis machines 200 one by one, the fault analysis machine 200 with the smallest load in the at least fault analysis machines 200, and distributes the fault analysis task to the fault analysis machine 200 with the smallest load, thereby realizing load balancing of the fault analysis machines 200 and improving processing efficiency of the fault analysis task.
In another possible implementation manner, the fault analysis server 100 is specifically configured to: randomly determining a target failure analyzer 200 from the at least two failure analyzers 200; the fault analysis tasks are distributed to the target fault analysis machine 200.
In one possible implementation, the fault analysis server 100 is specifically configured to: numbering the fault analysis tasks; the failure analysis task is distributed to any failure analysis machine 200 of the at least two failure analysis machines 200 based on the number.
In this implementation, the fault analysis server 100 can better manage the fault analysis tasks by numbering the fault analysis tasks and distributing the fault analysis tasks to any one of the at least two fault analysis machines 200 based on the numbering.
In one possible implementation, the fault analysis server 100 is further configured to: and displaying the fault analysis result in response to receiving the fault analysis result.
As one example of this implementation, the fault analysis server 100 may include a result display module that may display the fault analysis result in response to receiving the fault analysis result.
In this implementation, the fault analysis result is displayed in response to receiving the fault analysis result, thereby enabling a user to know the fault analysis result in time.
As an example of this implementation, the fault analysis server 100 is specifically configured to: and responding to the fault analysis result to comprise at least two fault types, and displaying the at least two fault types according to the sequence from high to low of the matching scores corresponding to the at least two fault types.
In one example, the failure analysis results may be displayed in a list form.
In this example, by displaying at least two fault types according to the order of the matching scores of the at least two fault types from high to low in response to the fault analysis result including the at least two fault types, manual analysis can be facilitated.
In one example, the fault analysis server 100 is specifically configured to: and responding to the fault analysis result to comprise at least two fault types, and displaying the at least two fault types and the matching scores thereof according to the sequence from high to low of the matching scores corresponding to the at least two fault types.
In this example, by displaying at least two fault types and their matching scores according to the order of the matching scores corresponding to the at least two fault types from high to low in response to the fault analysis result including the at least two fault types, manual analysis can be facilitated.
In one possible implementation, in case the failure analysis result includes only one failure type, no subsequent participation by a human may be required. In case the fault analysis result comprises at least two fault types, the subsequent determination may be performed manually.
In one possible implementation, the fault analysis server 100 is further configured to: and responding to the received fault analysis result, and returning the fault analysis result to the target equipment sending the fault analysis request.
In this implementation, the target device may represent a device that sends a failure analysis request to the failure analysis server 100. In this implementation manner, the fault analysis server 100 returns the fault analysis result to the target device that sends the fault analysis request in response to receiving the fault analysis result, so that a user corresponding to the target device can conveniently and timely learn about the fault analysis result.
In one possible implementation, the fault analysis server 100 is further configured to: and updating the fault analysis rule base in response to a rule updating request.
As one example of this implementation, the fault analysis server 100 may include a rule base update module that may be used to update the fault analysis rule base in response to a rule update request.
In this implementation, the fault analysis server 100 can improve the accuracy of fault analysis by updating the fault analysis rule base in response to a rule update request.
As an example of this implementation, the rule update request is for at least one of: adding fault analysis rules, deleting fault analysis rules and changing fault analysis rules.
In one example, the fault analysis server 100 may add the fault analysis rule in the fault analysis rule base in response to a rule update request for adding the fault analysis rule. For example, new fault analysis rules may be generated based on the process flow of known problems and key error identification.
In another example, the fault analysis server 100 may delete a fault analysis rule from the fault analysis rule base in response to a rule update request for deleting the fault analysis rule.
In another example, the fault analysis server 100 may make a change to at least one fault analysis rule in the fault analysis rule base in response to a rule update request for changing the fault analysis rule.
In this example, by updating the failure analysis rule base in response to a rule update request for at least one of adding a failure analysis rule, deleting a failure analysis rule, and changing a failure analysis rule, the accuracy of the subsequent failure analysis can be improved.
In one possible implementation, the fault analysis server 100 is further configured to: and returning all fault analysis rules in the fault analysis rule base in response to the rule searching request.
In this implementation, the fault analysis server 100 returns all fault analysis rules in the fault analysis rule base by responding to the rule search request, thereby enabling the user to conveniently know the latest situation of all fault analysis rules in the fault analysis rule base in time.
In one possible implementation, the fault analysis system further includes: and the target equipment is used for generating a fault analysis request according to the fault data and sending the fault analysis request to the fault analysis server 100, wherein the fault analysis request comprises the fault data.
Fig. 2 illustrates another block diagram of a fault analysis system provided by an embodiment of the present disclosure. As shown in fig. 2, the fault analysis system further includes a target device 300. Wherein the number of target devices 300 may be at least one. For example, the number of target devices 300 may be plural.
As one example of this implementation, the target device 300 may collect fault data through a data collection module. In one example, the data collection module may be located in a driver manager.
In this implementation manner, the target device 300 generates a fault analysis request according to the fault data, and sends the fault analysis request to the fault analysis server 100, where the fault analysis request includes the fault data, so that the driving and hardware problems (such as the driving and hardware problems in the Windows system) can be automatically processed in a large-scale mass production scenario, and thus the maintenance efficiency can be greatly improved.
As an example of this implementation, the fault data includes: dumping the file; the target device 300 is specifically configured to: and generating a fault analysis request according to the dump file in response to the dump file existing in the preset directory.
For example, when a graphic card drive fails seriously, the Windows system is restarted and a dump file (dump file) is generated.
For example, the preset directory may be a Windows directory, etc., which is not limited herein.
In this example, in the case where dump files exist in the preset directory, the dump files may be collected according to a predetermined rule and packaged to generate a failure analysis request.
In this example, the target device 300 generates a failure analysis request according to the dump file in response to the dump file being present in the preset directory, thereby automatically generating the failure analysis request and automatically triggering the flow of the failure analysis.
In one example, the target device 300 is further configured to: and checking whether the dump file exists in the preset directory according to a preset period.
In one example, the management software of the graphics card may automatically scan whether a dump file exists.
In this example, by the target device 300 checking whether the dump file exists in the preset directory at a preset period, it is possible to periodically acquire the abnormality information.
In one possible implementation, the fault analysis system further includes: and a communication module, configured to communicate with the fault analysis server 100 by using the target device 300. In this implementation, the target device 300 may send a failure analysis request to the failure analysis server 100 through the communication module. Wherein a remote failure analysis center or monitoring center, etc. may be implemented in the failure analysis server 100.
It will be appreciated that the above-mentioned method embodiments of the present disclosure may be combined with each other to form a combined embodiment without departing from the principle logic, and are limited to the description of the present disclosure. It will be appreciated by those skilled in the art that in the above-described methods of the embodiments, the particular order of execution of the steps should be determined by their function and possible inherent logic.
The embodiment of the disclosure also provides an electronic device, including: one or more processors; a memory for storing executable instructions; wherein the one or more processors are configured to invoke the executable instructions stored by the memory to perform the above-described method. The electronic device may be provided as a terminal, server or other form of device.
Fig. 3 shows a block diagram of an electronic device 1900 provided by an embodiment of the disclosure. For example, electronic device 1900 may be provided as a failure analysis server or failure analysis engine. Referring to FIG. 3, electronic device 1900 includes a processing component 1922 that further includes one or more processors and memory resources represented by memory 1932 for storing instructions, such as application programs, that can be executed by processing component 1922. The application programs stored in memory 1932 may include one or more modules each corresponding to a set of instructions. Further, processing component 1922 is configured to execute instructions to perform the methods described above.
The electronic device 1900 may also include a power component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input/output (I/O) interface 1958. Electronic device 1900 may operate an operating system based on memory 1932, such as the Microsoft Server operating system (Windows Server) TM ) Apple Inc. developed graphical user interface based operating System (Mac OS X TM ) Multi-user multi-process computer operating system (Unix) TM ) Unix-like operating system (Linux) of free and open source code TM ) Unix-like operating system (FreeBSD) with open source code TM ) Or the like.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 1932, including computer program instructions executable by processing component 1922 of electronic device 1900 to perform the methods described above.
The present disclosure may be a system, method, and/or computer program product. The computer program product may include a computer readable storage medium having computer readable program instructions embodied thereon for causing a processor to implement aspects of the present disclosure.
The computer readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: portable computer disks, hard disks, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static Random Access Memory (SRAM), portable compact disk read-only memory (CD-ROM), digital Versatile Disks (DVD), memory sticks, floppy disks, mechanical coding devices, punch cards or in-groove structures such as punch cards or grooves having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media, as used herein, are not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses through fiber optic cables), or electrical signals transmitted through wires.
The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a respective computing/processing device or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network interface card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing/processing device.
Computer program instructions for performing the operations of the present disclosure can be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, c++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present disclosure are implemented by personalizing electronic circuitry, such as programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), with state information of computer readable program instructions, which can execute the computer readable program instructions.
Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The computer program product may be realized in particular by means of hardware, software or a combination thereof. In an alternative embodiment, the computer program product is embodied as a computer storage medium, and in another alternative embodiment, the computer program product is embodied as a software product, such as a software development kit (Software Development Kit, SDK), or the like.
The foregoing description of various embodiments is intended to highlight differences between the various embodiments, which may be the same or similar to each other by reference, and is not repeated herein for the sake of brevity.
If the technical scheme of the embodiment of the disclosure relates to personal information, the product applying the technical scheme of the embodiment of the disclosure clearly informs the personal information processing rule and obtains personal independent consent before processing the personal information. If the technical solution of the embodiment of the present disclosure relates to sensitive personal information, the product applying the technical solution of the embodiment of the present disclosure obtains individual consent before processing the sensitive personal information, and simultaneously meets the requirement of "explicit consent". For example, a clear and remarkable mark is set at a personal information acquisition device such as a camera to inform that the personal information acquisition range is entered, personal information is acquired, and if the personal voluntarily enters the acquisition range, the personal information is considered as consent to be acquired; or on the device for processing the personal information, under the condition that obvious identification/information is utilized to inform the personal information processing rule, personal authorization is obtained by popup information or a person is requested to upload personal information and the like; the personal information processing rule may include information such as a personal information processor, a personal information processing purpose, a processing mode, and a type of personal information to be processed.
The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the improvement of technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (20)
1. A fault analysis system, characterized in that the fault analysis system comprises a target device, a fault analysis server and at least two fault analysis machines;
the target device is used for responding to the dump file existing in the preset catalog, generating a fault analysis request according to the dump file and sending the fault analysis request to the fault analysis server, wherein the fault analysis request comprises the dump file;
the fault analysis server is used for responding to the fault analysis request, generating a fault analysis task according to the dump file in the fault analysis request and distributing the fault analysis task to any one of the at least two fault analysis machines, wherein the fault analysis task comprises the dump file;
The fault analysis machine is used for responding to the fault analysis task received from the fault analysis server, obtaining at least one fault analysis rule, executing the fault analysis task according to the at least one fault analysis rule, obtaining a fault analysis result corresponding to the fault analysis task, and transmitting the fault analysis result back to the fault analysis server.
2. The fault analysis system of claim 1, wherein the fault analyzer is configured in particular to:
at least one fault analysis rule is obtained from a preset fault analysis rule base.
3. The fault analysis system of claim 2, wherein the fault analyzer is configured in particular to:
and acquiring all fault analysis rules from the fault analysis rule base.
4. A fault analysis system according to claim 2 or 3, wherein,
the fault analysis rule base is arranged in the fault analysis server.
5. A fault analysis system according to any one of claims 1 to 3, characterized in that the fault analyzer is in particular adapted to:
transmitting the at least one fault analysis rule to a debugger engine module;
And matching the dump file with the at least one fault analysis rule through the debugger engine module.
6. A fault analysis system according to any one of claims 1 to 3, characterized in that the fault analyzer is in particular adapted to:
respectively matching the dump file with the at least one fault analysis rule to obtain at least one matching score corresponding to the at least one fault analysis rule one by one;
and generating a fault analysis result corresponding to the fault analysis task according to the at least one matching score.
7. The fault analysis system of claim 6, wherein the fault analyzer is configured in particular to:
matching the dump file with any one of the at least one fault analysis rule to obtain the matching degree between the dump file and the fault analysis rule;
and determining a matching score corresponding to the fault analysis rule according to the matching degree, wherein the matching score is positively correlated with the matching degree.
8. The fault analysis system of claim 6, wherein the fault analyzer is configured in particular to:
Determining a fault analysis rule corresponding to a matching score which is greater than or equal to a preset score in the at least one matching score as a target fault analysis rule;
and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule.
9. The fault analysis system of claim 8, wherein the fault analyzer is configured in particular to:
and responding to the condition that only one target fault analysis rule exists, and generating a fault analysis result corresponding to the fault analysis task according to the fault type corresponding to the target fault analysis rule, wherein the fault analysis result comprises the fault type.
10. The fault analysis system of claim 8, wherein the fault analyzer is configured in particular to:
and responding to the number of the target fault analysis rules being greater than or equal to 2, and generating a fault analysis result corresponding to the fault analysis task according to the fault types corresponding to all the target fault analysis rules, wherein the fault analysis result comprises the fault types corresponding to each target fault analysis rule and the matching scores corresponding to each target fault analysis rule.
11. The fault analysis system of claim 1, wherein the fault analysis server is configured in particular to:
acquiring at least two busy and idle state information corresponding to the at least two fault analyzers one by one;
determining a fault analysis machine with the minimum load in the at least fault analysis machines according to the at least two busy and idle state information;
and distributing the fault analysis task to the fault analysis machine with the minimum load.
12. The fault analysis system according to claim 1 or 11, wherein the fault analysis server is in particular adapted to:
numbering the fault analysis tasks;
and distributing the fault analysis task to any fault analysis machine in the at least two fault analysis machines based on the number.
13. The fault analysis system of claim 1 or 11, wherein the fault analysis server is further configured to:
and displaying the fault analysis result in response to receiving the fault analysis result.
14. The fault analysis system of claim 13, wherein the fault analysis server is configured to:
and responding to the fault analysis result to comprise at least two fault types, and displaying the at least two fault types according to the sequence from high to low of the matching scores corresponding to the at least two fault types.
15. The fault analysis system of claim 14, wherein the fault analysis server is configured to:
and responding to the fault analysis result to comprise at least two fault types, and displaying the at least two fault types and the matching scores thereof according to the sequence from high to low of the matching scores corresponding to the at least two fault types.
16. The fault analysis system of claim 1 or 11, wherein the fault analysis server is further configured to:
and responding to the received fault analysis result, and returning the fault analysis result to the target equipment sending the fault analysis request.
17. The fault analysis system of claim 1 or 11, wherein the fault analysis server is further configured to:
and updating the fault analysis rule base in response to a rule updating request.
18. The fault analysis system of claim 17, wherein the rule update request is for at least one of: adding fault analysis rules, deleting fault analysis rules and changing fault analysis rules.
19. The fault analysis system of claim 1 or 11, wherein the fault analysis server is further configured to:
And returning all fault analysis rules in the fault analysis rule base in response to the rule searching request.
20. A fault analysis system according to any one of claims 1 to 3, wherein the target device is further configured to:
and checking whether the dump file exists in the preset directory according to a preset period.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211669173.3A CN115981857B (en) | 2022-12-23 | 2022-12-23 | Fault analysis system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211669173.3A CN115981857B (en) | 2022-12-23 | 2022-12-23 | Fault analysis system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115981857A CN115981857A (en) | 2023-04-18 |
| CN115981857B true CN115981857B (en) | 2023-09-19 |
Family
ID=85971756
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211669173.3A Active CN115981857B (en) | 2022-12-23 | 2022-12-23 | Fault analysis system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115981857B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170024299A1 (en) * | 2015-07-21 | 2017-01-26 | International Business Machines Corporation | Providing Fault Injection to Cloud-Provisioned Machines |
| CN108604200A (en) * | 2016-11-03 | 2018-09-28 | 华为技术有限公司 | The method and terminal device of the failure of processing terminal equipment |
| CN109274533A (en) * | 2018-09-28 | 2019-01-25 | 中国电子科技集团公司第十五研究所 | A kind of positioning device and method of the Web service failure of rule-based engine |
| CN111026572A (en) * | 2019-11-15 | 2020-04-17 | 北京金山云网络技术有限公司 | Fault processing method and device of distributed system and electronic equipment |
| US10963333B1 (en) * | 2018-08-21 | 2021-03-30 | Cox Communications, Inc. | Telematics-based network device troubleshooting and repair |
| CN113448303A (en) * | 2020-03-27 | 2021-09-28 | 广州汽车集团股份有限公司 | Vehicle fault diagnosis method and system |
| CN113544486A (en) * | 2019-03-08 | 2021-10-22 | 三菱电机株式会社 | Fault diagnosis system, prediction rule generation method, and prediction rule generation program |
| CN114691398A (en) * | 2020-12-30 | 2022-07-01 | 中兴通讯股份有限公司 | Rule-based fault analysis method, device, equipment and storage medium |
| CN114884796A (en) * | 2022-06-16 | 2022-08-09 | 中国工商银行股份有限公司 | Fault processing method and device, electronic equipment and storage medium |
| CN115016445A (en) * | 2022-07-27 | 2022-09-06 | 浙江极氪智能科技有限公司 | Remote fault diagnosis method and device for vehicle, vehicle and computer storage medium |
-
2022
- 2022-12-23 CN CN202211669173.3A patent/CN115981857B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170024299A1 (en) * | 2015-07-21 | 2017-01-26 | International Business Machines Corporation | Providing Fault Injection to Cloud-Provisioned Machines |
| CN108604200A (en) * | 2016-11-03 | 2018-09-28 | 华为技术有限公司 | The method and terminal device of the failure of processing terminal equipment |
| US10963333B1 (en) * | 2018-08-21 | 2021-03-30 | Cox Communications, Inc. | Telematics-based network device troubleshooting and repair |
| CN109274533A (en) * | 2018-09-28 | 2019-01-25 | 中国电子科技集团公司第十五研究所 | A kind of positioning device and method of the Web service failure of rule-based engine |
| CN113544486A (en) * | 2019-03-08 | 2021-10-22 | 三菱电机株式会社 | Fault diagnosis system, prediction rule generation method, and prediction rule generation program |
| CN111026572A (en) * | 2019-11-15 | 2020-04-17 | 北京金山云网络技术有限公司 | Fault processing method and device of distributed system and electronic equipment |
| CN113448303A (en) * | 2020-03-27 | 2021-09-28 | 广州汽车集团股份有限公司 | Vehicle fault diagnosis method and system |
| CN114691398A (en) * | 2020-12-30 | 2022-07-01 | 中兴通讯股份有限公司 | Rule-based fault analysis method, device, equipment and storage medium |
| CN114884796A (en) * | 2022-06-16 | 2022-08-09 | 中国工商银行股份有限公司 | Fault processing method and device, electronic equipment and storage medium |
| CN115016445A (en) * | 2022-07-27 | 2022-09-06 | 浙江极氪智能科技有限公司 | Remote fault diagnosis method and device for vehicle, vehicle and computer storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115981857A (en) | 2023-04-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11055646B2 (en) | Automated ticket resolution | |
| US10692065B2 (en) | Using a mixture model to generate simulated transaction information | |
| AU2018201941A1 (en) | Automated program code analysis and reporting | |
| US11907840B2 (en) | Method and system for generating a dynamic sequence of actions | |
| US9703690B2 (en) | Determining test case efficiency | |
| US10949765B2 (en) | Automated inference of evidence from log information | |
| CN109614325B (en) | Method and device for determining control attribute, electronic equipment and storage medium | |
| US9329979B2 (en) | Derivation of generalized test cases | |
| US10372572B1 (en) | Prediction model testing framework | |
| US10599476B2 (en) | Device and method for acquiring values of counters associated with a computational task | |
| CN113051183A (en) | Test data recommendation method and system, electronic device and storage medium | |
| CN111813649A (en) | Automatically generating integration tests from unit tests | |
| KR102118487B1 (en) | Automatic quality inspection system and method of container based application for ci/cd | |
| CN115981857B (en) | Fault analysis system | |
| US10685292B1 (en) | Similarity-based retrieval of software investigation log sets for accelerated software deployment | |
| CN111859139A (en) | Application program recommendation method and device, computing equipment and medium | |
| US11656977B2 (en) | Automated code checking | |
| CN113094415B (en) | Data extraction method, data extraction device, computer readable medium and electronic equipment | |
| CN113434382A (en) | Database performance monitoring method and device, electronic equipment and computer readable medium | |
| EP3379409A1 (en) | Automated program code analysis and reporting | |
| CN111290870A (en) | Method and device for detecting abnormity | |
| CN116089187B (en) | GPU test system, electronic equipment and storage medium | |
| CN112506762B (en) | Application program interface parameter screening method, device, equipment and storage medium | |
| CN117130945B (en) | Test method and device | |
| US20230048513A1 (en) | Intelligent cloud service health communication to customers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |