CN117389903A - Method, device and system for detecting abnormity of running environment of distributed combined application - Google Patents
Method, device and system for detecting abnormity of running environment of distributed combined application Download PDFInfo
- Publication number
- CN117389903A CN117389903A CN202311507191.6A CN202311507191A CN117389903A CN 117389903 A CN117389903 A CN 117389903A CN 202311507191 A CN202311507191 A CN 202311507191A CN 117389903 A CN117389903 A CN 117389903A
- Authority
- CN
- China
- Prior art keywords
- application
- distributed
- service
- availability
- determining
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000001514 detection method Methods 0.000 claims abstract description 106
- 230000002159 abnormal effect Effects 0.000 claims abstract description 30
- 238000012360 testing method Methods 0.000 claims description 35
- 230000005856 abnormality Effects 0.000 claims description 28
- 238000004590 computer program Methods 0.000 claims description 23
- 238000003860 storage Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 14
- 238000012935 Averaging Methods 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000013473 artificial intelligence Methods 0.000 abstract description 4
- 230000007613 environmental effect Effects 0.000 description 24
- 230000001419 dependent effect Effects 0.000 description 17
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 11
- 238000012827 research and development Methods 0.000 description 11
- 239000002131 composite material Substances 0.000 description 10
- 238000011144 upstream manufacturing Methods 0.000 description 9
- 238000011161 development Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 230000008859 change Effects 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 238000007689 inspection Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010960 commercial process Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a method, a device and a system for detecting abnormity of a distributed combined application running environment, which can be used in the technical field of artificial intelligence, and the method comprises the following steps: determining all distributed applications included in the distributed combined application according to the current time; determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application; and determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal or not according to the comprehensive availability. The method and the device consider that the comprehensive availability of the availability of each distributed application of the distributed combined application is obtained to judge whether the running environment is abnormal or not, and the detection accuracy of whether the running environment of the distributed combined application is available or not is improved.
Description
Technical Field
The invention relates to the technical field of distributed systems, in particular to the technical field of artificial intelligence, and particularly relates to a method, a device and a system for detecting abnormality of a distributed combined application running environment.
Background
This section is intended to provide a background or context to the embodiments of the application recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
Along with the gradual popularization of the distributed service technology, development pressure of large-scale distributed service system research and development enterprises is huge, and in order to rapidly realize business demands, the large-scale distributed service system research and development enterprises generally adopt project iteration, and project research and development support is realized in a mode of a plurality of sets of research and development environment alternation. In a large-scale distributed system, applications are generally divided into numerous applications and services in the form of distributed combined applications for independent development and operation.
Thus, in an actual development environment, the services do not exist independently, and the business functions of one distributed combined application often need to be completed by combining the services of a plurality of different distributed applications. Similarly, the successful verification of the business functions of a distributed combined application depends on the availability of multiple application environments. At present, the detection mode of the running environment of the distributed combined application in the distributed system does not consider the dependency relationship among services, and the accuracy of abnormality detection of the running environment of the distributed combined application needs to be improved.
Disclosure of Invention
An object of the present application is to provide a method for detecting an abnormality of an operating environment of a distributed combined application, which considers availability of each distributed application of the distributed combined application to obtain a comprehensive availability, and determines whether the operating environment is abnormal, thereby improving accuracy of detecting whether the operating environment of the distributed combined application is available. Another object of the present application is to provide a distributed combined application running environment anomaly detection device. It is yet another object of the present application to provide a distributed system. It is yet another object of the present application to provide a computer device. It is yet another object of the present application to provide a readable medium.
In order to achieve the above objective, an aspect of the present application discloses a method for detecting an anomaly of a running environment of a distributed combined application, including:
determining all distributed applications included in the distributed combined application according to the current time;
determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application;
and determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal or not according to the comprehensive availability.
Preferably, the determining all the distributed applications included in the distributed combined application according to the current time includes:
determining application names of all distributed applications included in the distributed combined application;
determining a target month version according to the current time;
and determining all distributed applications included by the distributed combined application according to the target month version, the application name and the application identifier of the distributed application, wherein the application identifier of the distributed application at least comprises the month version and the application name.
Preferably, the determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application includes:
determining the service called by each distributed application of the distributed combined application;
determining a corresponding detection application according to the service identifier of the service;
and calling the detection application to test the services of each distributed application according to the configuration information of the services to obtain corresponding availability.
Preferably, the determining the corresponding detection application according to the service identifier of the service includes:
determining a corresponding month version and a service name according to the service identifier of the service;
and determining the detection application corresponding to the service from a plurality of preset detection applications according to the month version and the service name.
Preferably, the calling the detection application to test the service of each distributed application according to the configuration information of the service to obtain the corresponding availability includes:
determining a corresponding month version to be tested according to the service identification of the service;
determining server deployment information of the service corresponding to the month version to be tested from the configuration information of the service;
and forming calling information according to the server deployment information, calling the detection application according to the calling information to test the service to obtain service availability, and obtaining the availability of each distributed application according to the service availability of all the services of each distributed application.
Preferably, the obtaining the availability of each distributed application according to the service availability of all services of each distributed application includes:
determining importance levels corresponding to all services included by each distributed application respectively;
determining an availability weight according to the importance level of the service;
and obtaining the availability of each distributed application according to the availability weight and the availability of all services of each distributed application.
Preferably, the determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability includes:
Determining the availability of all distributed applications corresponding to the distributed combined application according to the dependence relationship between the distributed combined application and each distributed application;
averaging the availability of all distributed applications results in a comprehensive availability of the distributed combined application.
Preferably, the determining whether the running environment of the distributed combined application has an abnormality according to the comprehensive availability includes:
and if the comprehensive availability is lower than a preset availability threshold, the running environment of the distributed combined application is abnormal.
Preferably, the method further comprises:
if the running environment of the distributed combined application is abnormal, determining whether the running environment of the monthly version of the distributed combined application before or after the current time is abnormal, and if not, routing the service request of the distributed combined application to the distributed combined application without the abnormality for processing.
The application also discloses a distributed combined application running environment abnormality detection device, which comprises:
the application analysis module is used for determining all the distributed applications included in the distributed combined application according to the current time;
the availability testing module is used for determining the service in each distributed application and the corresponding importance to obtain the availability of each distributed application;
And the running environment detection module is used for determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal according to the comprehensive availability.
The application also discloses a distributed system, which comprises the distributed combined application running environment abnormality detection device and a plurality of servers, wherein the distributed combined application comprises a distributed application, the distributed application calls at least one service, and the service is arranged on the servers.
The application also discloses a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method as described above when executing the computer program.
The application also discloses a computer readable storage medium storing a computer program which when executed by a processor implements a method as described above.
According to the method for detecting the running environment abnormality of the distributed combined application, all distributed applications included in the distributed combined application are determined according to the current time; determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application; and determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal or not according to the comprehensive availability. Therefore, the comprehensive availability of the distributed combined application is obtained according to the availability of each distributed application with a dependency relationship with the distributed combined application in consideration of the interdependence relationship between the distributed combined application and each distributed application. In addition, the method and the device consider the importance of the service of the distributed application to determine the availability of the distributed application, and improve the accuracy of the running environment anomaly detection of the distributed combined application.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
FIG. 1 is a schematic diagram of a distributed system provided in an embodiment of the present application;
FIG. 2 is a schematic flow chart of a method for detecting an abnormality of a running environment of a distributed combined application according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a method S100 for detecting an anomaly of a running environment of a distributed combined application according to an embodiment of the present application;
fig. 4 is a schematic flow chart of a method S200 for detecting an anomaly of a running environment of a distributed combined application according to an embodiment of the present application;
fig. 5 is a schematic flow chart of a method S220 for detecting an anomaly of a running environment of a distributed combined application according to an embodiment of the present application;
fig. 6 is a flowchart of a method S230 for detecting an anomaly of a running environment of a distributed combined application according to an embodiment of the present application;
Fig. 7 is a schematic flow chart of a method S233 for detecting an anomaly of a running environment of a distributed combined application according to an embodiment of the present application;
fig. 8 is a flowchart of a method S300 for detecting an anomaly of a running environment of a distributed combined application according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a distributed combined application running environment abnormality detection device according to an embodiment of the present application;
fig. 10 shows a schematic structural diagram of a computer device suitable for use in implementing embodiments of the present invention.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. The illustrative embodiments of the present application and their description are presented herein to illustrate the application and not to limit the application.
It should be noted that the method, the device and the system for detecting the abnormality of the running environment of the distributed combined application disclosed in the application can be used in the technical field of artificial intelligence, and can also be used in any field except the technical field of artificial intelligence.
It should be noted that, in one or more embodiments of the present application, taaS (Test as a Service ) service is a configurable, predictable end-to-end test service that integrates telecommunications domain knowledge, NFV domain knowledge, personnel services, and procedures. The TaaS service mainly provides a customized environment required by the test, guides or assists a third party manufacturer to complete activities such as testing, verification and the like in the environment, outputs a testable report, and accelerates the commercial process and speed of the tested system or product.
It should be noted that, in one or more embodiments of the present application, vue is a set of progressive JavaScript frames used to build user interfaces, and the developer only needs to pay attention to the view layer, which is not only easy to get on hand, but also facilitates integration with third party libraries or existing projects. Is based on MVVM (Model-View-ViewModel: view layer-View Model layer-Model layer) design concept. A library of bi-directional binding of MVVM data is provided, focusing on the UI level.
It should be noted that in one or more embodiments of the present application, the Element-Ui is a set of Ui component library that is not dependent on services and is implemented based on vue, providing rich PC-side components, reducing the packaging of common components by users, and reducing the difficulty of development. The Element-Ui is a component library based on vue encapsulation, so that encapsulation of common components is simplified, and reusability principle is improved.
Fig. 1 is a schematic structural diagram of a distributed system provided in an embodiment of the present application, and as shown in fig. 1, the distributed system provided in an embodiment of the present application includes a distributed combined application running environment anomaly detection device 1 and a plurality of distributed applications of the distributed combined application, where the distributed applications include at least one service, and each service is disposed on a server 2 of the distributed system.
The distributed combined application running environment abnormality detection device 1 is used for determining all distributed applications included in the distributed combined application according to the current time; determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application; and determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal or not according to the comprehensive availability.
Taking the distributed combined application running environment abnormality detection device 1 as an execution body as an example, the implementation process of the distributed combined application running environment abnormality detection method provided in the embodiment of the present application is described below. It can be understood that the execution body of the distributed combined application running environment abnormality detection method provided in the embodiment of the present application includes, but is not limited to, the distributed combined application running environment abnormality detection device.
According to one aspect of the application, the embodiment discloses a distributed combined application running environment anomaly detection method. As shown in fig. 2, in this embodiment, the method includes:
s100: all distributed applications included by the distributed combined application are determined according to the current time.
S200: determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application.
S300: and determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal or not according to the comprehensive availability.
According to the method for detecting the running environment abnormality of the distributed combined application, all distributed applications included in the distributed combined application are determined according to the current time; determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application; and determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal or not according to the comprehensive availability. Therefore, the comprehensive availability of the distributed combined application is obtained according to the availability of each distributed application with a dependency relationship with the distributed combined application in consideration of the interdependence relationship between the distributed combined application and each distributed application. In addition, the method and the device consider the importance of the service of the distributed application to determine the availability of the distributed application, and improve the accuracy of the running environment anomaly detection of the distributed combined application.
In an alternative embodiment, as shown in fig. 3, the determining, by S100, all the distributed applications included in the distributed combined application according to the current time includes:
s110: and determining application names of all distributed applications included by the distributed combined application.
S120: and determining the target month version according to the current time.
S130: and determining all distributed applications included by the distributed combined application according to the target month version, the application name and the application identifier of the distributed application, wherein the application identifier of the distributed application at least comprises the month version and the application name.
Specifically, it can be understood that all the distributed applications included in the distributed combined application can be determined through the preset dependency relationship between the distributed combined application and each distributed application.
The dependency relationship between the distributed combined application and each distributed application can be predefined by an operation and maintenance personnel, and the operation and maintenance personnel can set the dependency relationship between the distributed combined application and each distributed application in a manner of directly inputting or uploading a dependency relationship file and analyzing.
In addition, a preset automatic checking tool can be used for maintaining the dependency relationship view of the distributed combined application and each distributed application, and the Vue+element UI technology can be used for carrying out real-time maintenance on the dependency relationship in a template importing or manual interface adding, deleting or modifying mode so as to ensure that the dependency relationship change caused by business logic change can be updated to the automatic checking tool of the combined service environment in time. For example, initially, the environmental availability of a distributed combined application F-PRSA (personal settlement application in banking systems) was dependent on two critical applications, F-ECIS application (customer information application in banking systems) and F-BUIM application (accounting application in banking systems), respectively. When the dependency relationship is changed, the environmental availability of the distributed combined application F-PRSA (personal settlement application in a banking system) can be modified to depend on the environmental availability of three key applications, namely, F-ECIS application (customer information application in a banking system), F-BUIM application (accounting application in a banking system) and F-IPVS (business information application in a banking system), respectively.
Thus, the application names of all the distributed applications on which the distributed combined application depends can be determined according to the dependency relationship between the distributed combined application and the distributed application, for example, the application names of all the distributed applications on which the distributed combined application F-PRSA depends are F-PRSA, F-BUIM and F-IPVS, respectively. In addition, as each distributed application relied on by the distributed combined application develops corresponding month versions in different running environments according to different months, month versions are set in application identifiers of the distributed application relied on by the distributed combined application. And determining the month of the current time according to the current time, determining the month version corresponding to the month of the current time, and further determining all the distributed applications on which the distributed combined application of the current time depends according to the month version and the dependency relationship.
In an alternative embodiment, as shown in fig. 4, the determining, by S200, the availability of each distributed application according to the service and the importance of the service in each distributed application includes:
s210: and determining the service called by each distributed application of the distributed combined application.
S220: and determining a corresponding detection application according to the service identification of the service.
S230: and calling the detection application to test the services of each distributed application according to the configuration information of the services to obtain corresponding availability.
In particular, it can be appreciated that normal operation of the distributed application requires invocation of at least one service, and thus, the overall availability of the distributed application needs to be determined based on the availability of the service invoked by the distributed application.
When the availability test is performed, the detection application required by detection can be determined according to the service called by the distributed application, and the detection application is used for testing the availability of the service called by the distributed application according to the configuration information of the called service. In a specific example, when the distributed system is set on the TaaS platform, detection applications required for different service detection may be newly added or established on the TaaS platform. The service applications use a sending message to call the distributed service to be detected, capture certain keywords according to service return information, and judge that the service detection is not passed (service is not available) if the keywords are matched; if no keyword is matched, then the service detection passes (service is available). Because the services need to be respectively arranged in different development environments according to different month versions, the month versions are included in the service identifiers of the services, and corresponding detection applications for testing the services of different month versions also need to be identified according to the month versions and the services so as to determine the detection applications corresponding to the services of different month versions.
In an alternative embodiment, as shown in fig. 5, the determining, by S220, the corresponding detection application according to the service identifier of the service includes:
s221: and determining the corresponding month version and service name according to the service identifier of the service.
S222: and determining the detection application corresponding to the service from a plurality of preset detection applications according to the month version and the service name.
Specifically, the service identifier of the service includes a monthly version and a service name, and the identifier of the monthly version and the service name can be set for the detection application of the test service, so that the corresponding detection application can be determined according to the service identifier of the service to be tested. It should be noted that, specific program codes of the detection application of the test service can be configured by a person skilled in the art according to actual situations, which are conventional technical means in the art, and are not described herein again.
In an alternative embodiment, as shown in fig. 6, the step S230 of calling the detection application to test the service of each distributed application according to the configuration information of the service to obtain the corresponding availability includes:
s231: and determining a corresponding month version to be tested according to the service identifier of the service.
S232: and determining server deployment information of the service corresponding to the month version to be tested from the configuration information of the service.
S233: and forming calling information according to the server deployment information, calling the detection application according to the calling information to test the service to obtain service availability, and obtaining the availability of each distributed application according to the service availability of all the services of each distributed application.
In particular, it may be appreciated that services are typically provided on a server, and configuration information for all services may be predetermined, where the configuration information needs to include server deployment information for setting the service, and the server deployment information forms a call information call detection application to access a server for setting the service to test the service to determine an availability of the service.
For example, in a specific example, the configuration information may include the following:
1. group: application (or sub-application) name.
2. Detecting application names: the name of the application to be detected (the identification of the application to be detected).
3. The calling mode is as follows: two call modes, HTTP or RPC, are common in the industry.
4. zookeeper address: registry of distributed composition service (different month version use different registry).
5. Interface class full name: complete path and name of service.
6. Interface version: version numbers of services (the same service represents version upgrades with different version numbers).
7. The interface method comprises the following steps: there are multiple methods for a service to implement multiple specific functions.
8. Interface parameter type: and (5) uploading the format class of the message.
9. Request message: and calling the specific report message content of the service.
10. Decision key 1 … … N may not be invoked: the keyword for judging that the service is not available can be added/deleted/changed according to the actual requirement, and one or more keywords can be set. The tool will match these keywords based on the service return message information and if so, determine that the service is not available.
The operation flow of the detection application is that a tested request message is sent to a designated service of a registration center of a designated zookeeper address, after the service is called, the content of the sent message is processed and returned to the detection application, the detection application judges whether the messages are matched one by one according to a non-callable judgment keyword 1 … … N, if one of the messages is matched, the service is judged to be unavailable, and the detection is failed; if all do not match, the service is determined to be available and a pass is detected.
In an alternative embodiment, as shown in fig. 7, the step S233 of obtaining the availability of each distributed application according to the service availability of all the services of each distributed application includes:
S2331: and determining importance levels respectively corresponding to all the services included by each distributed application.
S2332: and determining the availability weight according to the importance level of the service.
S2333: and obtaining the availability of each distributed application according to the availability weight and the availability of all services of each distributed application.
Specifically, it can be understood that the detected applications are classified and assigned with weights according to the dependency relationship of each application and the importance of each application service in the combination service. The importance and criticality of each dependent service in the composite service is found to be different in the actual service scenario, so the detection applications need to be classified and given different weights. For example: some services are on a critical path, and if the service is not available, the service affects that most of combined services are not available, and the weight of the services is larger; some services are not on a critical path, and if the services are not available, the scope of influence is limited, and the weight of the services is smaller, so that the environment availability of the combined service application can be reflected more truly and effectively.
For example, in a specific example, service acsperaccountinginfo modification and service BosPerNetInfo in F-ECIS (customer information application in banking system) are service/interface to be invoked for 3-upstream and downstream application switch door transaction and switch door transaction of 1-present application, respectively, weights are 1 and 4, and if only service BosPerNetInfo availability is 100%, then F-ECIS (customer information application in banking system) environment availability is 80%. Service terllerCheckCcsiService and service ACSTelerAckWithOutTx in F-BUIM application (accounting application in banking system) are 4-service/interface that can cause testing bottleneck for upstream and downstream applications and 5-checkpoints that can cause testing working pain point, respectively, weight is 2 and 3, if ACSTelerAltRIBUTE. TerllerCheckWithOutTx availability is 100% for only service, and environment availability is 60% for F-BUIM application (accounting application in banking system).
In an alternative embodiment, as shown in fig. 8, the determining, by the S300, the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each of the distributed applications and the availability includes:
s311: and determining the availability of all the distributed applications corresponding to the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application.
S312: averaging the availability of all distributed applications results in a comprehensive availability of the distributed combined application.
In particular, whether the running environment of the distributed combined application is available or not needs to depend on whether the running environment of the corresponding distributed application is available or not. Thus, the availability of all distributed applications may be averaged to obtain a comprehensive availability of the distributed combined application. For example, in a specific example, the environmental availability of the composite service F-PRSA application (personal accounting application in a banking system) needs to depend on the availability of the F-ECIS (customer information application in a banking system) and the F-BUIM application (accounting application in a banking system), which are respectively 80% and 60%, the running environment availability of the distributed composite application is (80% +60%)/2=70%.
In an alternative embodiment, the determining, in S300, whether an abnormality exists in the running environment of the distributed combined application according to the integrated availability includes:
s320: and if the comprehensive availability is lower than a preset availability threshold, the running environment of the distributed combined application is abnormal.
Specifically, the comprehensive availability of the running environment of the distributed combined application reflects the processing capability of the distributed combined application for the service request, so that an availability threshold value of whether the running environment of the distributed combined application is available or not can be preset, and if the comprehensive availability of the distributed combined application is lower than the preset availability threshold value, the fact that the capability of the distributed combined application for processing the related service request is insufficient is indicated, and the running environment of the distributed combined application is abnormal. It should be noted that, the preset availability threshold may be set by a person skilled in the art according to actual requirements, which is not limited in this application.
In an alternative embodiment, the method further comprises:
s400: if the running environment of the distributed combined application is abnormal, determining whether the running environment of the monthly version of the distributed combined application before or after the current time is abnormal, and if not, routing the service request of the distributed combined application to the distributed combined application without the abnormality for processing.
It can be understood that when the running environment of the distributed combined application is abnormal, the distributed combined application of other available month versions of the distributed combined application before or after the current time can be determined to process the service request, so that when the switching of each month version is problematic, the service request can be routed to the distributed combined application of other available month versions for processing, and the correct uninterrupted processing of the service request is ensured.
The present application is further illustrated by a specific example. In this embodiment, the method for detecting the abnormality of the running environment of the distributed combined application may be implemented by the following steps:
step 101: each application adds/builds a detection application of the self application calling service on the TaaS platform. The detection applications use a sending message to call the distributed service to be detected, capture certain keywords according to service return information, and judge that the service is not detected (service is not available) if the keywords are matched; if no keyword is matched, then the service detection passes (service is available).
The distributed system may configure relevant information of the detection application and the test service through configuration information, which may include the following:
1. Group: application (or sub-application) name.
2. Detecting application names: the name of the application to be detected (the identification of the application to be detected).
3. The calling mode is as follows: two call modes, HTTP or RPC, are common in the industry.
4. zookeeper address: registry of distributed composition service (different month version use different registry).
5. Interface class full name: complete path and name of service.
6. Interface version: version numbers of services (the same service represents version upgrades with different version numbers).
7. The interface method comprises the following steps: there are multiple methods for a service to implement multiple specific functions.
8. Interface parameter type: and (5) uploading the format class of the message.
9. Request message: and calling the specific report message content of the service.
10. Decision key 1 … … N may not be invoked: the keyword for judging that the service is not available can be added/deleted/changed according to the actual requirement, and one or more keywords can be set. The tool will match these keywords based on the service return message information and if so, determine that the service is not available.
The operation flow of the detection application is that a tested request message is sent to a designated service of a registration center of a designated zookeeper address, after the service is called, the content of the sent message is processed and returned to the detection application, the detection application judges whether the messages are matched one by one according to a non-callable judgment keyword 1 … … N, if one of the messages is matched, the service is judged to be unavailable, and the detection is failed; if all do not match, the service is determined to be available and a pass is detected.
Step 102: each application detection application is deployed on the TaaS platform to automatically run in a mode of 'application + month version + detection application name', and a time interval for timing triggering is set. In large research and development enterprises, a system is split into a plurality of applications, each application is independently researched and issued, and in order to support rapid iterative development of projects, a plurality of research and development environments are usually developed and tested simultaneously, so that an automatic inspection tool for combined service environments deploys detection applications by taking 'application + month version + detection application name' as dimensions, and whether a certain service of a certain application in a certain month version is available or not can be rapidly and effectively detected by deploying the detection applications, and the environmental availability of the certain application in the certain month version is evaluated.
Step 103: the detection application of each service is automatically triggered and run at fixed time, the single application environment availability of each combined application is displayed on the TaaS platform, and the environment availability of each time period (30 minutes for example) of the day can be displayed by taking the application and month version as dimensions. If each detection application passes detection, the current time point of the whole application is detected as a green light, if a certain detection application does not pass detection, the whole application is displayed as a red marked E, the error exists, and an operation and maintenance person can repair the environment abnormal condition by checking the specific error of the red marked E.
Each application deploys detection applications with a service and month version as dimensions, each detection application has an independent switch, and can set "on detection" or "off detection". For the detection application of the open detection, the TaaS platform initiates a service request for service detection every fixed period of time (e.g., 30 minutes).
The detection results may be presented to an operation and maintenance person, for example, the F-PRSA application (personal settlement application in banking system) in the 2022 month 11 version at 2011 day 11 month 9 environmental availability, the detection period is: 30 minutes. Detection of a normal will be indicated by a "green light" and detection of an abnormality will be indicated by a "E" marked red, as in this example, there are two periods of abnormality "08: 30-09:00 'and 11:00-11:30', the detection of abnormal services is: F-PRSA (202211S month version F-PRSA-ACCESS group ATSMdium greement. AccountQuery interface can call state detection), environmental maintainer can click red 'E' to check specific error reporting information, and timely repair environmental error reporting.
Step 104: and according to the dependency relationship of each application, in the automatic inspection tool of the combined service environment, using the detection application deployed by each application to establish a combined service dependency relationship view. The combined service application uses the application as dimension according to the application service which needs to be called, uses the combined service environment automatic checking tool to establish the service dependency relationship view, and can establish the relationship by means of template import or manual interface addition/deletion/modification of each application service.
The front-end composite service dependency view sees that the environmental availability of the composite service F-PRSA application (personal settlement application in banking system) depends on the environmental availability of two key applications, F-ECIS application (customer information application in banking system) and F-BUIM application (accounting application in banking system), respectively. Among them, what is called in F-ECIS (customer information application in banking system) is service acsperaccountinginfofodify and service BosPerNetInfo, and what is called in F-BUIM application (accounting application in banking system) is service terllerchickiservice and service acshellerattribute. The background will call four service detection points of service AcsPerAccount InfoModify, service BosPerNetInfo, service TellerCheckCcsiService and service ACSTelelerA ttribute.
Step 105: according to the dependency relationship of each application and the importance of each application service in the combined service, classifying the service according to the importance to obtain the importance level of the service, and carrying out the weight assignment of the availability according to the importance level. The importance and criticality of each dependent service in the composite service is found to be different in the actual service scenario, so the detection applications need to be classified and given different weights. For example: some services are on a critical path, and if the service is not available, the service affects that most of combined services are not available, and the weight of the services is larger; some services are not on a critical path, and if the services are not available, the scope of influence is limited, and the weight of the services is smaller, so that the environment availability of the combined service application can be reflected more truly and effectively.
In an actual test scenario, different dependent application services have different importance and influence on the composite service. Therefore, the availability of the combined service application is given a certain availability weight according to the difference of the 'business detection point types' of the dependent application service, so that the availability of the combined service application is evaluated more accurately, the dependent service is divided into five importance levels, namely:
1-door opening and closing transactions for the present application.
2-core functions that can cause testing bottlenecks for the present application.
3-services/interfaces that the upstream and downstream applications need to invoke to switch door transactions.
4-service/interface that can cause testing bottlenecks for upstream and downstream applications.
5-checkpoints that would cause a test operating pain point.
The above five importance levels are respectively given according to the importance and influence thereof: 4. scores 5, 1, 2, 3. Longitudinally evaluate the combined service application availability = sigma state normal dependent service availability weight/sigma total dependent service availability weight for a certain period of time.
Step 106: each application detection application is automatically triggered to run at fixed time, and the environment availability of the combined service application is displayed in the combined service environment automatic checking tool. In the combined service environment automatic checking tool, the service detection condition of each dependent application under the combined service application is shown, and if each dependent application on which the combined service application depends passes the detection, the combined service application whole detection passing (the environment availability is 100%) in the period of time is shown; if the detection of a certain dependent application on which the combined service application depends is failed, the influence condition of the application on the whole combined service application is calculated according to the service classification and the weight assignment in the step 105, so that the combined service application environment availability in the time period is obtained.
The environmental availability of the combined service F-PRSA application (personal settlement application in banking system) depends on the environmental availability of two key applications, the F-ECIS application (customer information application in banking system) and the F-BUIM application (accounting application in banking system), respectively. The combined service F-PRSA application (personal settlement application in banking system) has a "green light" (availability 100%) for a period of time other than "12:00-12:30". In the period of "12:00-12:30", because the service acsPerAccountInfo modification and the service BosPerNetInfo in the F-ECIS (customer information application in the banking system) are the service/interface to be called by the 3-upstream and downstream application switch door transaction and the switch door transaction of the 1-present application, respectively, the weights are 1 and 4, respectively, and the environmental availability of the F-ECIS (customer information application in the banking system) is 80% according to the formula of step 105; service TellerCheckCcsiService and service ACSTellerAlaTithOutTx in F-BUIM application (accounting application in banking system) are 4-service/interface that can cause testing bottleneck for upstream and downstream applications and 5-checkpoint that can cause testing working pain point, respectively, so weights are 2 and 3, respectively, calculated according to the formula of step 105, environmental availability of F-BUIM application (accounting application in banking system) is 60%, environmental availability of combined service F-PRSA application (personal accounting application in banking system) is calculated according to the formula of step 105 to be 70%.
Step 107: for service freshness, when a service change occurs, the composite service dependency view may be maintained by an automated inspection tool in the composite service environment. Because in an actual usage scenario, the services that the combined service application depends on will change due to business requirement changes or technical modifications, for example: adding a certain dependent application service, or modifying a certain dependent application service, etc. In order to keep the service fresh, the automatic inspection tool for the combined service environment provides a maintenance function for the dependency relationship of the combined service, a user can use the automatic inspection tool for the combined service environment to maintain the view of the dependency relationship of the service, and the relationship maintenance can be carried out in a mode of adding/deleting/modifying the dependency service through a template import or a manual interface so as to ensure that the change of the dependency relationship caused by the change of business logic can be updated into the automatic inspection tool for the combined service environment in time.
The environmental availability of the combined service F-PRSA application (personal settlement application in banking system) is modified to depend on the environmental availability of three key applications, F-ECIS application (customer information application in banking system), F-BUIM application (accounting application in banking system) and F-IPVS (business information application in banking system), respectively. Wherein the service invoked by the F-IPVS application (the service information application in the banking system) is com.icbc.ipvs. service.ipvs5123, the combined service environment automatic checking tool background will incorporate the service com.icbc.ipvs. service.ipvs. ipvs. 5123 service detection point of the F-ipvs. application (the service information application in the banking system) into the combined service F-PRSA application (the personal settlement application in the banking system).
The environmental availability of the combined service F-PRSA application (personal settlement application in banking system) depends on the environmental availability of three key applications, F-ECIS application (customer information application in banking system), F-BUIM application (accounting application in banking system) and F-IPVS application (business information application in banking system), respectively. The combined service F-PRSA application (personal settlement application in banking system) has a "green light" (availability 100%) for a period of time other than "12:00-12:30". In the period of "12:00-12:30", because the service acsPerAccountInfo modification and the service BosPerNetInfo in the F-ECIS (customer information application in the banking system) are the service/interface to be called by the 3-upstream and downstream application switch door transaction and the switch door transaction of the 1-present application, respectively, the weights are 1 and 4, respectively, and the environmental availability of the F-ECIS (customer information application in the banking system) is 80% according to the formula of step 105; service TellerCheckCcsiService and service ACSTelerAltRattribute. TellerCheckWithOutTx in F-BUIM application (accounting application in banking system) are 4-service/interface that can cause testing bottleneck of upstream and downstream applications and 5-checkpoints that can cause testing working pain points, so weights are 2 and 3, respectively, and environmental availability of F-BUIM application (accounting application in banking system) is 60% according to the formula of step 105; the service com.ibc.ipvs.service.ipvs 5123 in the F-IPVS application (service information application in banking system) is a service/interface to be invoked for the 3-upstream and downstream application switch door transaction, so the weight is 5 respectively, the environmental availability of the F-IPVS application (service information application in banking system) is 100% calculated according to the formula of step 105, and the environmental availability of the composite service F-PRSA application (personal settlement application in banking system) is 80% calculated according to the formula of step 105.
Step 108: each application detection application is automatically triggered to run at fixed time, and the environment availability of the combined service application is displayed in the combined service environment automatic checking tool according to the updated combined service dependency relationship. According to the method and the device, the detection application of the application calling service is deployed to each research and development environment, so that the environment availability of each research and development environment of each application can be automatically monitored. However, the platform system can only detect that the environmental availability of a single application is in an actual development environment, but in the actual development environment, various services do not exist independently, and one business function often needs to be completed by combining services of a plurality of different applications. Similarly, the successful verification of a business function depends on the availability of multiple application environments. The existing TaaS service detection platform cannot detect and display the environment availability of the combined service according to an actual test scene. On the other hand, in the combined service, different dependent services have different importance according to the service logic link in the combined service, so that the different importance of each service needs to be fully considered for classification when the research and development environment availability is calculated, and different weights are given, so that the research and development environment availability can be calculated more accurately and objectively. This aspect is also lacking in the prior art.
From a business perspective, the application monitoring system and the application monitoring method support the availability of the combined service application monitoring environment by establishing the combined service dependency relationship view, are more in line with the health state of the research and development and production environment, and improve the first-line user experience. According to the method and the device, different weights are defined for the service detection point types of transactions such as key services, door opening services and the like, and the weight definition principle is that the more key and bottleneck services are provided, so that a set of evaluation indexes for accurately measuring the environment availability is provided, and the environment availability can be measured more accurately. In addition, the method and the system support service freshness preservation, and users can update the dependent environment elements of the combined service environment timely and rapidly by maintaining the view of the dependent relationship of the combined service, so that the latest combined service environment availability can be reflected accurately and objectively.
Based on the same principle, the application also discloses a distributed combined application running environment abnormality detection device. As shown in fig. 9, the apparatus includes an application parsing module 11, an availability testing module 12, and a running environment detecting module 13.
The application parsing module 11 is configured to determine all distributed applications included in the distributed combined application according to the current time.
The availability test module 12 is configured to determine the availability of each distributed application based on the service and the importance of the service.
The running environment detection module 13 is configured to determine a comprehensive availability of the distributed combined application according to a dependency relationship between the distributed combined application and each of the distributed applications and an availability, and determine whether the running environment of the distributed combined application is abnormal according to the comprehensive availability.
Since the principle of the device for solving the problem is similar to that of the above method, the implementation of the device can be referred to the implementation of the method, and will not be described herein.
The embodiment of the application also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the method when executing the computer program.
Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements the above method.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program to produce a system, apparatus, module, or unit of the embodiments described above, which may be implemented in particular by a computer chip or entity, or by an article of manufacture having some function. A typical implementation device is a computer device, which may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
In a typical example, the computer apparatus includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program to implement a method performed by a client as described above, or where the processor executes the program to implement a method performed by a server as described above.
Referring now to FIG. 10, there is illustrated a schematic diagram of a computer device 600 suitable for use in implementing embodiments of the present application.
As shown in fig. 10, the computer apparatus 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate works and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data required for the operation of the system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a liquid crystal feedback device (LCD), and the like, and a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 606 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on drive 610 as needed, so that a computer program read therefrom is mounted as needed as storage section 608.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, 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 specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.
Claims (13)
1. The method for detecting the abnormal running environment of the distributed combined application is characterized by comprising the following steps of:
determining all distributed applications included in the distributed combined application according to the current time;
determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application;
and determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal or not according to the comprehensive availability.
2. The method for detecting an abnormality in a running environment of a distributed combined application according to claim 1, wherein the determining all distributed applications included in the distributed combined application according to the current time includes:
determining application names of all distributed applications included in the distributed combined application;
determining a target month version according to the current time;
and determining all distributed applications included by the distributed combined application according to the target month version, the application name and the application identifier of the distributed application, wherein the application identifier of the distributed application at least comprises the month version and the application name.
3. The method for detecting abnormal running environment of distributed combined applications according to claim 1, wherein determining the service and the corresponding importance in each distributed application to obtain the availability of each distributed application comprises:
determining the service called by each distributed application of the distributed combined application;
determining a corresponding detection application according to the service identifier of the service;
and calling the detection application to test the services of each distributed application according to the configuration information of the services to obtain corresponding availability.
4. The method for detecting abnormal running environment of distributed combined application according to claim 3, wherein the determining the corresponding detection application according to the service identifier of the service comprises:
determining a corresponding month version and a service name according to the service identifier of the service;
and determining the detection application corresponding to the service from a plurality of preset detection applications according to the month version and the service name.
5. The method for detecting abnormal running environment of distributed combined application according to claim 3, wherein the calling the detection application to test the service of each distributed application according to the configuration information of the service to obtain the corresponding availability comprises:
Determining a corresponding month version to be tested according to the service identification of the service;
determining server deployment information of the service corresponding to the month version to be tested from the configuration information of the service;
and forming calling information according to the server deployment information, calling the detection application according to the calling information to test the service to obtain service availability, and obtaining the availability of each distributed application according to the service availability of all the services of each distributed application.
6. The method for detecting abnormal running environment of distributed combined applications according to claim 3, wherein the obtaining the availability of each distributed application according to the service availability of all services of each distributed application comprises:
determining importance levels corresponding to all services included by each distributed application respectively;
determining an availability weight according to the importance level of the service;
and obtaining the availability of each distributed application according to the availability weight and the availability of all services of each distributed application.
7. The method for detecting an abnormality in a running environment of a distributed combined application according to claim 1, wherein the determining a comprehensive availability of the distributed combined application according to a dependency relationship between the distributed combined application and each of the distributed applications and an availability includes:
Determining the availability of all distributed applications corresponding to the distributed combined application according to the dependence relationship between the distributed combined application and each distributed application;
averaging the availability of all distributed applications results in a comprehensive availability of the distributed combined application.
8. The method for detecting an abnormality in an operating environment of a distributed combined application according to claim 1, wherein said determining whether an abnormality exists in an operating environment of the distributed combined application according to the comprehensive availability includes:
and if the comprehensive availability is lower than a preset availability threshold, the running environment of the distributed combined application is abnormal.
9. The method for detecting an anomaly in a running environment of a distributed combined application according to claim 1, further comprising:
if the running environment of the distributed combined application is abnormal, determining whether the running environment of the monthly version of the distributed combined application before or after the current time is abnormal, and if not, routing the service request of the distributed combined application to the distributed combined application without the abnormality for processing.
10. A distributed combined application operating environment anomaly detection device, comprising:
The application analysis module is used for determining all the distributed applications included in the distributed combined application according to the current time;
the availability testing module is used for determining the service in each distributed application and the corresponding importance to obtain the availability of each distributed application;
and the running environment detection module is used for determining the comprehensive availability of the distributed combined application according to the dependency relationship between the distributed combined application and each distributed application and the availability, and determining whether the running environment of the distributed combined application is abnormal according to the comprehensive availability.
11. A distributed system comprising the distributed combined application running environment anomaly detection device of claim 10 and a plurality of servers, the distributed combined application comprising a distributed application that invokes at least one service disposed on the servers.
12. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 9 when executing the computer program.
13. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311507191.6A CN117389903A (en) | 2023-11-13 | 2023-11-13 | Method, device and system for detecting abnormity of running environment of distributed combined application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311507191.6A CN117389903A (en) | 2023-11-13 | 2023-11-13 | Method, device and system for detecting abnormity of running environment of distributed combined application |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117389903A true CN117389903A (en) | 2024-01-12 |
Family
ID=89439128
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311507191.6A Pending CN117389903A (en) | 2023-11-13 | 2023-11-13 | Method, device and system for detecting abnormity of running environment of distributed combined application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117389903A (en) |
-
2023
- 2023-11-13 CN CN202311507191.6A patent/CN117389903A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11068383B2 (en) | Service oriented architecture infrastructure for business process verification and systems integrated testing | |
| US10277622B2 (en) | Enterprise level cybersecurity automatic remediation | |
| EP2333669B1 (en) | Bridging code changes and testing | |
| US20160357660A1 (en) | Early risk identification in devops environments | |
| JP2018185808A (en) | Apparatus for and method of testing smart agreement based on block chain | |
| US20070006041A1 (en) | Analytical regression testing on a software build | |
| AU2014202907A1 (en) | Migration Assessment for Cloud Computing Platforms | |
| US10241902B2 (en) | Systems and methods for benchmark based cross platform service demand prediction | |
| CN110007921B (en) | Code publishing method and device | |
| Bertolino et al. | DevOpRET: Continuous reliability testing in DevOps | |
| US11169910B2 (en) | Probabilistic software testing via dynamic graphs | |
| Pulnil et al. | A microservices quality model based on microservices anti-patterns | |
| JP2022100301A (en) | Method for determining potential impact on computing device by software upgrade, computer program, and update recommendation computer server (recommendation of stability of software upgrade) | |
| CN109274533B (en) | Web service fault positioning device and method based on rule engine | |
| US11790249B1 (en) | Automatically evaluating application architecture through architecture-as-code | |
| CN117389903A (en) | Method, device and system for detecting abnormity of running environment of distributed combined application | |
| Senivongse et al. | A maintainability assessment model for service-oriented systems | |
| Winzinger et al. | Automatic test case generation for serverless applications | |
| EP3639130A1 (en) | Enterprise level cybersecurity automatic remediation | |
| US10324821B2 (en) | Oracle cemli analysis tool | |
| CN114285756A (en) | Service call dependency relationship analysis method and related device | |
| CN112631906A (en) | Page performance detection method and system based on server | |
| KR100775102B1 (en) | Quality test result estimate system of platform based application on embedded device and method thereof | |
| CN118158135A (en) | Cluster performance test method and device, electronic equipment and computer readable storage medium | |
| CN116414642A (en) | Function test method and related device of service node |
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 |