Service identification method and device
By analyzing the interaction information and service change information of the abnormal client, comparing the number of request processing for different versions of services, the problem of identifying service problems that cause abnormal application operation is solved, and efficient and accurate service identification is achieved.
Patent Information
- Application Number
- CN202311101854.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-29
- Publication Date
- 2025-02-28
AI Technical Summary
It is difficult to efficiently identify services that cause abnormal applications to run, especially when services deployed on the server side change.
By obtaining the interaction information of the abnormal client, determine the services it accesses and has changed, and compare the average number of request processing for instances of different versions of services. If the ratio is greater than or equal to the preset proportional threshold, it is determined that the service is the service that causes the exception.
It realizes the rapid and accurate identification of services that cause client exceptions, which is more efficient and accurate than manual confirmation methods.
Smart Images
Figure CN119537063A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a service identification method and device. Background Art
[0002] With the development of computer technology, more and more applications have emerged, and the functions that applications can provide are becoming more and more diverse. When the application is running, it interacts with the server to provide users with corresponding functions. The server can deploy services corresponding to the functions provided by the application. At present, when the service deployed by the server changes, such as when the service deployed by the server is upgraded, it may cause the application to run abnormally. Among them, the application can also be called a client, and in this application, the two can be used interchangeably.
[0003] How to efficiently identify services that cause application operation abnormalities is a problem that has yet to be solved. Summary of the invention
[0004] In order to solve or at least partially solve the above technical problems, an embodiment of the present application provides a service identification method and device.
[0005] In a first aspect, an embodiment of the present application provides a service identification method, the method comprising:
[0006] Acquire interaction information corresponding to the abnormal client, where the interaction information is used by the server to record access information of the abnormal client to the server;
[0007] Determine, according to the interaction information, at least one service accessed by the abnormal client and changed, wherein the at least one service includes a target service;
[0008] Determine, based on the interaction information, an average number of requests processed by instances corresponding to the first version of the target service, and determine an average number of requests processed by instances corresponding to the second version of the target service;
[0009] According to the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service, it is determined whether the target service is the service that causes the abnormal client to be abnormal.
[0010] Optionally, determining whether the target service is the service causing the abnormal client to be abnormal according to the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service includes:
[0011] If the ratio between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service is greater than or equal to a preset ratio threshold, the target service is determined to be the service that causes the abnormal client to have an abnormality.
[0012] Optionally, the obtaining interaction information corresponding to the abnormal client includes:
[0013] The interaction information of the abnormal client within a certain period of time before the abnormality occurs is obtained.
[0014] Optionally, determining, according to the interaction information, at least one service accessed by the abnormal client and changed includes:
[0015] Determining, according to the interaction information, a plurality of services accessed by the abnormal client;
[0016] According to the service change information, the at least one service that has been changed is determined from the multiple services.
[0017] Optionally, determining, according to the interaction information, an average number of requests processed by instances corresponding to the first version of the target service includes:
[0018] Determining, based on the interaction information, a first total number of requests for accessing the first version of the target service;
[0019] Determining, according to the service change information, a first instance number of a first instance for processing an access request for accessing the first version of the target service;
[0020] An average number of instance requests processed corresponding to the first version of the target service is obtained according to the first total number and the first instance number.
[0021] Optionally, determining, according to the interaction information, an average number of requests processed by instances corresponding to the second version of the target service includes:
[0022] determining, based on the interaction information, a second total number of requests for accessing the second version of the target service;
[0023] Determining, according to the service change information, a number of second instances of the second instance for processing access requests for accessing the second version of the target service;
[0024] An average number of instance requests processed corresponding to the second version of the target service is obtained according to the second total number and the second instance number.
[0025] Optionally, the method further includes:
[0026] Outputting prompt information, wherein the prompt information indicates that the target service is the service that causes the abnormal client to be abnormal.
[0027] In a second aspect, an embodiment of the present application provides a service identification device, the device comprising:
[0028] An acquisition unit, used for acquiring interaction information corresponding to the abnormal client, wherein the interaction information is access information used by the server to record the abnormal client's access to the server;
[0029] A first determining unit, configured to determine, based on the interaction information, at least one service accessed by the abnormal client and changed, wherein the at least one service includes a target service;
[0030] A second determining unit, configured to determine, based on the interaction information, an average number of requests processed by instances corresponding to the first version of the target service, and an average number of requests processed by instances corresponding to the second version of the target service;
[0031] The third determination unit is used to determine whether the target service is the service that causes the abnormal client to have an abnormality based on the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service.
[0032] Optionally, the third determining unit is used to:
[0033] If the ratio between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service is greater than or equal to a preset ratio threshold, the target service is determined to be the service that causes the abnormal client to have an abnormality.
[0034] Optionally, the acquisition unit is used to:
[0035] The interaction information of the abnormal client within a certain period of time before the abnormality occurs is obtained.
[0036] Optionally, the first determining unit is configured to:
[0037] Determining, according to the interaction information, a plurality of services accessed by the abnormal client;
[0038] According to the service change information, the at least one service that has been changed is determined from the multiple services.
[0039] Optionally, the second determining unit is configured to:
[0040] Determining, based on the interaction information, a first total number of requests for accessing the first version of the target service;
[0041] Determining, according to the service change information, a first instance number of a first instance for processing an access request for accessing the first version of the target service;
[0042] An average number of instance requests processed corresponding to the first version of the target service is obtained according to the first total number and the first instance number.
[0043] Optionally, the second determining unit is configured to:
[0044] determining, based on the interaction information, a second total number of requests for accessing the second version of the target service;
[0045] Determining, according to the service change information, a number of second instances of the second instance for processing access requests for accessing the second version of the target service;
[0046] An average number of instance requests processed corresponding to the second version of the target service is obtained according to the second total number and the second instance number.
[0047] Optionally, the device further comprises:
[0048] The output unit is used to output prompt information, where the prompt information indicates that the target service is the service that causes the abnormal client to be abnormal.
[0049] In a third aspect, an embodiment of the present application provides an electronic device, the electronic device comprising a processor and a memory;
[0050] The processor is used to execute instructions stored in the memory so that the electronic device executes the method described in any one of the first aspects above.
[0051] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, wherein the instructions instruct a device to execute any of the methods described in the first aspect above.
[0052] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute any of the methods described in the first aspect above.
[0053] Compared with the prior art, the embodiments of the present application have the following advantages:
[0054] The embodiment of the present application provides a service identification method, which can be executed by a server. The server can obtain the interaction information corresponding to the abnormal client, and the interaction information is the access information used by the server to record the abnormal client's access to the server. Considering that the abnormality of the client is often caused by the change of the service deployed by the server, after obtaining the interaction information corresponding to the abnormal client, at least one service accessed by the abnormal client and changed can be further determined according to the interaction information. The target service is any one of the at least one service. Considering that if the target service changes and causes the client to be abnormal, the difference between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service is large, therefore, the server can determine the average number of instance request processing corresponding to the first version of the target service according to the interaction information, and determine the average number of instance request processing corresponding to the second version of the target service; and determine whether the target service is the service that causes the abnormal client to be abnormal according to the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service. Using the solution of the embodiment of the present application, compared with the manual confirmation method to determine the service that causes the client to be abnormal, it is possible to more efficiently and accurately determine the service that causes the client to be abnormal. BRIEF DESCRIPTION OF THE DRAWINGS
[0055] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0056] Figure 1 A flowchart of a service identification method provided in an embodiment of the present application;
[0057] Figure 2 A schematic diagram of the structure of a server provided in an embodiment of the present application;
[0058] Figure 3 A schematic diagram of the structure of a service identification device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0059] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0060] The inventor of the present application has found through research that when a service deployed on the server side changes, such as when a service deployed on the server side is upgraded, it may cause the application to run abnormally. Therefore, it is necessary to locate the service that causes the client to have an abnormality. Currently, when a large number of clients are found to have an abnormality, the service that has changed on the server side within a certain period of time before the client has an abnormality can be checked, and the service that causes the client to have an abnormality can be determined by manual investigation.
[0061] However, the manual screening method is inefficient on the one hand, and its accuracy is also affected by the experience of the screeners on the other hand, resulting in the accuracy of the results cannot be guaranteed.
[0062] In order to solve the above problems, the embodiments of the present application provide a service identification method and device, which can accurately and efficiently identify the service that causes the client to have an abnormality.
[0063] In the embodiments of the present application, "service" can be understood as a software function provided through a network and having specific business logic processing capabilities.
[0064] Various non-limiting implementations of the present application are described in detail below in conjunction with the accompanying drawings.
[0065] Exemplary Methods
[0066] See also Figure 1 , which is a flow chart of a service identification method provided in an embodiment of the present application. In an embodiment of the present application, the method can be executed by a service end.
[0067] In this embodiment, the method may include the following steps: S101-S104.
[0068] S101: Acquire interaction information corresponding to an abnormal client, where the interaction information is access information used by a server to record the abnormal client's access to the server.
[0069] In an embodiment of the present application, when receiving an access request from a client, the server may record the interaction information corresponding to the access request, for example, the service requested by the access request, the time when the access request is received, the identifier of the client sending the access request, and the processing result of the access request. The processing result may include, for example, normal or abnormal, and the service requested by the recorded access request may include the identifier and version information of the service.
[0070] In one example, when S101 is specifically implemented, interaction information corresponding to multiple abnormal clients can be obtained. As a specific example, when determining that multiple clients are abnormal, the server can obtain interaction information corresponding to each of the multiple clients, thereby obtaining interaction information corresponding to the multiple abnormal clients. For example, for a certain client, the interaction information stored in the server can be queried with the identifier of the client as an index, thereby obtaining interaction information corresponding to the client.
[0071] In the embodiment of the present application, it is considered that for the abnormal client, the interaction information within a certain period of time before the abnormality occurs has a certain reference significance for locating the cause of the abnormality of the client, while the interaction information far away from the abnormality of the abnormal client does not have much reference significance for locating the cause of the abnormality of the client. Therefore, in one example, when S101 is implemented, the interaction information of the abnormal client within a certain period of time before the abnormality occurs can be obtained. For example, the interaction information of the abnormal client within 5 minutes before the abnormality occurs is obtained. Of course, the full amount of interaction information of the abnormal client can also be obtained, which is not specifically limited in the embodiment of the present application.
[0072] S102: Determine, according to the interaction information, at least one service accessed by the abnormal client and changed, where the at least one service includes a target service.
[0073] In an embodiment of the present application, considering that client exceptions are often caused by changes in services deployed by the server, after obtaining the interaction information corresponding to the abnormal client, at least one service that has changed and is accessed by the abnormal client can be further determined based on the interaction information.
[0074] In one example, each interaction record in the interaction information can be analyzed to obtain the service requested by the access request corresponding to each interaction record, and then, the version information of the service corresponding to each interaction record is compared to determine at least one service that has been changed and accessed by the abnormal client.
[0075] In another example, the server may also maintain service change information, which is used to record service change information, such as service representation, service version number, and version effective time. In this case, when S102 is implemented, the server may analyze each interaction record in the interaction information to obtain the service requested by the access request corresponding to each interaction record, that is, to obtain multiple services accessed by the abnormal client. Then, in combination with the service change information, at least one service to send the change is determined from the multiple services. For example, for any one of the multiple services, the service change information may be queried using the service identifier as an index to determine whether the service has changed within a certain period of time.
[0076] In the embodiment of the present application, the target service is any one of the at least one service. For the target service, S103-S104 can be executed to determine whether the target service is the service that causes the abnormal client to be abnormal.
[0077] S103: Determine, according to the interaction information, an average number of requests processed by instances corresponding to the first version of the target service, and determine an average number of requests processed by instances corresponding to the second version of the target service.
[0078] In the embodiment of the present application, for each version of the target service, it may correspond to multiple instances, and the multiple instances are used to process the access request sent by the client to access the target service.
[0079] In a specific example, for a first version of a target service, it may correspond to a first number of first instances, which are used to process access requests sent by a client to access the first version of the target service, and the first number of first instances may, for example, be in a load-sharing relationship with each other. Similarly, for a second version of a target service, it may correspond to a second number of second instances, which are used to process access requests sent by a client to access the second version of the target service, and the second number of second instances may, for example, be in a load-sharing relationship with each other.
[0080] Considering that if the target service changes, it will cause the client to be abnormal, the difference between the average number of requests processed by each first instance and the average number of requests processed by each second instance will be relatively large. Therefore, in the embodiment of the present application, the average number of requests processed by the instance corresponding to the first version of the target service can be determined based on the interaction information, and the average number of requests processed by the instance corresponding to the second version of the target service can be determined. Among them:
[0081] The average number of requests processed by the instances corresponding to the first version of the target service is: the average number of requests processed by each of the multiple first instances that process access requests for accessing the first version of the target service, and the average number of requests processed by the instances corresponding to the second version of the target service is: the average number of requests processed by each of the multiple second instances that process requests for accessing the second version of the target service.
[0082] In an example, the server may determine the average number of requests processed by the instance corresponding to the first version of the target service based on the following steps A1-A3.
[0083] A1: Determine, according to the interaction information, a first total number of requests for accessing the first version of the target service.
[0084] In one example, each interaction record in the interaction information may be analyzed to determine the service requested by the access request corresponding to each interaction record, and the number of interaction records used to request access to the first version of the target service may be counted to obtain the first total number.
[0085] A2: Determine a first number of first instances for processing access requests for accessing the first version of the target service.
[0086] In one example, the aforementioned service change information may also record instance information associated with the service. In this case, in the specific implementation of step A2, the instance information associated with the first version of the target service may be obtained through the service change information, thereby obtaining the first instance number of the first instance that processes the access request for accessing the first version of the target service.
[0087] In yet another example, the server may obtain the first instance quantity through a configuration file of the first version of the target service. The configuration file may, for example, record instance information associated with the first version of the target service.
[0088] A3: According to the first total number and the first instance number, obtain the average number of instance requests processed corresponding to the first version of the target service.
[0089] After determining the first total number and the first number of instances, the ratio of the first total number to the first number of instances can be determined as the average number of instance requests processed corresponding to the first version of the target service. For example, if the first total number is 100 and the first number of instances is 4, the average number of instance requests processed corresponding to the first version of the target service is 100 / 4=25.
[0090] Similarly, in one example, the server may determine the average number of requests processed by the instance corresponding to the second version of the target service based on the following steps B1-B3.
[0091] B1: Determine, according to the interaction information, a second total number of requests for accessing the second version of the target service.
[0092] In one example, each interaction record in the interaction information may be analyzed to determine the service requested by the access request corresponding to each interaction record, and the number of interaction records used to request access to the second version of the target service may be counted to obtain the second total number.
[0093] B2: Determine the second number of second instances of the second instance for processing access requests for accessing the second version of the target service.
[0094] In one example, the aforementioned service change information may also record instance information associated with the service. In this case, in the specific implementation of step B2, the instance information associated with the second version of the target service may be obtained through the service change information, thereby obtaining the second instance number of the second instance that processes the access request for accessing the second version of the target service.
[0095] In yet another example, the server may obtain the second instance quantity through a configuration file of the second version of the target service. The configuration file may record instance information associated with the second version of the target service, for example.
[0096] B3: According to the second total number and the second instance number, obtain the average number of instance requests processed corresponding to the second version of the target service.
[0097] After determining the second total number and the second number of instances, the ratio of the second total number to the second number of instances can be determined as the average number of requests processed by the instances corresponding to the second version of the target service. For example, if the second total number is 20 and the second number of instances is 4, then the average number of requests processed by the second instance is 20 / 4=5.
[0098] S104: Determine whether the target service is the service that causes the abnormal client to be abnormal based on the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service.
[0099] After determining the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service, it can be determined whether the target service is the service that causes the abnormal client to occur an exception based on the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service.
[0100] In one example, when the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service differ greatly, the target service is determined to be the service that causes the abnormal client to have an abnormality. When the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service differ little, the target service is determined not to be the service that causes the abnormal client to have an abnormality.
[0101] In a specific example, the difference between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service can be embodied as the ratio between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service. For example, it can be the first ratio obtained by dividing the average number of instance request processing corresponding to the first version of the target service by the average number of instance request processing corresponding to the second version of the target service. For example, it can be the second ratio obtained by dividing the average number of instance request processing corresponding to the second version of the target service by the average number of instance request processing corresponding to the first version of the target service. In this case, when the aforementioned first ratio or the second ratio is greater than or equal to the preset ratio threshold, it can be determined that the target service is the service that causes the abnormal client to be abnormal. Correspondingly, when both the aforementioned first ratio and the second ratio are less than the preset ratio threshold, it can be determined that the target service is not the service that causes the abnormal client to be abnormal. The embodiment of the present application does not specifically limit the preset ratio threshold, and the preset ratio threshold can be determined according to actual conditions. For example, the preset ratio threshold can be 2.
[0102] In another specific example, the difference between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service can be reflected as the difference between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service. For example, it can be the first difference obtained by subtracting the average number of instance request processing corresponding to the first version of the target service from the average number of instance request processing corresponding to the second version of the target service. For example, it can be the second difference obtained by subtracting the average number of instance request processing corresponding to the second version of the target service from the average number of instance request processing corresponding to the first version of the target service. In this case, when the aforementioned first difference or the second difference is greater than or equal to the preset difference threshold, it can be determined that the target service is the service that causes the abnormal client to be abnormal. Correspondingly, when both the aforementioned first difference and the second difference are less than the preset difference threshold, it can be determined that the target service is not the service that causes the abnormal client to be abnormal. The embodiment of the present application does not specifically limit the preset difference threshold, and the preset difference threshold can be determined according to actual conditions.
[0103] In one example, if the server determines that the target service is the service that causes the abnormal client to be abnormal, the server can output prompt information, which indicates that the target service is the service that causes the abnormal client to be abnormal. For example, the server can control a display device to display the prompt information so that the operation and maintenance personnel can troubleshoot the target service based on the prompt information.
[0104] Next, the service identification method provided in the embodiment of the present application is introduced in combination with specific scenarios.
[0105] See also Figure 2 , which is a schematic diagram of the structure of a server provided in an embodiment of the present application. Figure 2 As shown, the server is deployed with the new version of service A and the old version of service A, as well as the new version of service B and the old version of service B. The new version of service A corresponds to 3 instances, and the old version of service A corresponds to 4 instances. The new version of service B corresponds to 4 instances, and the old version of service B corresponds to 3 instances.
[0106] The server obtains the interaction information of multiple abnormal clients within 5 minutes before the abnormality occurs, and determines the following information:
[0107] There are 90 requests for access to the new version of service A.
[0108] There are 150 requests for accessing the old version of service A.
[0109] There are 200 requests for access to the new version of service B.
[0110] There are 400 requests for access to the old version of service B;
[0111] The server calculates the following results:
[0112] The average number of requests processed by the instance corresponding to the new version of service A is: 30;
[0113] The average number of requests processed by the instance corresponding to the old version of service A is: 37.5;
[0114] The average number of requests processed by the instances corresponding to the old version of service A divided by the average number of requests processed by the instances corresponding to the new version of service A equals: 1.25.
[0115] The average number of requests processed by the instance corresponding to the new version of service B is: 50;
[0116] The average number of requests processed by the instances corresponding to the old version of service B is: 133.
[0117] The average number of requests processed by the instances corresponding to the old version of service B divided by the average number of requests processed by the instances corresponding to the new version of service B equals: 2.66.
[0118] Assuming that the preset ratio threshold is equal to 2, the server can determine that service B is the service that causes the client to have an exception.
[0119] Exemplary Devices
[0120] Based on the method provided in the above embodiment, the embodiment of the present application further provides a device, which is described below in conjunction with the accompanying drawings.
[0121] See also Figure 3 , which is a schematic diagram of the structure of a service identification device provided in an embodiment of the present application. The device 300 may specifically include, for example, an acquisition unit 301, a first determination unit 302, a second determination unit 303 and a third determination unit 304.
[0122] An acquisition unit 301 is used to acquire interaction information corresponding to an abnormal client, where the interaction information is access information used by a server to record the abnormal client's access to the server;
[0123] A first determining unit 302 is configured to determine, according to the interaction information, at least one service accessed by the abnormal client and changed, wherein the at least one service includes a target service;
[0124] A second determining unit 303 is used to determine, according to the interaction information, an average number of instance requests processed corresponding to the first version of the target service, and to determine an average number of instance requests processed corresponding to the second version of the target service;
[0125] The third determination unit 304 is used to determine whether the target service is the service that causes the abnormal client to be abnormal based on the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service.
[0126] Optionally, the third determining unit 304 is configured to:
[0127] If the ratio between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service is greater than or equal to a preset ratio threshold, the target service is determined to be the service that causes the abnormal client to have an abnormality.
[0128] Optionally, the acquiring unit 301 is used to:
[0129] The interaction information of the abnormal client within a certain period of time before the abnormality occurs is obtained.
[0130] Optionally, the first determining unit 302 is configured to:
[0131] Determining, according to the interaction information, a plurality of services accessed by the abnormal client;
[0132] According to the service change information, the at least one service that has been changed is determined from the multiple services.
[0133] Optionally, the second determining unit 303 is configured to:
[0134] Determining, based on the interaction information, a first total number of requests for accessing the first version of the target service;
[0135] Determining, according to the service change information, a first instance number of a first instance for processing an access request for accessing the first version of the target service;
[0136] An average number of instance requests processed corresponding to the first version of the target service is obtained according to the first total number and the first instance number.
[0137] Optionally, the second determining unit 303 is configured to:
[0138] determining, based on the interaction information, a second total number of requests for accessing the second version of the target service;
[0139] Determining, according to the service change information, a number of second instances of the second instance for processing access requests for accessing the second version of the target service;
[0140] An average number of instance requests processed corresponding to the second version of the target service is obtained according to the second total number and the second instance number.
[0141] Optionally, the device further comprises:
[0142] The output unit is used to output prompt information, where the prompt information indicates that the target service is the service that causes the abnormal client to be abnormal.
[0143] Since the device 300 is a device corresponding to the method provided in the above method embodiment, the specific implementation of each unit of the device 300 is based on the same concept as the above method embodiment. Therefore, for the specific implementation of each unit of the device 300, reference can be made to the description part of the above method embodiment, which will not be repeated here.
[0144] The embodiment of the present application also provides an electronic device, the electronic device comprising a processor and a memory;
[0145] The processor is used to execute the instructions stored in the memory, so that the electronic device executes the service identification method provided by the above method embodiment.
[0146] An embodiment of the present application provides a computer-readable storage medium, including instructions, wherein the instructions instruct a device to execute the service identification method provided by the above method embodiment.
[0147] An embodiment of the present application provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the service identification method provided by the above method embodiment.
[0148] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.
[0149] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.
[0150] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims
1. A service identification method, characterized in that: The method comprises: Acquire interaction information corresponding to the abnormal client, where the interaction information is used by the server to record access information of the abnormal client to the server; Determine, according to the interaction information, at least one service accessed by the abnormal client and changed, wherein the at least one service includes a target service; Determine, based on the interaction information, an average number of requests processed by instances corresponding to the first version of the target service, and determine an average number of requests processed by instances corresponding to the second version of the target service; According to the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service, it is determined whether the target service is the service that causes the abnormal client to be abnormal.
2. The method according to claim 1, characterized in that The determining, according to the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service, whether the target service is the service causing the abnormal client to be abnormal, includes: If the ratio between the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service is greater than or equal to a preset ratio threshold, the target service is determined to be the service that causes the abnormal client to occur an exception.
3. The method according to claim 1, characterized in that The obtaining of interaction information corresponding to the abnormal client includes: The interaction information of the abnormal client within a certain period of time before the abnormality occurs is obtained.
4. The method according to claim 1, characterized in that: The determining, according to the interaction information, at least one service accessed by the abnormal client and changed, includes: Determining, according to the interaction information, a plurality of services accessed by the abnormal client; According to the service change information, the at least one service that has been changed is determined from the multiple services.
5. The method according to claim 1, characterized in that: Determining, according to the interaction information, an average number of requests processed by an instance corresponding to the first version of the target service, including: Determining, based on the interaction information, a first total number of requests for accessing the first version of the target service; Determining, according to the service change information, a first instance number of a first instance for processing an access request for accessing the first version of the target service; An average number of instance requests processed corresponding to the first version of the target service is obtained according to the first total number and the first instance number.
6. The method according to claim 1, characterized in that The step of determining, according to the interaction information, an average number of requests processed by instances corresponding to the second version of the target service includes: determining, based on the interaction information, a second total number of requests for accessing the second version of the target service; Determining, according to the service change information, a number of second instances of the second instance for processing access requests for accessing the second version of the target service; An average number of instance requests processed corresponding to the second version of the target service is obtained according to the second total number and the second instance number.
7. The method according to claim 2, characterized in that The method further comprises: Outputting prompt information, wherein the prompt information indicates that the target service is the service that causes the abnormal client to be abnormal.
8. A service identification device, characterized in that: The device comprises: An acquisition unit, used for acquiring interaction information corresponding to the abnormal client, wherein the interaction information is access information used by the server to record the abnormal client's access to the server; A first determining unit, configured to determine, according to the interaction information, at least one service accessed by the abnormal client and changed, wherein the at least one service includes a target service; A second determining unit, configured to determine, based on the interaction information, an average number of requests processed by instances corresponding to the first version of the target service, and an average number of requests processed by instances corresponding to the second version of the target service; The third determination unit is used to determine whether the target service is the service that causes the abnormal client to have an abnormality based on the average number of instance request processing corresponding to the first version of the target service and the average number of instance request processing corresponding to the second version of the target service.
9. An electronic device, characterized in that: The electronic device comprises a processor and a memory; The processor is configured to execute instructions stored in the memory, so that the electronic device executes the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: The method comprises instructions for instructing a device to execute the method according to any one of claims 1 to 7.