Fault location method, device, electronic device and storage medium for application system
By obtaining monitoring items associated with exception monitoring items in the application system and determining the fault source, the problem of difficulty in fault location by operation and maintenance engineers in complex systems is solved, and the accuracy and efficiency of fault source location is improved.
Patent Information
- Application Number
- CN202010838988.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-08-19
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-08-19
AI Technical Summary
In complex software systems, operation and maintenance engineers need to spend a lot of time and effort during the troubleshooting process. The information provided by existing monitoring tools is relatively large, resulting in increased difficulty in fault location.
Through multiple monitoring items, multiple monitoring objects in the application system are monitored separately, and the associated monitoring items with preset associations with exception monitoring items are obtained, and the fault source of the application system is determined based on the monitoring results, and information including the fault source is output, thereby Realize the interrelationship of each monitoring object and the correlation of monitoring items, and improve the accuracy of fault source positioning.
It greatly improves the accuracy of fault source positioning, assists operation and maintenance engineers to quickly locate the fault source of production environment failures, and promotes rapid recovery of production services and ensures business availability.
Smart Images

Figure CN112084055B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of operation and maintenance technology, and in particular to a method, device, computer equipment and storage medium for locating a fault of an application system. Background Art
[0002] In recent years, with the continuous progress of computer technology and the continuous improvement of computer application level, in order to meet the increasing needs of customers, it is usually necessary to establish complex and large software systems on the server. Because of this, in the process of operating and maintaining the software system, it is becoming more and more difficult for operation and maintenance engineers to troubleshoot the faults that occur. At present, in order to reduce the difficulty of troubleshooting for operation and maintenance engineers, the CPU (central processing unit) usage, memory usage, disk space, network traffic, etc. of the server are usually monitored for a long time, and thresholds are set for each monitoring item. When the threshold is exceeded, an alarm message will be issued to prompt the operation and maintenance engineer to handle it.
[0003] Although the above existing troubleshooting solutions can provide positioning for operation and maintenance engineers to a certain extent, since the information provided to the operation and maintenance engineers covers a large area, the operation and maintenance engineers are still required to conduct in-depth troubleshooting, and the troubleshooting process requires a lot of time and effort. Summary of the invention
[0004] In view of the above problems, embodiments of the present invention provide a method, apparatus, computer device and storage medium for locating faults of an application system to solve the above problems.
[0005] In a first aspect, an embodiment of the present invention provides a fault locating method for an application system, the method being used to monitor the operating status of multiple monitoring objects in the application system respectively through multiple monitoring items, the method comprising: when the monitoring result of any monitoring item is an abnormal state, taking the monitoring item in the abnormal state as the first monitoring item; obtaining at least one associated monitoring item having a preset association relationship with the first monitoring item; obtaining the monitoring results of the associated monitoring items, the monitoring results of the associated monitoring items including a normal state and an abnormal state; and determining the fault source of the application system according to the monitoring results, and outputting information including the fault source.
[0006] In a second aspect, an embodiment of the present invention provides a fault locating device for an application system, the device is used to monitor the running status of multiple monitoring objects in the application system respectively through multiple monitoring items, and the device includes: a first monitoring item acquisition module, an associated monitoring item acquisition module, a monitoring result acquisition module and a fault source determination module. The first monitoring item acquisition module is used to take the monitoring item in the abnormal state as the first monitoring item when the monitoring result of any monitoring item is an abnormal state. The associated monitoring item acquisition module is used to obtain at least one associated monitoring item that has a preset association relationship with the first monitoring item. The monitoring result acquisition module is used to obtain the monitoring results of the associated monitoring items, and the monitoring results of the associated monitoring items include a normal state and an abnormal state. The fault source determination module is used to determine the fault source of the application system according to the monitoring results, and output information including the fault source.
[0007] In a third aspect, an embodiment of the present invention provides a control unit, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned method for locating the fault of the application system when executing the computer program.
[0008] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned method for locating a fault in an application system are implemented.
[0009] The present invention provides a fault locating method, device, computer equipment and storage medium for an application system. The fault locating method for the application system is used to monitor the running status of multiple monitoring objects in the application system respectively through multiple monitoring items. The fault locating method for the application system can monitor each monitoring object in the application system respectively through the monitoring items. When the monitoring result of a certain monitoring item is in an abnormal state, the monitoring item is used as the first monitoring item, and an associated monitoring item with a preset association relationship with the first monitoring item is further obtained. The fault source in the application system is obtained according to the monitoring result of the associated monitoring item, and information including the fault source is output, thereby realizing that each monitoring object in the application system is associated with each other, and each monitoring item is associated, so that when an abnormality occurs in one of the monitoring objects, the status of the monitoring object associated with the monitoring object can be further obtained, which greatly improves the accuracy of fault source locating, can assist operation and maintenance engineers in quickly locating the fault source of the production environment fault in complex monitoring items, and plays a great role in promoting the rapid recovery of production services and ensuring the availability of services. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.
[0011] Figure 1 A schematic diagram of an application environment suitable for an embodiment of the present invention is shown.
[0012] Figure 2 A schematic flow chart of a method for locating a fault in an application system according to an embodiment of the present invention is shown.
[0013] Figure 3 Shows Figure 2 A flowchart of the steps for obtaining associated monitoring items in the method shown.
[0014] Figure 4 Shows Figure 1 A flow chart of the steps of determining a fault source in the method shown.
[0015] Figure 5 A schematic flow chart of the steps of configuring weight values for monitoring items in a fault locating method for an application system according to an embodiment of the present invention is shown.
[0016] Figure 6 A flow chart showing steps for obtaining monitoring results in a method for locating a fault in an application system according to an embodiment of the present invention is shown.
[0017] Figure 7 Shows Figure 6 A flowchart of the steps of determining the monitoring results of the monitoring items corresponding to the monitoring objects whose monitoring type is a static type in the method shown.
[0018] Figure 8 Shows Figure 6 A flowchart of the steps of determining the monitoring results of the monitoring items corresponding to the monitoring objects whose monitoring type is a dynamic type in the method shown.
[0019] Fig. 9 A functional module block diagram of a fault location device for an application system proposed in an embodiment of the present invention is shown.
[0020] Fig.10 A functional module block diagram of an electronic device proposed in an embodiment of the present invention is shown. DETAILED DESCRIPTION
[0021] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0022] In order to clearly explain the solutions of the present invention, some terms are explained below.
[0023] Application system: a system formed by the cooperation of software and hardware;
[0024] Monitoring objects: hardware units and / or software units that implement various functions in the application system;
[0025] Monitoring item: a monitoring unit used to monitor the status of the monitored object;
[0026] Monitoring tool: a tool for monitoring various monitoring objects in the application system;
[0027] Operation and maintenance: operation and maintenance of each stage of the application system life cycle;
[0028] Fault location: troubleshoot faulty units in the application system;
[0029] Fault source: The source of the fault in the application system, such as the faulty monitoring object.
[0030] At present, in order to meet business needs, it is usually necessary to develop new application systems, or update the versions of various production environments in the original application systems, business changes, code logic or network fluctuations, etc., which may cause various abnormal situations. Especially when the production environment system is large and complex, there are dozens or hundreds of applications, and the server scale is even thousands or tens of thousands. It is particularly difficult for operation and maintenance engineers to track and analyze the root causes of failures. The main difficulty in tracking and locating the root causes of failures is that after a long period of historical development, the architecture of business services has become more and more complex, with many functional modules, many monitoring systems, a large number of alarms, etc., which makes tracking more difficult. At the same time, due to the large number of business modules, the operation and maintenance engineers reflect thousands of monitoring combination dimensions (such as provinces, operators, client versions, server versions, etc.) in the global monitoring data, and it is difficult to accurately locate the root causes of related failures.
[0031] In the existing technology, traditional monitoring tools such as Nagios and Zabbix are usually used. Monitoring tools can monitor basic monitoring items of server dimensions such as CPU usage, memory usage, disk space, network traffic, etc. for a long time. Operation and maintenance engineers need to set alarm thresholds for monitoring items, such as good, warning, error and other states. Once the threshold is exceeded, an alarm message will be issued. However, once a certain failure occurs, the business indicators, application indicators and operating system indicators associated with the source of the failure will also issue alarm messages at the same time. It is still difficult for operation and maintenance engineers to locate the root cause of the failure.
[0032] Based on this, the inventor of the present invention has conducted a lot of research and found that in the process of monitoring the application system, a neural network model can be used to locate the fault source in the application system. Specifically, the historical data of the application system is used as a sample and trained through the neural network model. When the recognition accuracy of the neural network model reaches a preset value, the trained neural network model is used to obtain the alarm information in the application system, and prediction is made based on the alarm information to obtain the fault source of the application system. The inventor found that although the method of predicting the fault source through the neural network model can theoretically obtain a better fault source location result, due to the high requirements of the neural network model on the training samples, the large amount of training sample data, and the low degree of repetition of many faults in the application system, the recognition effect of the neural network model is poor, and the computing resources required are large and the cost is high, which is not conducive to actual commercial use.
[0033] In order to fundamentally solve the above-described problems, the inventor of the present invention continues to invest in research and development, and is committed to studying how to improve the accuracy of fault source location in the application system. Further, the inventor proposes a fault location method for the application system of the present invention, in which the fault location method for the application system is used to monitor the operating status of multiple monitoring objects in the application system through multiple monitoring items. In the fault location method for the application system, when the monitoring result of any monitoring item is an abnormal state, the monitoring item in the abnormal state is used as the first monitoring item; at least one associated monitoring item that has a preset association relationship with the first monitoring item is obtained; the monitoring result of the associated monitoring item is obtained, and the monitoring result of the associated monitoring item includes a normal state and an abnormal state; and the fault source of the application system is determined according to the monitoring result, and information including the fault source is output. Through monitoring items, each monitoring object in the application system is monitored separately. When the monitoring result of a monitoring item is abnormal, the monitoring item is used as the first monitoring item, and the associated monitoring item with a preset association relationship with the first monitoring item is further obtained, and the fault source in the application system is obtained according to the monitoring result of the associated monitoring item, thereby realizing the mutual association of each monitoring object in the application system and associating each monitoring item, so that when an abnormality occurs in one of the monitoring objects, the status of the monitoring object associated with the monitoring object can be further obtained, which greatly improves the accuracy of fault source locating, and can assist operation and maintenance engineers in quickly locating the fault source of the production environment fault in complex monitoring items, which greatly promotes the rapid recovery of production services and ensuring business availability.
[0034] The fault location method of the application system provided by the present invention can be applied as follows: Figure 1 In the system environment shown, the system environment may include a server 10 and a client 20, and the server 10 may communicate with the client 20 through a network 50. The client 20 may include, but is not limited to, intelligent portable devices such as personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and may also be software such as applications installed on electronic devices, without specific restrictions here. The server 10 may be implemented with an independent server or a server cluster consisting of multiple servers. In addition, the server may be a cloud server or a traditional computer room server. Furthermore, the application system may run on the server 10, and the system formed based on the system positioning method of the application system may be used as a monitoring center, which may be deployed on the server to monitor the status of the application system.
[0035] See also Figure 2, a method for locating a fault in an application system provided in an embodiment of the present invention is applied to a server 10. Once triggered, the process of the method in the embodiment can be automatically run by a control device, wherein each step can be performed in sequence as in the flowchart, or multiple steps can be performed simultaneously according to actual conditions, which is not limited here. It should be noted that when some functions in the application system are implemented by the client, the method for locating a fault in the application system can also locate the fault of the functional module of the client responsible for implementing the part of the function.
[0036] The fault location method of the application system is used to monitor the running status of multiple monitoring objects in the application system respectively through multiple monitoring items.
[0037] In the embodiment of the present invention, the application system usually includes a computer hardware system, system software, and application software. Among them, the computer hardware system may include an arithmetic unit and a controller, a memory, a peripheral interface, a peripheral device, etc.; the system software may include an operating system, a compiler, a database management system, various high-level languages, etc.; the application software may include general support software and various application software packages. The monitoring object may be a unit that implements various functions in the application system. The monitoring item may be used to monitor the status of the corresponding monitoring object.
[0038] It should be noted that in the embodiment of the present invention, the application system can be divided into multiple monitoring levels, each monitoring level includes one or more monitoring objects. Among them, the monitoring objects in the application system can be divided according to functional categories, and the monitoring level can be a general term for monitoring objects belonging to a certain functional category in the application system. For example, the monitoring level can be a business layer, an application service layer, a system service layer, an operating system layer, an infrastructure layer, etc.
[0039] In order to more clearly understand the specific meaning of the monitoring object and the relationship between the monitoring objects in the embodiment of the present invention, the various monitoring levels of the application system are described below:
[0040] Specifically, the business layer may include various indicators that reflect the quality of business operations. For example, the monitoring objects in the business layer may be page views (PV), unique visitors (UV), the number of registered users per day, the number of logged-in users per day, the number of daily active users, the number of monthly active users, etc. The application service layer may include indicators that reflect the operating quality of the application. For example, the monitoring objects in the application service layer may be queries per second (QPS), application interface response success rate, application interface response speed, HTTP (Hypertext Transfer Protocol) response code, HTTP response speed, etc. The system service layer may include performance indicators of various middleware in the system. For example, the middleware may be a database, cache, message queue, etc., and the monitoring objects in the system service layer may be the QPS of MySQL (relational database management system), the load of the middleware, the space utilization rate, etc. The operating system layer may include various application indicators of the operating system. For example, the monitoring objects in the operating system layer may be CPU (central processing unit) utilization, memory utilization, disk utilization, etc. The infrastructure layer may include basic indicators of the server. For example, when the server is an IDC (Internet Data Center) computer room, the monitoring objects in the infrastructure layer can be a series of indicators such as the computer room, racks, routers, switches, and dedicated line quality; when the server is a cloud server, the monitoring objects in the infrastructure layer can be total bandwidth traffic, load balancing traffic, instance running status, etc.
[0041] In the embodiment of the present invention, each monitoring level in the application system should be related and associated, and the monitoring objects in each level need to support each other to realize various functions. That is to say, when the application system is in working state, when a monitoring object in the business layer is abnormal, other monitoring objects in the application service layer associated with the monitoring object may be abnormal. Take the following table (1) as an example.
[0042]
[0043] Table (1)
[0044] As shown in Table (1), the application system is divided into five monitoring levels, namely the business layer, application service layer, system service layer, operating system layer and infrastructure layer. Among them, the monitoring object in the business layer is PV. When PV statistics are required, the monitoring object in the application service layer needs to be used: site health detection, and the monitoring objects in the system service layer need to be used: Tomcat (Apache Tomcat), REDIS (Remote Dictionary Server) and MYSQL. The monitoring objects in the system service layer also need to be used: CPU, Memory, Disk and Network. The monitoring objects in the infrastructure layer also need to be used: load balancing, firewall and switch. In other words, since the completion of PV statistics requires calling each monitoring object shown in Table (1), when the monitoring object PV is abnormal, each monitoring object shown in Table (1) may be in an abnormal state.
[0045] It should be noted that when the monitoring layers include the business layer, application service layer, system service layer, operating system layer, and infrastructure layer, there is a hierarchical support relationship between the monitoring layers. When the business layer needs to implement a certain function, it needs the support of the application service layer; when the application service layer needs to implement another function, it needs the support of the system service layer and / or the business layer, and so on.
[0046] The application system in this embodiment adopts a hierarchical structure, and each monitoring object in the application system is divided to obtain multiple monitoring levels. Since the monitoring levels are in an upper and lower support relationship, when an abnormality occurs in a monitoring object in one of the monitoring levels, the relationship between the monitoring objects in the upper and lower monitoring levels can be quickly obtained through the relationship between the monitoring levels, so that the relationship between the monitoring objects is clearer, which helps to improve the accuracy and efficiency of fault location in the actual fault location process.
[0047] Furthermore, the fault location method of the application system may include the following steps S11 to S14.
[0048] Step S11: when the monitoring result of any monitoring item is in an abnormal state, the monitoring item in the abnormal state is used as the first monitoring item.
[0049] The plurality of monitoring items are respectively used to monitor the states of the plurality of monitoring objects, so as to obtain monitoring results corresponding to the monitoring objects. In addition, each monitoring object may correspond to a monitoring item corresponding to the monitoring item.
[0050] Step S12: Acquire at least one associated monitoring item that has a preset association relationship with the first monitoring item.
[0051] In an embodiment of the present invention, the preset association relationship may include a functional realization relationship between monitoring items. Specifically, when the monitoring object corresponding to the monitoring item realizes a certain function, if the realization of the function requires calling other monitoring objects, the monitoring items with other monitoring objects are judged to be associated monitoring items. For example, as shown in Table (1) above, the associated monitoring items that have a preset association relationship with the monitoring items of the monitoring PV include the monitoring items corresponding to site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch, respectively.
[0052] Step S13: Acquire monitoring results of associated monitoring items, where the monitoring results of associated monitoring items include normal status and abnormal status.
[0053] In an embodiment of the present invention, the monitoring result of each associated monitoring item can be obtained. Specifically, taking the above table (1) as an example, when the result of the monitoring item corresponding to PV is abnormal, the monitoring results of each monitoring item corresponding to site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch associated with it can be obtained respectively.
[0054] Step S14: Determine the fault source of the application system according to the monitoring result, and output information including the fault source.
[0055] In the embodiment of the present invention, the fault source may be a monitoring object corresponding to the first monitoring item, or a monitoring object corresponding to the associated monitoring item. In addition, the fault source of the application system may be obtained by analyzing and calculating based on the monitoring result and / or the operating parameters of the monitoring object.
[0056] It should be noted that, after determining the fault source of the monitoring result, information including the fault source can be output, and the information can be fault prompt information, which is used to prompt the operation and maintenance engineer to know the cause of the fault in the application system. For example, when the fault source of the application system is Memory, the feedback information "Memory in the application system is the fault source, please eliminate the fault as soon as possible" is fed back to remind the operation and maintenance engineer, wherein the feedback information can be in various ways, such as room alarm, SMS sending, email sending, voice broadcast, etc., and the feedback information method is not specifically limited here.
[0057] In this embodiment, through the implementation of the above steps S11 to S14, each monitoring object in the application system can be monitored separately through monitoring items. When the monitoring result of a certain monitoring item is an abnormal state, the monitoring item is used as the first monitoring item, and the associated monitoring item that has a preset association relationship with the first monitoring item is further obtained. The fault source in the application system is obtained according to the monitoring result of the associated monitoring item, and information including the fault source is output, thereby realizing the mutual association of each monitoring object in the application system and associating each monitoring item. When an abnormality occurs in one of the monitoring objects, the state of the monitoring object associated with the monitoring object can be further obtained, which greatly improves the accuracy of fault source locating, and can assist operation and maintenance engineers in quickly locating the fault source of the production environment fault in complex monitoring items, which greatly promotes the rapid recovery of production services and ensuring the availability of services.
[0058] Further, as an implementation method of this embodiment, Figure 3 As shown, the above step S12 may also include the following steps S121 to S122.
[0059] Step S121: Determine the monitoring group to which the first monitoring item belongs, wherein the monitoring group includes the first monitoring item and one or more different second monitoring items, and the first monitoring item and each second monitoring item are respectively used to monitor a corresponding monitoring object.
[0060] In an embodiment of the present invention, the monitoring group may include a set of monitoring objects that the application system needs to call to complete a certain function. The number of monitoring groups of monitoring objects in the monitoring application system may be one or more, and the multiple monitoring objects in the monitoring group may be distributed in one or more monitoring levels. In addition, the way to determine the monitoring group to which the first monitoring item belongs may be to query in a pre-set database, and the mapping relationship between each monitoring item and each monitoring group should be pre-stored in the pre-set database.
[0061] It should be noted that a monitoring item may belong to one monitoring group or to different monitoring groups. In other words, the number of monitoring groups to which the first monitoring item belongs may be one or more.
[0062] Step S122: according to the monitoring group, determine a second monitoring item having a preset association relationship with the first monitoring item from one or more second monitoring items, and determine the second monitoring item having a preset association relationship with the first monitoring item as an associated monitoring item.
[0063] In an embodiment of the present invention, when the monitoring object corresponding to the first monitoring item is in a working state, it is necessary to call the monitoring objects monitored by all the second monitoring items in the monitoring group to which the first monitoring item belongs, and at this time, all the second monitoring items in the monitoring group to which the first monitoring item belongs are associated monitoring items. For example, taking the above table (1) as an example, the monitoring items corresponding to PV, site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch form a monitoring group. When the monitoring result of the monitoring item corresponding to PV is abnormal, the monitoring item corresponding to PV is used as the first monitoring item, and the monitoring items corresponding to site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch are respectively used as second monitoring items. Since it is necessary to call monitoring items such as site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch when implementing PV statistics, each second monitoring item is regarded as an associated monitoring item. When the monitoring object corresponding to the first monitoring item is in working state, when it is necessary to call the monitoring objects monitored by some second monitoring items in the monitoring group to which the first monitoring item belongs, at this time, the part of the second monitoring items in the monitoring group to which the first monitoring item belongs are all associated monitoring items.
[0064] In an embodiment, through the implementation of steps S121 to S122 above, the monitoring group to which the first monitoring item belongs can be obtained first, and then the associated monitoring items having a preset association relationship with the first monitoring item can be determined based on the monitoring group to which it belongs. Since the relationship between the monitoring group and the monitoring item is pre-set, there is no need to traverse the query in the database and then judge the relationship between other monitoring items and the first monitoring item one by one, which effectively reduces the query time and improves the efficiency of fault source locating.
[0065] Further, as an implementation method of this embodiment, Figure 4 As shown, the above step S14 may include the following steps S141 to S142.
[0066] Step S141: If the monitoring result of at least one of the associated monitoring items is in an abnormal state, a first weight value of the first monitoring item and a second weight value of the associated monitoring item in the abnormal state are obtained.
[0067] In an embodiment of the present invention, a corresponding weight value can be set in advance for each monitoring item. When locating a fault, it can be determined whether the monitoring object corresponding to the monitoring item is the source of the fault based on the first weight value of the first monitoring item and the second weight value of the associated monitoring item in an abnormal state.
[0068] In addition, the weight value of each monitoring item can be stored in a pre-built database, and the first weight value of the first monitoring item and the second weight value of the associated monitoring item in an abnormal state are obtained from the pre-built database. It should be noted that for a monitoring item, the weight value of the monitoring item should be configured in the monitoring group to which the monitoring item belongs.
[0069] Step S142: Determine the fault source from the plurality of monitoring objects according to the first weight value and the second weight value, and the corresponding relationship between the associated monitoring items, the first monitoring items and the monitoring objects, and output information including the fault source.
[0070] In an embodiment of the present invention, the fault source can be determined based on the magnitude of the first weight value and the second weight value. Furthermore, the monitoring object corresponding to the weight value with the largest numerical value in the first weight value and the second weight value can be determined as the fault source, and the monitoring object corresponding to the weight value with the highest numerical value in the first weight value and the second weight value can also be determined as the fault source. For example, the monitoring objects corresponding to the weight values with the top three numerical values in the first weight value and the second weight value can be determined as the fault source, and the monitoring objects corresponding to the weight values with the top 20% numerical values in the first weight value and the second weight value can also be determined as the fault source, and no specific limitation is made here. In other words, the fault source can be one or more. Take the following table (2) as an example:
[0071]
[0072] Table (2)
[0073] As shown in Table (2), the monitoring item corresponding to PV is taken as the first monitoring item, and the first weight value of the first monitoring item is obtained as "1"; the monitoring items corresponding to site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch are respectively taken as associated monitoring items, and the monitoring objects corresponding to the associated monitoring items with abnormal monitoring results are obtained: site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, and the second weight values of the associated monitoring items corresponding to site health detection, Tomcat, REDIS, MYSQL, CPU, and Memory are obtained as "2", "3", "3", "3", "4", and "4" respectively. According to the size of the first weight value and each second weight value, the monitoring objects (CPU and Memory) corresponding to the two key monitoring items with a weight value of "4" are determined as the fault source.
[0074] In this embodiment, through the implementation of the above-mentioned steps S141 to S142, the fault source can be determined based on the monitoring results of each associated monitoring item, the first weight value of the first monitoring item and the second weight value of the associated monitoring item, without having to regard all monitoring objects with abnormal monitoring results as the fault source, thereby effectively improving the accuracy of fault source locating and reducing the troubleshooting time of operation and maintenance engineers.
[0075] Further, as an implementation method of this embodiment, Figure 5 As shown, before the above step S11, the weight value of each monitoring item may be pre-configured, and configuring the weight value of each monitoring item may include the following steps S21 to S22.
[0076] Step S21: Group multiple monitoring items to obtain at least one monitoring group.
[0077] In the embodiment of the present invention, a monitoring group may include one or more monitoring items, and a monitoring item may belong to one or more monitoring groups.
[0078] In addition, when grouping multiple monitoring items, the monitoring objects in the application system that need to be called to complete a certain function can be divided into the same monitoring group. For example, taking the above table (1) as an example, when performing PV statistics, it is necessary to call site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch. Therefore, PV, site health detection, Tomcat, REDIS, MYSQL, CPU, Memory, Disk, Network, load balancing, firewall, and switch can be divided into the same monitoring group.
[0079] Step S22: According to the application attributes of the monitored object and the corresponding relationship between the monitored objects, the weight value of each monitored item is configured.
[0080] In an embodiment of the present invention, application attributes may include the application of the monitoring object function. For example, the application attributes may be the logic of the monitoring object when implementing the function, the call time of the monitoring object, the call relationship with other monitoring objects, etc. Specifically, the higher the importance of the data part processed by the monitoring object in a certain monitoring group, the larger the weight value of the monitoring item configuration corresponding to the monitoring object in the monitoring group can be; the more times the monitoring object is called in a certain monitoring group, the larger the weight value of the monitoring item configuration corresponding to the monitoring object in the monitoring group can be. In other words, the operation and maintenance engineer himself classifies and summarizes according to the characteristics of the business, thereby adjusting the weight of the monitoring item in the monitoring group.
[0081] It should be noted that, in the embodiment of the present invention, the same monitoring item may belong to multiple monitoring groups at the same time, and the weights of the monitoring item in different monitoring groups may be different, which can be determined according to the business situation. For example, there is a monitoring item A, and monitoring item A belongs to monitoring group X and monitoring group Y respectively. The weight value of monitoring item A in monitoring group X is a, and the weight value of monitoring item A in monitoring group Y is b. The sizes of a and b may be the same or different.
[0082] In this embodiment, through the implementation of the above steps S21 to S22, the weight values of the monitoring items corresponding to the monitored objects can be configured based on the application attributes of the monitored objects, so that when this embodiment is actually applied, the operation and maintenance engineers can configure the weight values of each monitoring item in the monitoring group to which it belongs according to various business characteristics.
[0083] Further, as an implementation of this embodiment, when determining the fault source, the above step S14 may include: if the monitoring results of each associated monitoring item are in a normal state, determining that the monitoring object corresponding to the first monitoring item is the fault source, and outputting information including the fault source.
[0084] In the embodiment of the present invention, if the monitoring results of each associated monitoring item are all in a normal state, the fault source is the monitoring object corresponding to the first monitoring item. For example, the monitoring group includes the first monitoring item B, the associated monitoring item C, the associated monitoring item D, and the associated monitoring item E. When the monitoring results of the associated monitoring item C, the associated monitoring item D, and the associated monitoring item E are all in a normal state, the monitoring object corresponding to the first monitoring item B is determined as the fault source.
[0085] In this embodiment, by implementing the step of determining that the monitoring object corresponding to the first monitoring item is the source of the fault if the monitoring results of each associated monitoring item are normal, the associated monitoring items can be checked and excluded as the source of the fault, thereby avoiding the operation and maintenance engineers wasting too much time on checking the monitoring objects that are not faulty.
[0086] Further, as an implementation method of this embodiment, Figure 6 As shown, before the above-mentioned step S11, a step of selecting different processing methods based on the monitoring type of the monitored object to obtain monitoring results can be performed to adopt different processing standards for different monitored objects. Therefore, before step S11, the fault location method of the application system of this embodiment can also include the following steps S31 to S32.
[0087] Step S31: Obtain the monitoring type of each monitored object, where the monitoring type includes a static type and a dynamic type.
[0088] In the embodiment of the present invention, the monitoring type of the monitoring object can be classified according to the judgment criterion of its running state, and the judgment criterion can be understood as the basis for judging whether the running state of the monitoring object is normal or abnormal, wherein the monitoring object whose parameters of the judgment criterion do not change over time belongs to the static type, and the monitoring object whose parameters of the judgment criterion change over time belongs to the dynamic type. For example, the monitoring objects belonging to the static type may be disk space, CPU, Tomcat, REDIS, MYSQL, etc.; the monitoring objects belonging to the dynamic type may be PV, UV, the number of registered users per day, the number of logged-in users per day, the number of daily active users, etc.
[0089] Step S32: Analyze the operating parameters of each monitored object according to the monitoring type to obtain the monitoring results of the monitoring items corresponding to each monitored object.
[0090] In an embodiment of the present invention, different judgment criteria may be used for monitoring objects of different monitoring types, so as to obtain monitoring results of monitoring items corresponding to each monitoring object. The operating parameters may be parameters used to represent the operating conditions of the monitoring object. For example, when the monitoring object is a login page, the operating parameters may be PV, UV, the number of registered users per day, etc. When the monitoring type of the monitoring object is a static type, a processing method corresponding to the static type is selected to obtain monitoring results of monitoring items corresponding to the monitoring object; when the monitoring type of the monitoring object is a dynamic type, a processing method corresponding to the dynamic type is selected to obtain monitoring results of monitoring items corresponding to the monitoring object.
[0091] In this embodiment, by implementing the above steps S31 to S32, different processing methods can be selected based on different monitoring types of the monitored objects to obtain monitoring results of the monitored items, thereby achieving diversified processing to adapt to different application scenarios.
[0092] Further, as an implementation method of this embodiment, Figure 7 As shown, a corresponding processing method can be selected for a monitoring object whose monitoring type is a static type to obtain a monitoring result for obtaining the monitoring result of the monitoring item corresponding to the monitoring object whose monitoring type is a static type. Therefore, the above step S32 can also include the following steps S321 to S322.
[0093] Step S321: If the monitoring type of the monitored object is a static type, obtain the first operating parameter of the monitored object.
[0094] In the embodiment of the present invention, the first operating parameter may be used to represent the operating information of the monitoring object of the static type. For example, the first operating parameter may be disk space usage, CPU usage, memory occupancy, etc.
[0095] Step S322: Determine the monitoring result of the monitoring item corresponding to the monitoring object whose monitoring type is the static type according to the size relationship between the first operating parameter and the preset static threshold.
[0096] In the embodiment of the present invention, the static threshold can be determined based on experience. For example, when the first operating parameter is disk space usage, the static threshold can be 90%; when the first operating parameter is CPU usage, the static threshold can be 80%.
[0097] In an embodiment of the present invention, when the first operating parameter is greater than the static threshold, the monitoring result of the monitoring item corresponding to the monitoring object is determined to be in an abnormal state; when the first operating parameter is less than or equal to the static threshold, the monitoring result of the monitoring item corresponding to the monitoring object is determined to be in a normal state. For example, when the first operating parameter of the monitoring object is a CPU usage rate of 95% and the static threshold is 90%, the first operating parameter is greater than the static threshold, indicating that the CPU is in an overloaded operating state at this time, and the monitoring result of the monitoring item corresponding to the CPU is in an abnormal state. When the CPU is determined to be the source of the fault, the information "CPU usage rate 95%, in an overloaded state" can be output to prompt the operation and maintenance engineer.
[0098] In this embodiment, by implementing the above steps S321 to S322, it is possible to determine whether a monitoring object of a static type is abnormal, thereby obtaining a monitoring result, and a static threshold judgment method is adopted.
[0099] Further, as an implementation method of this embodiment, Figure 8 As shown, a corresponding processing method can be selected for a monitoring object whose monitoring type is a dynamic type to obtain a monitoring result for obtaining the monitoring result of the monitoring item corresponding to the monitoring object whose monitoring type is a dynamic type. Therefore, the above step S32 can also include the following steps S323 to S325.
[0100] Step S323: If the monitoring type of the monitored object is a dynamic type, obtain the second operating parameter of the monitored object.
[0101] In the embodiment of the present invention, the second operating parameter may be used to represent the operating information of the monitoring object of the dynamic type. For example, the second operating parameter may be PV, UV, the number of registered users in a certain period of time, etc.
[0102] Step S324: obtaining a third operating parameter of a monitoring object whose monitoring type is a dynamic type within a preset time, and determining a dynamic threshold value according to the third operating parameter.
[0103] In an embodiment of the present invention, the third operating parameter may be used to represent the operating information of a monitoring object of a dynamic type within a preset time in the past. The preset time may be the past week, month, year, etc., which may be determined based on experience. Here is an example: Assuming that the preset time is the past month, and the third operating parameter of the monitoring object is the daily registration volume, it can be found based on the third operating parameter in the past month that the daily registration volume on Saturdays is more than 10,000, and the daily registration volume at other times of the week is more than 1,000. Then, the dynamic threshold for subsequent Saturdays of each week can be set to 10,000, and the dynamic threshold for subsequent time periods of each week except Saturday can be set to 1,000.
[0104] Further, as an implementation of this embodiment, in step S324, the step of determining the dynamic threshold according to the third operating parameter may include: determining the dynamic threshold according to a preset probability threshold and the distribution of the third operating parameter within a preset time.
[0105] In the embodiment of the present invention, the probability threshold can be determined by experience. There is no specific limitation on the form of expression of the distribution of the third operating parameter within the preset time. For example, the distribution of the third operating parameter within the preset time can be represented by a chart, a curve, or a probability graph. Among them, the distribution of the third operating parameter within the preset time can be obtained, and the distribution can be segmented using a pre-set probability threshold to obtain the third operating parameter within the probability threshold range, and then the dynamic threshold is determined according to the third operating parameter within the probability threshold range.
[0106] Furthermore, when determining the dynamic threshold value according to the third operating parameter, the third operating parameter of the monitored object may be first obtained; the distribution of the data may be processed by the Laida criterion to obtain the normal distribution data of the third operating parameter within a preset time period; and the dynamic threshold value may be determined based on the pre-set probability threshold value and the normal distribution data. In order to more clearly understand the content of determining the dynamic threshold value, the following examples are listed:
[0107] The monitoring object is PV, and the PV in the past month is obtained. The PV in the past month is processed using the Laida criterion to obtain the normal distribution data of the third operating parameter in the past month. According to the normal distribution data, it is found that: the probability of the value being distributed in (μ-σ, μ+σ) is 0.6827, the probability of the value being distributed in (μ-2σ, μ+2σ) is 0.9545, and the probability of the value being distributed in (μ-3σ, μ+3σ) is 0.9973, where μ represents the standard deviation of the third operating parameter in the past month, and μ represents the average value of the third operating parameter in the past month. According to the normal distribution data, the third operating parameter in the past month is mainly concentrated in the interval of (μ-3σ, μ+3σ), and the possibility of exceeding this range is less than 0.3%. Therefore, 0.9973 can be used as the probability threshold, and the dynamic threshold is the maximum and minimum values of the third operating parameter in the interval of (μ-3σ, μ+3σ) processed by the Laida criterion. That is to say, when the value of the second operating parameter after being processed by the Laida criterion is within the interval (μ-3σ, μ+3σ), the monitoring result of the monitoring item corresponding to the second operating parameter is normal; when the value of the second operating parameter after being processed by the Laida criterion is outside the interval (μ-3σ, μ+3σ), the monitoring result of the monitoring item corresponding to the second operating parameter is abnormal.
[0108] It can be seen from the above examples that a dynamic threshold can be obtained according to the third operating parameter. It should be noted that the above example is only used as an example to illustrate the content of this embodiment. It is a way to generate a dynamic threshold based on the Laida criterion using past experience data. This method is suitable for the case when the amount of data of the third operating parameter is large. When the amount of data of the third operating parameter is small, the dynamic threshold can be obtained by using other probability threshold segmentation methods based on experience, and no specific restrictions are made here.
[0109] In this embodiment, through the implementation of determining the dynamic threshold based on the pre-set probability threshold and the distribution of the third operating parameter within the preset time, the dynamic threshold can be flexibly obtained based on the third operating parameter without the need to manually repeatedly set the threshold, which effectively reduces manpower and can fully utilize past data for prediction, thereby improving the accuracy of judging whether the monitoring item corresponding to the monitored object is abnormal.
[0110] Step S325: Determine the monitoring result of the monitoring item corresponding to the monitoring object whose monitoring type is the dynamic type according to the magnitude relationship between the second operating parameter and the dynamic threshold.
[0111] In the embodiment of the present invention, when the second operating parameter is greater than the dynamic threshold, the monitoring result of the monitoring item corresponding to the monitoring object is determined to be in an abnormal state; when the second operating parameter is less than or equal to the dynamic threshold, the monitoring result of the monitoring item corresponding to the monitoring object is determined to be in a normal state. It should be noted that this embodiment does not specifically limit the method for comparing the size between the second operating parameter and the dynamic threshold.
[0112] Take the example listed in the above step S234 for illustration: in the subsequent monitoring process, if the second operating parameter on Saturday is six thousand, which is less than the corresponding dynamic threshold, then the monitoring result of the monitoring item corresponding to the monitored object is determined to be abnormal; if the second operating parameter on Monday is three thousand, which is greater than the corresponding dynamic threshold, then the monitoring result of the monitoring item corresponding to the monitored object is determined to be normal.
[0113] In this embodiment, by implementing the above-mentioned steps S323 to S325, it is possible to determine whether the monitoring object of the dynamic type is abnormal, thereby obtaining the monitoring result, wherein the dynamic threshold can be generated over time, and the corresponding judgment standard can be adopted for the monitoring object of the dynamic type to improve the accuracy of the monitoring result judgment.
[0114] By implementing the fault location method of the above application system, each monitoring object in the application system can be monitored separately through monitoring items. When the monitoring result of a monitoring item is abnormal, the monitoring item is used as the first monitoring item, and the associated monitoring item with a preset association relationship with the first monitoring item is further obtained, and the fault source in the application system is obtained according to the monitoring result of the associated monitoring item, thereby realizing that each monitoring object in the application system is associated with each other, and each monitoring item is associated, so that when an abnormality occurs in one of the monitoring objects, the state of the monitoring object associated with the monitoring object can be further obtained, which greatly improves the accuracy of fault source location, and can assist operation and maintenance engineers to quickly locate the fault source of the production environment fault in complex monitoring items; it can also first obtain the first monitoring item to which Monitoring group, and then determine the associated monitoring items that have a preset association relationship with the first monitoring item based on the monitoring group to which it belongs. Since the relationship between the monitoring group and the monitoring item is preset, there is no need to traverse the query in the database, and then judge the relationship between other monitoring items and the first monitoring item one by one; it is also possible to configure the weight value of the monitoring item corresponding to the monitoring object in the monitoring item based on the application attributes of the monitoring object, so that when this embodiment is actually applied, the operation and maintenance engineer can configure the weight value of each monitoring item in the monitoring group to which it belongs according to various business characteristics; and it is possible to judge whether the monitoring object of the dynamic type is abnormal, so as to obtain the monitoring result, wherein the dynamic threshold can be generated over time, and the corresponding judgment standard can be adopted for the monitoring object of the dynamic type, so as to improve the accuracy of the judgment of the monitoring result.
[0115] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0116] An embodiment of the present invention provides a fault locating device for an application system, and the fault locating device for the application system roughly corresponds to the fault locating method for the application system provided above.
[0117] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0118] See also Fig. 9 , which shows a fault location device for an application system provided by an embodiment of the present invention, the fault location device for the application system is used to monitor the running status of multiple monitoring objects in the application system through multiple monitoring items, and the fault location device for the application system includes a first monitoring item acquisition module 410, an associated monitoring item acquisition module 420, a monitoring result acquisition module 430 and a fault source determination module 440. The functional modules are described in detail as follows:
[0119] The first monitoring item acquisition module 410 is used to take the monitoring item in the abnormal state as the first monitoring item when the monitoring result of any monitoring item is in an abnormal state; the associated monitoring item acquisition module 420 is used to obtain at least one associated monitoring item that has a preset association relationship with the first monitoring item; the monitoring result acquisition module 430 is used to obtain the monitoring results of the associated monitoring items, and the monitoring results of the associated monitoring items include a normal state and an abnormal state; and the fault source determination module 440 is used to determine the fault source of the application system according to the monitoring result, and output information including the fault source.
[0120] Further, as an implementation mode, the associated monitoring item acquisition module 420 in the fault location device of the application system may include a monitoring group determination unit and an associated monitoring item determination unit. Each functional unit is described in detail as follows: a monitoring group determination unit, used to determine the monitoring group to which the first monitoring item belongs, wherein the monitoring group includes the first monitoring item and one or more different second monitoring items, and the first monitoring item and each second monitoring item are respectively used to monitor a corresponding monitoring object; and an associated monitoring item determination unit, used to determine, according to the monitoring group, a second monitoring item that has a preset association relationship with the first monitoring item in one or more second monitoring items, and determine the second monitoring item that has a preset association relationship with the first monitoring item as an associated monitoring item.
[0121] Further, as an implementation mode, the fault source determination module 440 in the fault location device of the application system may include a weight value determination unit and a fault source determination unit. Each functional unit is described in detail as follows: a weight value determination unit, which is used to obtain a first weight value of a first monitoring item and a second weight value of the associated monitoring item in an abnormal state if the monitoring result of at least one of the associated monitoring items is an abnormal state; and a fault source determination unit, which is used to determine the fault source from multiple monitoring objects according to the first weight value and the second weight value, and the corresponding relationship between the associated monitoring items, the first monitoring item and the monitoring object, and output information including the fault source.
[0122] Furthermore, as an implementation method, the fault location device of the application system may also include a monitoring group acquisition module and a weight value configuration module. The functional modules are described in detail as follows: the monitoring group acquisition module is used to group each monitoring item to obtain at least one monitoring group; the weight value configuration module is used to configure the weight value of the monitoring item corresponding to the monitoring object in the monitoring item according to the application attribute of the monitoring object.
[0123] Further, as an implementation mode, the fault source determination module 440 in the fault location device of the application system may include a first fault source determination unit. The first fault source determination unit is described in detail as follows: the first fault source determination unit is used to determine that the monitoring object corresponding to the first monitoring item is a fault source if the monitoring results of each associated monitoring item are in a normal state, and output information including the fault source.
[0124] Furthermore, as an implementation method, the fault location device of the application system may also include a monitoring type acquisition module and a monitoring result determination module. The functional modules are described in detail as follows: a type acquisition module, used to obtain the type of each monitored object, including a static type and a dynamic type; a monitoring result determination module, used to analyze the operating parameters of each monitored object according to the monitoring type to obtain the monitoring results of the monitoring items corresponding to each monitored object.
[0125] Further, as an implementation mode, the monitoring result determination module in the fault location device of the application system may include a first operation parameter acquisition unit and a monitoring result determination unit. Each functional unit is described in detail as follows: the first operation parameter acquisition unit is used to acquire the first operation parameter of the monitoring object if the monitoring type of the monitoring object is a static type; the monitoring result determination unit is used to determine the monitoring result of the monitoring item corresponding to the monitoring object whose monitoring type is a static type according to the size relationship between the first operation parameter and a preset static threshold.
[0126] Furthermore, as an implementation method, the monitoring result determination module in the fault location device of the application system may also include a second operating parameter acquisition unit, a dynamic threshold determination unit, and a monitoring result confirmation unit. Each functional unit is described in detail as follows: a second operating parameter acquisition unit, for obtaining the second operating parameter of the monitored object if the monitoring type of the monitored object is a dynamic type; a dynamic threshold determination unit, for obtaining the third operating parameter of the monitored object whose monitoring type is a dynamic type within a preset time, and determining the dynamic threshold according to the third operating parameter; a monitoring result confirmation unit, for determining the monitoring result of the monitoring item corresponding to the monitored object whose monitoring type is a dynamic type according to the size relationship between the second operating parameter and the dynamic threshold.
[0127] Further, as an implementation mode, the above-mentioned dynamic threshold determination unit may include a third operation parameter acquisition subunit and a dynamic threshold determination subunit. Each functional subunit is described in detail as follows: the third operation parameter acquisition subunit is used to obtain the third operation parameter of the monitoring object whose monitoring type is dynamic type within a preset time. The dynamic threshold determination subunit is used to determine the dynamic threshold according to a preset probability threshold and the distribution of the third operation parameter within a preset time.
[0128] In addition, each functional module and functional unit in each embodiment of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. Each module and unit in the fault location device of the above integrated application system can be implemented in the form of hardware or in the form of software functional modules.
[0129] See also Fig.10 , which shows an electronic device 800 provided by an embodiment of the present invention, including: a processor 810, a communication module 820, a memory 830 and a bus. The processor 810, the communication module 820 and the memory 830 are connected to each other through the bus and communicate with each other. The bus can be an ISA bus, a PCI bus or an EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. Among them:
[0130] The memory 830 is used to store programs. Specifically, the memory 830 can be used to store software programs and various data. The memory 830 may mainly include a program storage area and a data storage area, wherein the program storage area can store application programs required to operate at least one function and may include program codes, and the program codes include computer operating instructions. In addition to storing programs, the memory 830 can also temporarily store messages that the communication module 820 needs to send, etc. The memory 830 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk storage.
[0131] The processor 810 is used to execute the program stored in the memory 830. When the program is executed by the processor, the steps of the permission-based smart device control method of each embodiment described above are implemented.
[0132] The embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, each process of the above-mentioned permission-based smart device control method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0133] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.
[0134] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods of various embodiments of the present invention.
[0135] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.
Claims
1. A method for locating a fault in an application system, characterized in that: The method is used to monitor the running status of multiple monitoring objects in an application system respectively through multiple monitoring items, wherein the application system includes multiple monitoring levels, each monitoring level includes one or more monitoring objects, and the method includes: performing grouping processing on the plurality of monitoring items to obtain at least one monitoring group; and According to the application attributes of the monitored object and the corresponding relationship between the monitored object and the monitored items, a weight value of each monitored item is configured; Acquire a monitoring type for each monitored object, the monitoring type including a static type and a dynamic type; the monitored object whose parameters of the judgment criterion do not change over time belongs to the static type, and the monitored object whose parameters of the judgment criterion change over time belongs to the dynamic type; and Analyze the operating parameters of each monitored object according to the monitoring type to obtain the monitoring results of the monitoring items corresponding to each monitored object; When the monitoring result is an abnormal state, the monitoring item in the abnormal state is used as the first monitoring item; Acquire at least one associated monitoring item that has a preset association relationship with the first monitoring item; Acquire monitoring results of the associated monitoring items, where the monitoring results of the associated monitoring items include normal status and abnormal status; and If the monitoring result of at least one of the associated monitoring items is in an abnormal state, obtaining a first weight value of the first monitoring item and a second weight value of the associated monitoring item in the abnormal state; and According to the first weight value and the second weight value, and the corresponding relationship between the associated monitoring item, the first monitoring item and the monitoring object, a fault source is determined from the plurality of monitoring objects, and information including the fault source is output.
2. The fault location method of the application system according to claim 1, characterized in that: The step of obtaining at least one associated monitoring item having a preset association relationship with the first monitoring item includes: Determine a monitoring group to which the first monitoring item belongs, wherein the monitoring group includes the first monitoring item and one or more different second monitoring items, and the first monitoring item and each of the second monitoring items are respectively used to monitor a corresponding monitoring object; and According to the monitoring group, a second monitoring item having the preset association relationship with the first monitoring item is determined from one or more of the second monitoring items, and the second monitoring item having the preset association relationship with the first monitoring item is determined as the associated monitoring item.
3. The fault location method of the application system according to claim 1, characterized in that: The method further comprises: If the monitoring results of each of the associated monitoring items are in a normal state, it is determined that the monitoring object corresponding to the first monitoring item is a fault source.
4. The fault location method of the application system according to claim 1, characterized in that: The step of analyzing the operating parameters of each of the monitored objects according to the monitoring type to obtain the monitoring results of the monitoring items corresponding to each of the monitored objects includes: If the monitoring type of the monitored object is a static type, obtaining a first operating parameter of the monitored object; and According to the magnitude relationship between the first operating parameter and a preset static threshold, a monitoring result of the monitoring item corresponding to the monitoring object whose monitoring type is a static type is determined.
5. The fault location method of the application system according to claim 1, characterized in that: The step of analyzing the operating parameters of each of the monitored objects according to the monitoring type to obtain the monitoring results of the monitoring items corresponding to each of the monitored objects includes: If the monitoring type of the monitored object is the dynamic type, obtaining a second operating parameter of the monitored object; Acquire a third operating parameter of the monitoring object whose monitoring type is dynamic within a preset time, and determine a dynamic threshold value according to the third operating parameter; and According to the magnitude relationship between the second operating parameter and the dynamic threshold, the monitoring result of the monitoring item corresponding to the monitoring object whose monitoring type is the dynamic type is determined.
6. The fault location method of the application system according to claim 5, characterized in that: The step of obtaining a third operating parameter of the monitoring object of a static monitoring type within a preset time, and obtaining a dynamic threshold value according to the third operating parameter comprises: Acquire a third operating parameter of the monitoring object whose monitoring type is a dynamic type within a preset time; and The dynamic threshold is determined according to a preset probability threshold and the distribution of the third operating parameter within the preset time.
7. A fault location device for an application system, characterized in that: The device is used to monitor the running status of multiple monitoring objects in the application system through multiple monitoring items, the application system includes multiple monitoring levels, each monitoring level includes one or more monitoring objects, and the device includes: A monitoring group acquisition module, used for grouping the plurality of monitoring items to obtain at least one monitoring group; A weight value configuration module, used to configure the weight value of each of the monitoring items according to the application attributes of the monitoring object and the corresponding relationship between the monitoring object and the monitoring items; A type acquisition module, used to acquire the monitoring type of each monitored object, wherein the monitoring type includes a static type and a dynamic type; the monitoring object whose parameters of the judgment criterion do not change over time belongs to the static type, and the monitoring object whose parameters of the judgment criterion change over time belongs to the dynamic type; A monitoring result determination module, used to analyze the operating parameters of each of the monitored objects according to the monitoring type to obtain the monitoring results of the monitoring items corresponding to each monitored object; A first monitoring item acquisition module, used for taking the monitoring item in the abnormal state as the first monitoring item when the monitoring result is in an abnormal state; An associated monitoring item acquisition module, used to acquire at least one associated monitoring item having a preset association relationship with the first monitoring item; A monitoring result acquisition module, used to acquire the monitoring result of the associated monitoring item, wherein the monitoring result of the associated monitoring item includes a normal state and an abnormal state; and A fault source determination module is used to obtain a first weight value of the first monitoring item and a second weight value of the associated monitoring item in an abnormal state if the monitoring result of at least one of the associated monitoring items is an abnormal state; and determine a fault source from a plurality of the monitored objects based on the first weight value and the second weight value, and the correspondence between the associated monitoring items, the first monitoring item and the monitored object, and output information including the fault source.
8. An electronic device, characterized in that: include: Memory; One or more processors coupled to the memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the method according to any one of claims 1-6.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program codes, which can be called by a processor to execute the method according to any one of claims 1 to 6.
