CN111143151A - Service monitoring method and device and electronic equipment - Google Patents
Service monitoring method and device and electronic equipment Download PDFInfo
- Publication number
- CN111143151A CN111143151A CN201811300610.8A CN201811300610A CN111143151A CN 111143151 A CN111143151 A CN 111143151A CN 201811300610 A CN201811300610 A CN 201811300610A CN 111143151 A CN111143151 A CN 111143151A
- Authority
- CN
- China
- Prior art keywords
- service
- interface
- service interface
- detected
- dependency relationship
- 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.)
- Granted
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 75
- 238000000034 method Methods 0.000 title claims abstract description 55
- 230000002159 abnormal effect Effects 0.000 claims abstract description 104
- 230000004044 response Effects 0.000 claims abstract description 87
- 238000001514 detection method Methods 0.000 claims abstract description 81
- 238000012806 monitoring device Methods 0.000 claims description 7
- 230000008676 import Effects 0.000 claims description 4
- 238000000605 extraction Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 28
- 230000008569 process Effects 0.000 description 12
- 230000008030 elimination Effects 0.000 description 8
- 238000003379 elimination reaction Methods 0.000 description 8
- 230000005856 abnormality Effects 0.000 description 7
- 238000013024 troubleshooting Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000012795 verification Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000011156 evaluation Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a service monitoring method, which comprises the following steps: acquiring a service interface which has a dependency relationship with a service to be detected; transmitting detection parameters to the service interface according to the parameter input standard of the service interface; and judging whether the response parameters returned by the service interface meet the detection response reference, and if not, recording abnormal information of the abnormal service interface which does not meet the detection response reference. According to the service monitoring method, the service interface with the dependency relationship of the service to be detected is determined by deeply analyzing the service to be detected, so that the limitation of a black box of the service interface is broken, the abnormity of the service to be detected can be accurately positioned, the fault can be rapidly eliminated on the basis of the accurate positioning, and the influence on the service is avoided.
Description
Technical Field
The present application relates to the field of network technologies, and in particular, to a service monitoring method. The application also relates to a service monitoring device and an electronic device.
Background
With the development of networks, network resources are more and more, and many application services are arranged at a server side and provide access to external application services, such as an online login service, an online payment service, and the like. Generally, an application service deployed at a server side is formed by combining a plurality of sub-application services, and different sub-application services provide different functions and exist independently; meanwhile, each sub-application service is maintained by different teams and business units, and optimization and online of the application are necessary items due to business/technical development requirements; in addition, the service interface of the application service provided by the server needs to be guaranteed in stability, otherwise, the service accessing the application service downstream is affected.
At present, a technical means for performing stability detection on an online application service is mainly to monitor whether the online application service is alive or not by analyzing a parameter response returned by the online application service, but the current stability detection technical means is separated from an online application service business, a problem node with an abnormal online application service cannot be timely located, more consideration is not given to abnormal troubleshooting and recovery, an abnormal troubleshooting path is complex, great trouble is caused to the stability of the online application service, and meanwhile, the user experience and business income are influenced because the abnormality of the online application service cannot be timely repaired.
Therefore, how to quickly sense and locate the abnormal node of the online application service becomes a problem to be solved urgently.
Disclosure of Invention
The application provides a service monitoring method to solve the defects in the prior art. The application also relates to a service monitoring device and an electronic device.
The application provides a service monitoring method, which comprises the following steps:
acquiring a service interface which has a dependency relationship with a service to be detected;
transmitting detection parameters to the service interface according to the parameter input standard of the service interface;
and judging whether the response parameters returned by the service interface meet the detection response reference, and if not, recording abnormal information of the abnormal service interface which does not meet the detection response reference.
Optionally, the acquiring a service interface having a dependency relationship with a service to be detected includes:
splitting the service to be detected into at least one service domain by taking the service domain as a splitting dimension;
combining the service domains according to the service dependency relationship among the service domains;
and extracting a service interface contained in the service link obtained by the service domain combination as the service interface having a dependency relationship with the service to be detected.
Optionally, the service interfaces have a dependency relationship therebetween; and, a plurality of service interfaces with mutual dependency relationship belong to the same service domain, or a plurality of service interfaces with mutual dependency relationship belong to different service domains.
Optionally, the service interface having a dependency relationship with the service to be detected includes at least one of the following:
and the service interface to be detected comprises at least one service interface, and at least one third-party service interface which has strong dependency relationship with the service interface to be detected.
Optionally, the acquiring a service interface having a dependency relationship with a service to be detected includes:
performing strong dependency analysis on a service interface and/or the third-party service interface included in the service to be detected to obtain a strong dependency relationship between the service interface and/or the third-party service interface included in the service to be detected;
and extracting the service interface contained in the service to be detected and/or a third party service interface having a strong dependency relationship with the service interface contained in the service to be detected according to the strong dependency relationship.
Optionally, the strong dependency relationship between the service interfaces included in the service to be detected and/or the third-party service interfaces is embodied based on the call path and the timing relationship of the service interfaces included in the service to be detected and/or the third-party service interfaces.
Optionally, the transmitting the detection parameter to the service interface according to the parameter input standard of the service interface includes:
and inputting detection parameters matched with the respective corresponding parameter input standards to the service interface contained in the service to be detected and/or the third-party service interface according to the calling path and the time sequence relationship and according to the respective corresponding parameter input standards of the service interface contained in the service to be detected and/or the third-party service interface.
Optionally, after the step of transmitting the detection parameter to the service interface according to the parameter input standard of the service interface is executed, and before the step of determining whether the response parameter returned by the service interface meets the detection response reference is executed, the following operations are executed:
acquiring a response parameter returned by the service interface;
wherein the response parameter includes at least one of: response parameter type, response parameter information.
Optionally, the recording of the abnormal information of the abnormal service interface that does not meet the detection response reference includes:
uploading the abnormal service interface by calling an abnormal reporting interface;
and recording the abnormal field information of the abnormal service interface.
Optionally, the service monitoring method is executed based on a monitoring module, and the monitoring module initiates scheduling at regular time by a distributed timing task module.
The present application further provides a service monitoring apparatus, including:
a service interface obtaining unit, configured to obtain a service interface having a dependency relationship with a service to be detected;
the detection parameter transmitting unit is used for transmitting detection parameters to the service interface according to the parameter input standard of the service interface;
a response parameter judging unit, configured to judge whether a response parameter returned by the service interface meets a detection response criterion, and if not, run an exception recording unit;
and the abnormal recording unit is used for recording abnormal information of the abnormal service interface which does not accord with the detection response reference.
Optionally, the service interface obtaining unit includes:
a service domain splitting subunit, configured to split the service to be detected into at least one service domain with the service domain as a splitting dimension;
the service domain combination subunit is used for combining the service domains according to the service dependency relationship among the service domains;
and the service interface extraction subunit is used for extracting the service interface contained in the service link obtained by the service domain combination and taking the service interface as the service interface which has a dependency relationship with the service to be detected.
Optionally, the service interfaces have a dependency relationship therebetween; and, a plurality of service interfaces with mutual dependency relationship belong to the same service domain, or a plurality of service interfaces with mutual dependency relationship belong to different service domains.
Optionally, the service interface having a dependency relationship with the service to be detected includes at least one of the following:
and the service interface to be detected comprises at least one service interface, and at least one third-party service interface which has strong dependency relationship with the service interface to be detected.
Optionally, the service interface obtaining unit includes:
the strong dependence analysis subunit is configured to perform strong dependence analysis on the service interface included in the service to be detected and/or the third-party service interface, and obtain a strong dependence relationship between the service interface included in the service to be detected and/or the third-party service interface;
and the extracting subunit is used for extracting the service interface contained in the service to be detected and/or the third-party service interface with strong dependency relationship with the service interface contained in the service to be detected according to the strong dependency relationship.
Optionally, the strong dependency relationship between the service interfaces included in the service to be detected and/or the third-party service interfaces is embodied based on the call path and the timing relationship of the service interfaces included in the service to be detected and/or the third-party service interfaces.
Optionally, the detection parameter importing unit is specifically configured to import, according to the call path and the time sequence relationship and according to respective corresponding parameter input standards of the service interface included in the service to be detected and/or the third-party service interface, the detection parameter matching the respective corresponding parameter input standard to the service interface included in the service to be detected and/or the third-party service interface.
The present application further provides an electronic device, comprising:
a memory and a processor; the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to: acquiring a service interface which has a dependency relationship with a service to be detected; transmitting detection parameters to the service interface according to the parameter input standard of the service interface; and judging whether the response parameters returned by the service interface meet the detection response reference, and if not, recording abnormal information of the abnormal service interface which does not meet the detection response reference.
Compared with the prior art, the method has the following advantages:
the service monitoring method provided by the application comprises the following steps: acquiring a service interface which has a dependency relationship with a service to be detected; transmitting detection parameters to the service interface according to the parameter input standard of the service interface; and judging whether the response parameters returned by the service interface meet the detection response reference, and if not, recording abnormal information of the abnormal service interface which does not meet the detection response reference.
The business monitoring method comprises the steps of determining a business interface with a dependency relationship of a business to be detected by deeply analyzing the business to be detected, breaking through the limitation of a black box of the business interface, transmitting corresponding detection parameters to the business interface according to the parameter input standard of the business interface, further judging whether returned response parameters meet expectations to judge whether business processing of the business interface is abnormal or not, recording abnormal information of the abnormal business interface with abnormal business processing if the business processing of the business interface is abnormal, and taking the abnormal information as a basis for carrying out abnormal troubleshooting and repairing, so that the abnormal business to be detected can be accurately positioned, faults can be rapidly eliminated on the basis of accurate positioning, and the influence on the business is avoided.
Drawings
Fig. 1 is an execution flow chart of a service monitoring method provided in the present application;
FIG. 2 is a timing diagram of a log-in service monitoring provided by the present application;
FIG. 3 is a schematic diagram of an embodiment of a traffic monitoring apparatus provided in the present application;
fig. 4 is a schematic diagram of an electronic device provided by the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The application provides a business monitoring method, a business monitoring device and electronic equipment. The following detailed description and the description of the steps of the method are individually made with reference to the drawings of the embodiments provided in the present application.
The embodiment of the service monitoring method provided by the application is as follows:
referring to fig. 1, a flow chart of a service monitoring method according to the present application is shown, and referring to fig. 2, a timing chart of login service monitoring according to the present application is shown.
And S101, acquiring a service interface which has a dependency relationship with the service to be detected.
In practical application, an online service deployed at a server end often consists of sub-services maintained by a plurality of service teams or service units, each sub-service has a service interface thereof, and data docking is performed with other services or sub-services through the service interface or with a third-party service interface through the service interface.
The service monitoring method provided by the application takes the service to be detected deployed on the line of the server as an example, and deeply analyzes the service to be detected, so as to determine all service interfaces with dependency relationship with the service to be detected. On the basis of determining a service interface contained in a service to be detected and a third-party service interface with a strong dependence relationship with the service interface, respectively transmitting corresponding detection parameters to the service interface of the service to be detected and the third-party service interface according to respective parameter input standards of the service interface of the service to be detected and the third-party service interface, and after the detection parameters are transmitted to the service interface of the service to be detected and the third-party service interface, processing by respective service execution units of the service interface of the service to be detected and the third-party service interface and then returning corresponding response parameters; and finally, judging whether the service interface of the service to be detected and the third-party service interface can perform service processing and whether the service processing is normal according to the returned response parameters, if the service processing cannot be performed or is abnormal, indicating that the service of the service interface of the service to be detected or the third-party service interface is abnormal, recording the field abnormal information of the abnormal service interface, transmitting the recorded abnormal information to a service team or a service unit in charge of the abnormal processing, and further performing abnormal troubleshooting and repairing according to the recorded abnormal information, so that the abnormal condition of the service to be detected can be accurately positioned, faults can be rapidly eliminated on the basis of the accurate positioning, and the influence on the service is avoided.
It should be noted that, according to the above characteristics of the service to be detected on the line deployed at the server, the service monitoring method provided by the present application is used to perform stability monitoring on the service deployed at the server, so that the technical effect of implementation can be embodied to the greatest extent, that is: the method and the device can accurately position the abnormity of the service to be detected, and can quickly remove the fault on the basis of accurate positioning. In addition, the service monitoring method provided by the application can be popularized to a scene of the characteristic type of the service deployed at the server side for implementation, and the effects of abnormal quick positioning and fault quick elimination can be achieved.
The service monitoring method provided by the embodiment of the application is executed based on the monitoring service module, specifically, the monitoring service module is scheduled by the distributed timing task module, so that under the scheduling of the distributed timing task module, the stability monitoring and the fault quick positioning elimination of the service to be detected are started regularly. As shown in fig. 2, the distributed timed task module is provided with a timer, the distributed timed task module initiates scheduling to the monitoring service module at regular time, and the monitoring service module starts stability monitoring and fault fast positioning and removing of the to-be-detected service on the line after receiving the scheduling issued by the distributed timed task module.
Further, under the condition that the computing capacity allows, for example, when the stability monitoring and the rapid fault location elimination of the service to be detected are performed in the cloud computing environment, the stability monitoring and the rapid fault location elimination of the service to be detected can be accelerated by shortening the timing scheduling period of the distributed timing task module initiating scheduling to the monitoring service module, so that the rapid fault location elimination of the service to be detected on the line is more timely. For example, when the timing scheduling period of the distributed timing task module initiating scheduling to the monitoring service module is reduced to the level of seconds, milliseconds or even microseconds, the distributed timing task module can even perform 'quasi-real-time' monitoring and fault quick positioning and removing on the operations of service change of the service to be detected on the line, operation and maintenance on the line and the like.
In the specific implementation, in the process of stability monitoring and fault fast positioning elimination of the service to be detected, a service interface having a dependency relationship with the service to be detected needs to be acquired, that is, a service range targeted for stability detection and abnormal fast positioning elimination is determined. However, in an actual service scenario, for a service to be detected with a long link, the existing situation is complex, and not only is the service connection among many sub-services in the link tight, especially embodied in a complete transaction service link (full link service), the updating of the pre-function of the full link service may cause a problem to be expressed in the foreground, and it is difficult to locate the cause of the abnormality in time, but also the connection between service teams or service units responsible for maintaining the sub-services of the full link service is tight, and it is difficult to split the service link of the full link service forcibly.
In an embodiment of the present application, from a service perspective of a service to be detected, splitting the service to be detected with a service domain as a dimension, specifically, acquiring a service interface having a dependency relationship with the service to be detected includes: splitting the service to be detected into at least one service domain by taking the service domain as a splitting dimension; combining the service domains according to the service dependency relationship among the service domains; and extracting the service interface contained in the service link obtained by the service domain combination, wherein the service interface contained in the extracted service link is the service interface which has a dependency relationship with the service to be detected.
Taking the online transaction service as an example, a complete transaction service link includes operations from registration, login, merchandise display, order processing, payment, logistics express delivery, order evaluation, goods return, refund and the like, different operations may be maintained by different teams, a complete transaction service link (full link service) may be maintained by a plurality of teams or even dozens of teams of different links, and from the service perspective, a complete transaction service link (full link service) is sequentially divided into the following service domains: a login domain, a goods domain, a payment domain, a logistics domain, an evaluation domain and an after-sales service domain.
Preferably, the service interfaces further have a dependency relationship, for example, the service interface of the commodity display operation in the transaction service link has a strong dependency relationship with the service interface of the login operation, and if the service interface of the login operation is abnormal, the service interface of the subsequent commodity display operation cannot be invoked and executed; similarly, the business interfaces for order processing, payment, etc. operations also have strong dependencies with the business interfaces for login operations. Moreover, a plurality of service interfaces with dependency relationship can belong to the same service domain, for example, the service interface of login operation and the service interface of registration operation have strong dependency relationship, and both of them belong to the same service domain, that is, the login domain; in addition, a plurality of service interfaces with mutual dependency relationship can also belong to different service domains, for example, a service interface for payment operation and a service interface for login operation have strong dependency relationship, and both of them belong to different service domains together, wherein the service interface for login operation belongs to the login domain, and the service interface for payment operation belongs to the payment domain.
The preferred embodiment provided above mainly processes a full link service scene, and in addition, a single service scene with an independent service processing link also exists in an actual service scene, and under the service scene, a service interface having a dependency relationship with a service to be detected can be deeply analyzed in a targeted manner, so that the limitation of a black box of the service interface is broken, the unavailability of the service due to the occurrence of an abnormality of a strongly dependent service interface is monitored in time, and accurate positioning is performed before the occurrence of the abnormality, so as to repair the abnormality. In another preferred embodiment, the embodiment of the present application provides that the service interface having a dependency relationship with the service to be detected is obtained, and the following method is specifically adopted: carrying out strong dependence analysis on a service interface and/or a third-party service interface included in the service to be detected to obtain a strong dependence relationship between the service interface and/or the third-party service interface included in the service to be detected; and extracting a service interface contained in the service to be detected and a third party service interface having a strong dependency relationship with the service interface contained in the service to be detected according to the strong dependency relationship.
Preferably, the strong dependency relationship between the service interfaces and/or the third-party service interfaces included in the service to be detected is embodied based on the call path and the time sequence relationship of the service interfaces and/or the third-party service interfaces included in the service to be detected. For example, a timing chart between the service interface included in the service to be detected and the third-party service interface is generated by analyzing the strong dependence of the service interface included in the service to be detected and the third-party service interface, and a call path and a timing relation between the service interfaces included in the service to be detected and the third-party service interface, and a call path and a timing relation between the service interface included in the service to be detected and the third-party service interface are reflected by the timing chart.
And step S102, transmitting detection parameters to the service interface according to the parameter input standard of the service interface.
In practical application, according to the fact that a service interface included in a service to be detected and a service interface depended by a third party service interface are different or the third party service interface is different, detection parameters transmitted to the service interface and the third party service interface may also be different from each other, and each service interface and the third party service interface have own parameter input standards. Based on this, in a preferred implementation manner provided by the embodiment of the present application, according to the determined call path and time sequence relationship of the service interface and/or the third-party service interface included in the service to be detected, the detection parameters are sequentially transmitted according to the call path and the time sequence relationship for detection. Specifically, in the process of transmitting the detection parameters, according to the respective corresponding parameter input standards of the service interface and/or the third-party service interface included in the service to be detected, the detection parameters matched with the respective corresponding parameter input standards are input into the service interface and/or the third-party service interface included in the service to be detected.
After the detection parameters are transmitted into the service interface of the service to be detected and/or the third-party service interface, the service interface of the service to be detected and/or the respective service execution unit of the third-party service interface process and return corresponding response parameters, and the returned response parameters may be different for different service interfaces and/or third-party service interfaces. Preferably, after the detection parameters matched with the respective corresponding parameter input standards are input to the service interface and/or the third-party service interface included in the service to be detected according to the respective corresponding parameter input standards of the service interface and/or the third-party service interface included in the service to be detected, the operation further includes an operation of acquiring response parameters returned by the service interface and/or the third-party service interface included in the service to be detected, where the acquired response parameters include a response parameter type and response parameter information.
Step S103, judging whether the response parameter returned by the service interface meets the detection response reference.
As described above, after the response parameters returned by the service interface and/or the third-party service interface included in the service to be detected are acquired, whether the returned response parameters meet respective detection response criteria of the service interface and/or the third-party service interface included in the service to be detected is judged, that is, whether the returned response parameter type and the returned response parameter information meet expectations is judged, if yes, it is indicated that the service interface and/or the third-party service interface included in the service to be detected is normal, and it is sufficient to continue to perform stability detection and abnormal quick positioning investigation on the subsequent services; if not, it indicates that the service interface of the service to be detected and/or the third-party service interface are abnormal, and the following step S104 is executed to record abnormal information of the service interface and/or the third-party service interface (i.e. abnormal service interface) that do not meet the respective detection response criteria.
And step S104, recording abnormal information of the abnormal service interface which does not accord with the detection response reference.
The precondition for implementing this step is that the step S103 determines whether the returned response parameter meets the respective detection response criteria of the service interface and/or the third-party service interface included in the service to be detected, if not, indicating that the service interface and/or the third-party service interface of the service to be detected is abnormal, and then records the abnormal information of the service interface and/or the third-party service interface (i.e., the abnormal service interface) that does not meet the respective detection response criteria by executing this step. In an embodiment of the present application, in a preferred implementation manner, the recording of the abnormal information on the service interface and/or the third-party service interface (i.e. the abnormal service interface) that do not meet the respective detection response criteria specifically includes: and uploading the abnormal service interface by calling an abnormal reporting interface, and recording the abnormal field information of the abnormal service interface. For example, when it is detected whether the returned response parameter type and response parameter information conform to an expected third-party interface, that is, a third-party interface with abnormal service, the third-party interface with abnormal service is reported to a service team maintaining the abnormal service interface by calling an abnormal reporting interface, and the specific service name and stack information of the third-party interface with abnormal service are recorded.
A complete example is provided below to illustrate the traffic monitoring method:
as shown in fig. 2, the distributed timed task module is provided with a timer, the distributed timed task module initiates scheduling to the monitoring service module at regular time, and the monitoring service module starts stability monitoring and fault fast location and elimination for the on-line login service after receiving the scheduling issued by the distributed timed task module. Specifically, in the process of monitoring the stability of the login service and quickly locating and removing the fault, firstly, determining the service having a strong dependency relationship with the login service includes: IM logs on the service, member center and apparatus service, corresponding, have strong business interface of the dependency relation with logging on the business including: the service interface of the IM login service, the service interface of the member center and the service interface of the equipment service.
According to the call path and time sequence relationship among the IM login service, the member center and the device service embodied in the attached figure 2, the user login verification process is sequentially divided into three steps: user identity authentication, member authentication and login equipment authentication. The user identity authentication is to transfer a request carrying a user ID to a service interface of the IM login service by calling the service interface of the IM login service so as to apply for the user identity authentication to the IM login service, and the user ID returns an object containing personal information of the user after the identity authentication of the IM login service is passed. And in the member authentication, a request carrying user account information is transmitted to the service interface of the member center by calling the service interface of the member center so as to apply for member authentication to the member center, and the user account information returns to an object containing the user member information after the member authentication of the member center is passed. And (3) login equipment authentication, namely, transmitting a request carrying a user ID and a user equipment hardware identifier to the service interface of the equipment service by calling the service interface of the equipment service so as to apply login equipment authentication to the equipment service, wherein the user ID and the user equipment hardware identifier return a unique feature code containing a representation user login equipment identifier after the login equipment authentication of the equipment service passes.
In the execution process, after the monitoring service module receives the scheduling issued by the distributed timing task module, if a user login authentication service request exists at the moment, three user data transmitted to a service interface of the IM login service, a service interface of the member center and a service interface of the equipment service in the user login authentication process can be used as detection parameters, and correspondingly, a processing result returned after the user data is transmitted is used as a response parameter returned by the detection parameter transmitted to the service interface. And further detecting whether the IM login service is abnormal by judging whether the business interface of the IM login service returns the processing result and whether the returned processing result is in accordance with the expectation (for example, detecting whether the returned processing result is an object containing the personal information of the user). Similarly, whether the member center is abnormal is detected by judging whether the service interface of the member center returns the processing result and whether the returned processing result is in accordance with the expectation (for example, detecting whether the returned processing result is an object containing the user member information); and detecting whether the equipment service is abnormal or not by judging whether the service interface of the equipment service returns the processing result or not and whether the returned processing result is in accordance with expectation (for example, detecting whether the returned processing result contains a unique feature code representing the user login equipment identifier or not).
If no processing result is returned in any of the three steps of the login verification process or the returned processing result is not in accordance with the expectation, reporting the service interface with abnormal service to the robot module by calling the abnormal reporting interface of the robot module, and recording the abnormal information of the service interface with abnormal service by the robot module. And if the processing results returned by the three steps of the login verification process are all in accordance with expectations, waiting for the next scheduling of the distributed timing task module.
In addition, in the execution process, after the monitoring service module receives the scheduling issued by the distributed timing task module, and no user login verification service request exists in a specific time period, corresponding detection parameters are respectively transmitted according to respective parameter standards of service interfaces of the IM login service, the member center and the equipment service, whether service abnormality exists in the IM login service, the member center and the equipment service is detected by judging whether response parameters returned after the detection parameters are transmitted into the service interfaces meet expectations, if so, the abnormal reporting interface of the robot module is called to report the service interface with the abnormal service to the robot module, and the robot module records the abnormal information of the service interface with the abnormal service. And if the processing results returned by the three steps of the login verification process are all in accordance with expectations, waiting for the next scheduling of the distributed timing task module.
In summary, the service monitoring method determines the service interface where the service to be detected has a dependency relationship by deeply analyzing the service to be detected, thereby breaking through the black box limitation of the service interface, and transmits corresponding detection parameters to the service interface according to the parameter input standard of the service interface, and further determines whether the returned response parameters meet expectations to determine whether the service processing of the service interface is abnormal, and if the service processing of the service interface is abnormal, records the abnormal information of the abnormal service interface where the service processing is abnormal, as a basis for performing abnormal troubleshooting and repair, thereby enabling the abnormality of the service to be detected to be accurately positioned, and performing fault quick troubleshooting on the basis of the accurate positioning, thereby avoiding the influence on the service.
The embodiment of the service monitoring device provided by the application is as follows:
in the foregoing embodiment, a service monitoring method is provided, and correspondingly, a service monitoring apparatus is also provided in the present application, which is described below with reference to the accompanying drawings.
Referring to fig. 3, a schematic diagram of an embodiment of a traffic monitoring apparatus provided in the present application is shown.
Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to the corresponding description of the method embodiments provided above for relevant portions. The device embodiments described below are merely illustrative.
The application provides a business monitoring device, includes:
a service interface acquiring unit 301, configured to acquire a service interface having a dependency relationship with a service to be detected;
a detection parameter input unit 302, configured to input a detection parameter to the service interface according to a parameter input standard of the service interface;
a response parameter determining unit 303, configured to determine whether a response parameter returned by the service interface meets a detection response criterion, and if not, run an exception recording unit 304;
the exception recording unit 304 is configured to record exception information for an exception service interface that does not meet the detection response criterion.
Optionally, the service interface obtaining unit 301 includes:
a service domain splitting subunit, configured to split the service to be detected into at least one service domain with the service domain as a splitting dimension;
the service domain combination subunit is used for combining the service domains according to the service dependency relationship among the service domains;
and the service interface extraction subunit is used for extracting the service interface contained in the service link obtained by the service domain combination and taking the service interface as the service interface which has a dependency relationship with the service to be detected.
Optionally, the service interfaces have a dependency relationship therebetween; and, a plurality of service interfaces with mutual dependency relationship belong to the same service domain, or a plurality of service interfaces with mutual dependency relationship belong to different service domains.
Optionally, the service interface having a dependency relationship with the service to be detected includes at least one of the following:
and the service interface to be detected comprises at least one service interface, and at least one third-party service interface which has strong dependency relationship with the service interface to be detected.
Optionally, the service interface obtaining unit 301 includes:
the strong dependence analysis subunit is configured to perform strong dependence analysis on the service interface included in the service to be detected and/or the third-party service interface, and obtain a strong dependence relationship between the service interface included in the service to be detected and/or the third-party service interface;
and the extracting subunit is used for extracting the service interface contained in the service to be detected and/or the third-party service interface with strong dependency relationship with the service interface contained in the service to be detected according to the strong dependency relationship.
Optionally, the strong dependency relationship between the service interfaces included in the service to be detected and/or the third-party service interfaces is embodied based on the call path and the timing relationship of the service interfaces included in the service to be detected and/or the third-party service interfaces.
Optionally, the detection parameter importing unit 302 is specifically configured to import, according to the call path and the timing relationship, the detection parameter matching the parameter input standard corresponding to the service interface included in the service to be detected and/or the third-party service interface according to the parameter input standard corresponding to the service interface included in the service to be detected and/or the third-party service interface.
Optionally, the service monitoring apparatus includes:
a response parameter unit, configured to obtain a response parameter returned by the service interface;
wherein the response parameter includes at least one of: response parameter type, response parameter information.
Optionally, the exception recording unit 304 includes:
an abnormal service interface reporting subunit, configured to upload the abnormal service interface by calling the abnormal reporting interface;
and the abnormal field information recording subunit is used for recording the abnormal field information of the abnormal service interface.
Optionally, the service monitoring apparatus operates based on a monitoring module, and the monitoring module initiates scheduling at regular time by a distributed timing task module.
The embodiment of the electronic equipment provided by the application is as follows:
in the foregoing embodiment, a service monitoring method is provided, and in addition, the present application also provides an electronic device for implementing the service monitoring method, which is described below with reference to the accompanying drawings.
Referring to fig. 4, a schematic diagram of an electronic device provided in the present embodiment is shown.
The embodiments of the electronic device provided in the present application are described more simply, and for related parts, reference may be made to the corresponding descriptions of the embodiments of the service monitoring method provided above. The embodiments described below are merely illustrative.
The application provides an electronic device, including:
a memory 401 and a processor 402;
the memory 401 is configured to store computer-executable instructions, and the processor 402 is configured to execute the following computer-executable instructions:
acquiring a service interface which has a dependency relationship with a service to be detected;
transmitting detection parameters to the service interface according to the parameter input standard of the service interface;
and judging whether the response parameters returned by the service interface meet the detection response reference, and if not, recording abnormal information of the abnormal service interface which does not meet the detection response reference.
Optionally, the acquiring a service interface having a dependency relationship with a service to be detected includes:
splitting the service to be detected into at least one service domain by taking the service domain as a splitting dimension;
combining the service domains according to the service dependency relationship among the service domains;
and extracting a service interface contained in the service link obtained by the service domain combination as the service interface having a dependency relationship with the service to be detected.
Optionally, the service interfaces have a dependency relationship therebetween; and, a plurality of service interfaces with mutual dependency relationship belong to the same service domain, or a plurality of service interfaces with mutual dependency relationship belong to different service domains.
Optionally, the service interface having a dependency relationship with the service to be detected includes at least one of the following:
and the service interface to be detected comprises at least one service interface, and at least one third-party service interface which has strong dependency relationship with the service interface to be detected.
Optionally, the acquiring a service interface having a dependency relationship with a service to be detected includes:
performing strong dependency analysis on a service interface and/or the third-party service interface included in the service to be detected to obtain a strong dependency relationship between the service interface and/or the third-party service interface included in the service to be detected;
and extracting the service interface contained in the service to be detected and/or a third party service interface having a strong dependency relationship with the service interface contained in the service to be detected according to the strong dependency relationship.
Optionally, the strong dependency relationship between the service interfaces included in the service to be detected and/or the third-party service interfaces is embodied based on the call path and the timing relationship of the service interfaces included in the service to be detected and/or the third-party service interfaces.
Optionally, the transmitting the detection parameter to the service interface according to the parameter input standard of the service interface includes:
and inputting detection parameters matched with the respective corresponding parameter input standards to the service interface contained in the service to be detected and/or the third-party service interface according to the calling path and the time sequence relationship and according to the respective corresponding parameter input standards of the service interface contained in the service to be detected and/or the third-party service interface.
Optionally, after a detection parameter instruction is transmitted to the service interface according to the parameter input standard of the service interface and executed, and before the response parameter returned by the service interface is judged to meet the detection response reference instruction and executed, the processor 402 is further configured to execute the following computer-executable instructions:
acquiring a response parameter returned by the service interface;
wherein the response parameter includes at least one of: response parameter type, response parameter information.
Optionally, the recording of the abnormal information of the abnormal service interface that does not meet the detection response reference includes:
uploading the abnormal service interface by calling an abnormal reporting interface;
and recording the abnormal field information of the abnormal service interface.
Optionally, the computer executable instruction is executed based on a monitoring module, and the monitoring module initiates scheduling by the distributed timed task module at regular time.
Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.
In a typical configuration, a computing device includes one or more processors, input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
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 computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
As will be appreciated by one skilled in the art, 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.
Claims (18)
1. A method for monitoring a service, comprising:
acquiring a service interface which has a dependency relationship with a service to be detected;
transmitting detection parameters to the service interface according to the parameter input standard of the service interface;
and judging whether the response parameters returned by the service interface meet the detection response reference, and if not, recording abnormal information of the abnormal service interface which does not meet the detection response reference.
2. The service monitoring method according to claim 1, wherein the acquiring a service interface having a dependency relationship with a service to be detected comprises:
splitting the service to be detected into at least one service domain by taking the service domain as a splitting dimension;
combining the service domains according to the service dependency relationship among the service domains;
and extracting a service interface contained in the service link obtained by the service domain combination as the service interface having a dependency relationship with the service to be detected.
3. The traffic monitoring method according to claim 2, wherein the traffic interfaces have a dependency relationship therebetween; and, a plurality of service interfaces with mutual dependency relationship belong to the same service domain, or a plurality of service interfaces with mutual dependency relationship belong to different service domains.
4. The traffic monitoring method according to claim 1, wherein the traffic interface having a dependency relationship with the traffic to be detected comprises at least one of:
and the service interface to be detected comprises at least one service interface, and at least one third-party service interface which has strong dependency relationship with the service interface to be detected.
5. The service monitoring method according to claim 4, wherein the acquiring a service interface having a dependency relationship with the service to be detected comprises:
performing strong dependency analysis on a service interface and/or the third-party service interface included in the service to be detected to obtain a strong dependency relationship between the service interface and/or the third-party service interface included in the service to be detected;
and extracting the service interface contained in the service to be detected and/or a third party service interface having a strong dependency relationship with the service interface contained in the service to be detected according to the strong dependency relationship.
6. The service monitoring method according to claim 5, wherein the strong dependency relationship between the service interfaces included in the service to be detected and/or the third-party service interfaces is embodied based on the call path and the timing relationship of the service interfaces included in the service to be detected and/or the third-party service interfaces.
7. The traffic monitoring method according to claim 6, wherein said transmitting detection parameters to said traffic interface according to the parameter input standard of said traffic interface comprises:
and inputting detection parameters matched with the respective corresponding parameter input standards to the service interface contained in the service to be detected and/or the third-party service interface according to the calling path and the time sequence relationship and according to the respective corresponding parameter input standards of the service interface contained in the service to be detected and/or the third-party service interface.
8. The traffic monitoring method according to claim 1, wherein after the step of transmitting the detection parameter to the traffic interface according to the parameter input standard of the traffic interface is executed, and before the step of determining whether the response parameter returned by the traffic interface meets the detection response criterion is executed, the following operations are executed:
acquiring a response parameter returned by the service interface;
wherein the response parameter includes at least one of: response parameter type, response parameter information.
9. The traffic monitoring method according to claim 1, wherein the recording of the abnormal traffic interface that does not meet the detection response criteria includes:
uploading the abnormal service interface by calling an abnormal reporting interface;
and recording the abnormal field information of the abnormal service interface.
10. The traffic monitoring method according to any of claims 1 to 9, wherein the traffic monitoring method is performed based on a monitoring module, and the monitoring module is scheduled by a distributed timed task module.
11. A traffic monitoring apparatus, comprising:
a service interface obtaining unit, configured to obtain a service interface having a dependency relationship with a service to be detected;
the detection parameter transmitting unit is used for transmitting detection parameters to the service interface according to the parameter input standard of the service interface;
a response parameter judging unit, configured to judge whether a response parameter returned by the service interface meets a detection response criterion, and if not, run an exception recording unit;
and the abnormal recording unit is used for recording abnormal information of the abnormal service interface which does not accord with the detection response reference.
12. The traffic monitoring apparatus according to claim 11, wherein the traffic interface obtaining unit includes:
a service domain splitting subunit, configured to split the service to be detected into at least one service domain with the service domain as a splitting dimension;
the service domain combination subunit is used for combining the service domains according to the service dependency relationship among the service domains;
and the service interface extraction subunit is used for extracting the service interface contained in the service link obtained by the service domain combination and taking the service interface as the service interface which has a dependency relationship with the service to be detected.
13. The traffic monitoring apparatus according to claim 12, wherein the traffic interfaces have a dependency relationship therebetween; and, a plurality of service interfaces with mutual dependency relationship belong to the same service domain, or a plurality of service interfaces with mutual dependency relationship belong to different service domains.
14. The traffic monitoring apparatus according to claim 11, wherein the traffic interface having a dependency relationship with the traffic to be detected comprises at least one of:
and the service interface to be detected comprises at least one service interface, and at least one third-party service interface which has strong dependency relationship with the service interface to be detected.
15. The traffic monitoring apparatus according to claim 14, wherein the traffic interface acquiring unit includes:
the strong dependence analysis subunit is configured to perform strong dependence analysis on the service interface included in the service to be detected and/or the third-party service interface, and obtain a strong dependence relationship between the service interface included in the service to be detected and/or the third-party service interface;
and the extracting subunit is used for extracting the service interface contained in the service to be detected and/or the third-party service interface with strong dependency relationship with the service interface contained in the service to be detected according to the strong dependency relationship.
16. The service monitoring device according to claim 15, wherein a strong dependency relationship between the service interfaces included in the service to be detected and/or the third-party service interfaces is embodied based on a call path and a timing relationship of the service interfaces included in the service to be detected and/or the third-party service interfaces.
17. The service monitoring device according to claim 16, wherein the detection parameter importing unit is specifically configured to import, according to the call path and the time sequence relationship and according to respective parameter input standards corresponding to a service interface included in the service to be detected and/or the third-party service interface, a detection parameter that matches the respective parameter input standard to the service interface included in the service to be detected and/or the third-party service interface.
18. An electronic device, comprising:
a memory and a processor;
the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:
acquiring a service interface which has a dependency relationship with a service to be detected;
transmitting detection parameters to the service interface according to the parameter input standard of the service interface;
and judging whether the response parameters returned by the service interface meet the detection response reference, and if not, recording abnormal information of the abnormal service interface which does not meet the detection response reference.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811300610.8A CN111143151B (en) | 2018-11-02 | 2018-11-02 | Service monitoring method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811300610.8A CN111143151B (en) | 2018-11-02 | 2018-11-02 | Service monitoring method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111143151A true CN111143151A (en) | 2020-05-12 |
| CN111143151B CN111143151B (en) | 2023-11-17 |
Family
ID=70516265
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811300610.8A Active CN111143151B (en) | 2018-11-02 | 2018-11-02 | Service monitoring method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143151B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111556080A (en) * | 2020-05-18 | 2020-08-18 | 网易（杭州）网络有限公司 | Network node monitoring method, device, medium and electronic equipment |
| CN113553235A (en) * | 2021-07-19 | 2021-10-26 | 猪八戒股份有限公司 | Business scene monitoring method and device, electronic equipment and storage medium |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060064483A1 (en) * | 2004-09-23 | 2006-03-23 | Patel Rikin S | System and method for service response monitoring |
| US20090210534A1 (en) * | 2006-07-12 | 2009-08-20 | Hewlett-Packard Development Company L.P. | Method of Providing Services in a Network, Network Element and Computer Program Product |
| US20130311839A1 (en) * | 2012-05-15 | 2013-11-21 | Sap Ag | Generation of error messages and progress information messages via a common interface |
| CN104410550A (en) * | 2014-12-10 | 2015-03-11 | 深圳中兴网信科技有限公司 | Web service monitoring method and web service monitoring device |
| CN106021068A (en) * | 2016-05-27 | 2016-10-12 | 北京京东尚科信息技术有限公司 | Monitoring method for service interface and monitoring system |
| CN106215416A (en) * | 2016-07-19 | 2016-12-14 | 网易（杭州）网络有限公司 | Game services method for monitoring state, device and system |
| US20160370784A1 (en) * | 2015-06-16 | 2016-12-22 | Siemens Aktiengesellschaft | Interfaces for connected software applications in automation environments |
| CN106301995A (en) * | 2015-06-24 | 2017-01-04 | 北京京东尚科信息技术有限公司 | The method and apparatus that a kind of automatic detection interface service is abnormal |
| CN106484592A (en) * | 2016-09-28 | 2017-03-08 | 北京奇虎科技有限公司 | A kind of method for detecting abnormality and device |
| CN106528390A (en) * | 2016-11-04 | 2017-03-22 | 智者四海（北京）技术有限公司 | Application monitoring method and device |
| WO2017045537A1 (en) * | 2015-09-14 | 2017-03-23 | 阿里巴巴集团控股有限公司 | Method and device for processing request in distributed system |
| CN106776093A (en) * | 2016-12-12 | 2017-05-31 | Tcl集团股份有限公司 | A kind of application exception log processing method and system |
| CN107688899A (en) * | 2017-08-22 | 2018-02-13 | 北京潘达互娱科技有限公司 | Business process monitoring method and device |
| CN107846321A (en) * | 2016-09-19 | 2018-03-27 | 阿里巴巴集团控股有限公司 | A kind of monitoring method of interface, device and electronic equipment |
| CN107888656A (en) * | 2017-10-09 | 2018-04-06 | 北京京东尚科信息技术有限公司 | Service the call method and calling device of end interface |
| CN108156061A (en) * | 2017-12-26 | 2018-06-12 | 重庆信联达软件有限公司 | Esb monitoring service platforms |
-
2018
- 2018-11-02 CN CN201811300610.8A patent/CN111143151B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060064483A1 (en) * | 2004-09-23 | 2006-03-23 | Patel Rikin S | System and method for service response monitoring |
| US20090210534A1 (en) * | 2006-07-12 | 2009-08-20 | Hewlett-Packard Development Company L.P. | Method of Providing Services in a Network, Network Element and Computer Program Product |
| US20130311839A1 (en) * | 2012-05-15 | 2013-11-21 | Sap Ag | Generation of error messages and progress information messages via a common interface |
| CN104410550A (en) * | 2014-12-10 | 2015-03-11 | 深圳中兴网信科技有限公司 | Web service monitoring method and web service monitoring device |
| US20160370784A1 (en) * | 2015-06-16 | 2016-12-22 | Siemens Aktiengesellschaft | Interfaces for connected software applications in automation environments |
| CN106301995A (en) * | 2015-06-24 | 2017-01-04 | 北京京东尚科信息技术有限公司 | The method and apparatus that a kind of automatic detection interface service is abnormal |
| WO2017045537A1 (en) * | 2015-09-14 | 2017-03-23 | 阿里巴巴集团控股有限公司 | Method and device for processing request in distributed system |
| CN106021068A (en) * | 2016-05-27 | 2016-10-12 | 北京京东尚科信息技术有限公司 | Monitoring method for service interface and monitoring system |
| CN106215416A (en) * | 2016-07-19 | 2016-12-14 | 网易（杭州）网络有限公司 | Game services method for monitoring state, device and system |
| CN107846321A (en) * | 2016-09-19 | 2018-03-27 | 阿里巴巴集团控股有限公司 | A kind of monitoring method of interface, device and electronic equipment |
| CN106484592A (en) * | 2016-09-28 | 2017-03-08 | 北京奇虎科技有限公司 | A kind of method for detecting abnormality and device |
| CN106528390A (en) * | 2016-11-04 | 2017-03-22 | 智者四海（北京）技术有限公司 | Application monitoring method and device |
| CN106776093A (en) * | 2016-12-12 | 2017-05-31 | Tcl集团股份有限公司 | A kind of application exception log processing method and system |
| CN107688899A (en) * | 2017-08-22 | 2018-02-13 | 北京潘达互娱科技有限公司 | Business process monitoring method and device |
| CN107888656A (en) * | 2017-10-09 | 2018-04-06 | 北京京东尚科信息技术有限公司 | Service the call method and calling device of end interface |
| CN108156061A (en) * | 2017-12-26 | 2018-06-12 | 重庆信联达软件有限公司 | Esb monitoring service platforms |
Non-Patent Citations (1)
| Title |
|---|
| 卓欣欣;白晓颖;许静;李恩鹏;刘喻;康介恢;宋文莉;: "服务接口测试自动化工具的研究", 计算机研究与发展, no. 02 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111556080A (en) * | 2020-05-18 | 2020-08-18 | 网易（杭州）网络有限公司 | Network node monitoring method, device, medium and electronic equipment |
| CN113553235A (en) * | 2021-07-19 | 2021-10-26 | 猪八戒股份有限公司 | Business scene monitoring method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111143151B (en) | 2023-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190378073A1 (en) | Business-Aware Intelligent Incident and Change Management | |
| CN105550113B (en) | Web test method and test machine | |
| CN112559361A (en) | Flow playback method, device, equipment and computer readable medium | |
| EP3422639A2 (en) | Performance testing method and apparatus for an industrial system deployed on cloud | |
| CN111899016A (en) | Quality data processing method and device based on block chain | |
| US10241902B2 (en) | Systems and methods for benchmark based cross platform service demand prediction | |
| US20180357143A1 (en) | Testing computing devices | |
| US20180095819A1 (en) | Incident analysis program, incident analysis method, information processing device, service identification program, service identification method, and service identification device | |
| CN114692169B (en) | Page vulnerability processing method applying big data and AI analysis and page service system | |
| CN111143151B (en) | Service monitoring method and device and electronic equipment | |
| US9811447B2 (en) | Generating a fingerprint representing a response of an application to a simulation of a fault of an external service | |
| CN109951326B (en) | Data processing method, device, storage medium and processor | |
| CN111901172B (en) | Application service monitoring method and system based on cloud computing environment | |
| US8037359B2 (en) | Operation management system having a process execution apparatus, information management apparatus, and process analyzing apparatus, process analyzing apparatus, recording medium in which process analysis program is recorded, and process analysis method | |
| CN115391224A (en) | Flow playback method and device, computer equipment and readable storage medium | |
| CN115840686A (en) | Server performance test method and device, electronic equipment and storage medium | |
| EP3029573B1 (en) | System and method for testing the performance of a computing infrastructure | |
| US11573851B2 (en) | Data of point-of-sale devices | |
| CN112860509A (en) | Dial testing alarm method and device | |
| CN112286792A (en) | Interface testing method, device, equipment and storage medium | |
| CN118277266A (en) | Configuration file detection method and device, storage medium and electronic equipment | |
| CN111815401B (en) | Order flow control method and equipment | |
| US20220197945A1 (en) | Computer-implemented method for analyzing a transaction log | |
| US20170116675A1 (en) | Generating term insurance service model in software defined environments | |
| CN112286791A (en) | Business system testing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |