DETECTING AND ANALYZING PERFORMANCE ANOMALIES OF CLIENT-SERVER BASED APPLICATIONS

• US 20170091008A1
• Filed: 09/29/2015
• Published: 03/30/2017
• Est. Priority Date: 09/29/2015
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated (Kyndryl Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Cherbakov, Luba, Dey, Kuntal, Mukherjea, Sougata, Rajput, Nitendra, Ramakrishna, Venkatraman
• Granted Patent: US 10,275,301 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0742 in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06N 20/00 Machine learning
• CPC Class Codes: G06N 5/04 Inference or reasoning models
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/064 involving time analysis
• CPC Class Codes: H04L 41/16 using machine learning or artificial intelligence
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0864 Round trip delays
• CPC Class Codes: H04L 43/16 Threshold monitoring

Abstract

An approach is provided for detecting and analyzing an anomaly in application performance in a client-server connection via a network. A request time and an Internet Protocol (IP) address of the client are determined. Based on the request time and the IP address, log entries relevant to the request are selected. A response code, a round trip latency time (RTT) of the response, and an indication of whether the connection timed out are determined. Based on the status code, the RTT, and the indication of whether connection timed out, the anomaly is detected. Based on temporal and textual analyses of log entries associated with the anomaly and an environment analysis that determines activity of the client, server, and network, candidate root causes of a failure that resulted in the anomaly are determined.

Claims

1. A method of detecting and analyzing an anomaly in a performance of an application in a connection between client and server computers, the method comprising the steps of:

a first computer determining a time of a request from the client computer executing the application and an Internet Protocol (IP) address of the client computer, the request being sent by the client computer to the server computer via a communications network;

based on the time of the request from the client computer and the IP address of the client computer, the first computer selecting one or more log entries from a plurality of log entries so that the selected one or more log entries are relevant to the request;

the first computer determining a status code of a response from the server computer, a round trip latency time (RTT) of the response, and an indication of whether the connection timed out, the response being sent by the server computer to the client computer via the network and responsive to the request;

based on the status code, the RTT, the indication of whether connection timed out, or a combination of the status code, the RTT, and the indication of whether the connection timed out, the first computer detecting the anomaly in the performance of the application; and

based on a temporal analysis and textual analysis of log entries associated with the anomaly, and based on an environment analysis that determines activity of the client computer, the server computer, and the network, the first computer determining candidate root causes of a failure that resulted in the anomaly, the failure being in the client computer, the server computer, the network, or a combination of the client computer, the server computer, and the network.

2. The method of claim 1, further comprising the steps of:

the first computer determining a period of time relevant to the anomaly;

based on the period of time, the first computer selecting relevant entities from among the client computer, the server computer, and components of the communications network;

based on the selected relevant entities and the period of time, the first computer selecting log entries from logs provided by the relevant entities;

subsequent to the step of selecting the log entries, the first computer filtering the selected log entries based on keywords that specify anomalies;

the first computer determining a usage of a central processing unit (CPU) of the server computer, a usage of a memory by the server computer, and an input/output (I/O) activity of the server computer; and

based on the filtered log entries, the usage of the CPU, the usage of the memory, and the I/O activity, the first computer determining whether each of the client computer, the server computer, and the components of the communications network was active or inactive at a time of an occurrence of the anomaly, wherein the step of determining the candidate root causes is based in part on whether each of the client computer, the server computer and the components of the communications network is determined to have been active or inactive at the time of the occurrence of the anomaly.

3. The method of claim 2, further comprising the steps of:

the first computer determining one or more components of the server computer were active at the time of the occurrence of the anomaly; and

based on the filtered log entries, the usage of the CPU, the usage of the memory, and the I/O activity, the first computer determining whether the one or more components of the server computer were performing tasks relevant to the application or extraneous to the application, wherein the step of determining the candidate root causes is based in part on whether the one or more components of the server computer were performing tasks relevant to the application or extraneous to the application.

4. The method of claim 1, further comprising the steps of:

the first computer determining confidences of the respective candidate root causes, each confidence indicating how likely the respective root cause is an actual root cause of the anomaly; and

the first computer presenting the candidate root causes in an order which is based on the confidences.

5. The method of claim 1, further comprising the steps of:

the first computer determining the anomaly specifies a type of an alert;

the first computer determining a role of a user;

the first computer determining an association between the type of the alert and the role of the user; and

based on the association between the type of the alert and the role of the user, the first computer presenting the alert to the user, the alert notifying the user about the anomaly.

6. The method of claim 5, further comprising the steps of:

the first computer collecting attributes of the anomaly and sending the attributes to a machine learning process, the attributes including the RTT, the indication of whether the connection timed out;

a delay value of the connection, details of the server computer and the application, details about a function specified by the request, and a uniform resource locator of the server computer;

the first computer receiving feedback from the user about whether the anomaly was correctly detected or incorrectly detected;

the first computer utilizing the feedback as a label of the machine learning process;

based on the collected attributes, the first computer generating a machine learning model for the machine learning process, the machine learning model including rules specifying subsequent anomalies;

the first computer updating the machine learning model continuously or at specified time intervals; and

based on the machine learning model or the updated machine learning model, the first computer detecting a subsequent anomaly in the performance of the application, wherein the subsequent anomaly is more likely to be accurately detected than the anomaly detected by the prior step of detecting the anomaly.

7. The method of claim 1, further comprising the step of:

providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable program code in the computer, the program code being executed by a processor of the computer to implement the steps of determining the time of the request and the IP address of the client computer, selecting the one or more log entries, determining the status code of the response, the RTT, and the indication of whether the connection timed out, detecting the anomaly, and determining the candidate root causes of the failure that resulted in the anomaly.

8. A computer program product, comprising:

a computer-readable, storage device; and

a computer-readable program code stored in the computer-readable, storage device, the computer-readable program code containing instructions that are executed by a central processing unit (CPU) of a computer system to implement a method of detecting and analyzing an anomaly in a performance of an application in a connection between client and server computers, the method comprising the steps of;

the computer system determining a time of a request from the client computer executing the application and an Internet Protocol (IP) address of the client computer, the request being sent by the client computer to the server computer via a communications network;

based on the time of the request from the client computer and the IP address of the client computer, the computer system selecting one or more log entries from a plurality of log entries so that the selected one or more log entries are relevant to the request;

the computer system determining a status code of a response from the server computer, a round trip latency time (RTT) of the response, and an indication of whether the connection timed out, the response being sent by the server computer to the client computer via the network and responsive to the request;

based on the status code, the RTT, the indication of whether connection timed out, or a combination of the status code, the RTT, and the indication of whether the connection timed out, the computer system detecting the anomaly in the performance of the application; and

based on a temporal analysis and textual analysis of log entries associated with the anomaly, and based on an environment analysis that determines activity of the client computer, the server computer, and the network, the computer system determining candidate root causes of a failure that resulted in the anomaly, the failure being in the client computer, the server computer, the network, or a combination of the client computer, the server computer, and the network.

9. The computer program product of claim 8, wherein the method further comprises the steps of:

the computer system determining a period of time relevant to the anomaly;

based on the period of time, the computer system selecting relevant entities from among the client computer, the server computer, and components of the communications network;

based on the selected relevant entities and the period of time, the computer system selecting log entries from logs provided by the relevant entities;

subsequent to the step of selecting the log entries, the computer system filtering the selected log entries based on keywords that specify anomalies;

the computer system determining a usage of a central processing unit (CPU) of the server computer, a usage of a memory by the server computer, and an input/output (I/O) activity of the server computer; and

based on the filtered log entries, the usage of the CPU, the usage of the memory, and the I/O activity, the computer system determining whether each of the client computer, the server computer, and the components of the communications network was active or inactive at a time of an occurrence of the anomaly, wherein the step of determining the candidate root causes is based in part on whether each of the client computer, the server computer and the components of the communications network is determined to have been active or inactive at the time of the occurrence of the anomaly.

10. The computer program product of claim 9, wherein the method further comprises the steps of:

the computer system determining one or more components of the server computer were active at the time of the occurrence of the anomaly; and

based on the filtered log entries, the usage of the CPU, the usage of the memory, and the I/O activity, the computer system determining whether the one or more components of the server computer were performing tasks relevant to the application or extraneous to the application, wherein the step of determining the candidate root causes is based in part on whether the one or more components of the server computer were performing tasks relevant to the application or extraneous to the application.

11. The computer program product of claim 8, wherein the method further comprises the steps of:

the computer system determining confidences of the respective candidate root causes, each confidence indicating how likely the respective root cause is an actual root cause of the anomaly; and

the computer system presenting the candidate root causes in an order which is based on the confidences.

12. The computer program product of claim 8, wherein the method further comprises the steps of:

the computer system determining the anomaly specifies a type of an alert;

the computer system determining a role of a user;

the computer system determining an association between the type of the alert and the role of the user; and

based on the association between the type of the alert and the role of the user, the computer system presenting the alert to the user, the alert notifying the user about the anomaly.

13. The computer program product of claim 12, wherein the method further comprises the steps of:

the computer system collecting attributes of the anomaly and sending the attributes to a machine learning process, the attributes including the RTT, the indication of whether the connection timed out;

a delay value of the connection, details of the server computer and the application, details about a function specified by the request, and a uniform resource locator of the server computer;

the computer system receiving feedback from the user about whether the anomaly was correctly detected or incorrectly detected;

the computer system utilizing the feedback as a label of the machine learning process;

based on the collected attributes, the computer system generating a machine learning model for the machine learning process, the machine learning model including rules specifying subsequent anomalies;

the computer system updating the machine learning model continuously or at specified time intervals; and

based on the machine learning model or the updated machine learning model, the computer system detecting a subsequent anomaly in the performance of the application, wherein the subsequent anomaly is more likely to be accurately detected than the anomaly detected by the prior step of detecting the anomaly.

14. A computer system comprising:

a central processing unit (CPU);

a memory coupled to the CPU; and

a computer readable storage device coupled to the CPU, the storage device containing instructions that are executed by the CPU via the memory to implement a method of detecting and analyzing an anomaly in a performance of an application in a connection between client and server computers, the method comprising the steps of;

the computer system determining a time of a request from the client computer executing the application and an Internet Protocol (IP) address of the client computer, the request being sent by the client computer to the server computer via a communications network;

based on the time of the request from the client computer and the IP address of the client computer, the computer system selecting one or more log entries from a plurality of log entries so that the selected one or more log entries are relevant to the request;

the computer system determining a status code of a response from the server computer, a round trip latency time (RTT) of the response, and an indication of whether the connection timed out, the response being sent by the server computer to the client computer via the network and responsive to the request;

based on the status code, the RTT, the indication of whether connection timed out, or a combination of the status code, the RTT, and the indication of whether the connection timed out, the computer system detecting the anomaly in the performance of the application; and

based on a temporal analysis and textual analysis of log entries associated with the anomaly, and based on an environment analysis that determines activity of the client computer, the server computer, and the network, the computer system determining candidate root causes of a failure that resulted in the anomaly, the failure being in the client computer, the server computer, the network, or a combination of the client computer, the server computer, and the network.

15. The computer system of claim 14, wherein the method further comprises the steps of:

the computer system determining a period of time relevant to the anomaly;

based on the period of time, the computer system selecting relevant entities from among the client computer, the server computer, and components of the communications network;

based on the selected relevant entities and the period of time, the computer system selecting log entries from logs provided by the relevant entities;

subsequent to the step of selecting the log entries, the computer system filtering the selected log entries based on keywords that specify anomalies;

the computer system determining a usage of a central processing unit (CPU) of the server computer, a usage of a memory by the server computer, and an input/output (I/O) activity of the server computer; and

based on the filtered log entries, the usage of the CPU, the usage of the memory, and the I/O activity, the computer system determining whether each of the client computer, the server computer, and the components of the communications network was active or inactive at a time of an occurrence of the anomaly, wherein the step of determining the candidate root causes is based in part on whether each of the client computer, the server computer and the components of the communications network is determined to have been active or inactive at the time of the occurrence of the anomaly.

16. The computer system of claim 15, wherein the method further comprises the steps of:

the computer system determining one or more components of the server computer were active at the time of the occurrence of the anomaly; and

based on the filtered log entries, the usage of the CPU, the usage of the memory, and the I/O activity, the computer system determining whether the one or more components of the server computer were performing tasks relevant to the application or extraneous to the application, wherein the step of determining the candidate root causes is based in part on whether the one or more components of the server computer were performing tasks relevant to the application or extraneous to the application.

17. The computer system of claim 14, wherein the method further comprises the steps of:

the computer system determining confidences of the respective candidate root causes, each confidence indicating how likely the respective root cause is an actual root cause of the anomaly; and

the computer system presenting the candidate root causes in an order which is based on the confidences.

18. The computer system of claim 14, wherein the method further comprises the steps of:

the computer system determining the anomaly specifies a type of an alert;

the computer system determining a role of a user;

the computer system determining an association between the type of the alert and the role of the user; and

based on the association between the type of the alert and the role of the user, the computer system presenting the alert to the user, the alert notifying the user about the anomaly.

19. The computer system of claim 18, wherein the method further comprises the steps of:

the computer system collecting attributes of the anomaly and sending the attributes to a machine learning process, the attributes including the RTT, the indication of whether the connection timed out;

a delay value of the connection, details of the server computer and the application, details about a function specified by the request, and a uniform resource locator of the server computer;

the computer system receiving feedback from the user about whether the anomaly was correctly detected or incorrectly detected;

the computer system utilizing the feedback as a label of the machine learning process;

based on the collected attributes, the computer system generating a machine learning model for the machine learning process, the machine learning model including rules specifying subsequent anomalies;

the computer system updating the machine learning model continuously or at specified time intervals; and

based on the machine learning model or the updated machine learning model, the computer system detecting a subsequent anomaly in the performance of the application, wherein the subsequent anomaly is more likely to be accurately detected than the anomaly detected by the prior step of detecting the anomaly.