Application health monitoring and automatic remediation

Patent metadata

Field	Value
Publication number	US-10891193-B2
Application number	US-201916238306-A
Country	US
Kind code	B2
Filing date	Jan 2, 2019
Priority date	Jan 2, 2019
Publication date	Jan 12, 2021
Grant date	Jan 12, 2021

Abstract

An application health monitoring system automatically resolves anomalies arising among clients of a messaging server. The messaging server clients (MSCs) include one or more applications and services included in the applications. The anomalies include MSC anomalies and process starter anomalies. When a messaging session is disconnected due to server restarts, the service may be automatically restarted a predetermined number of times to re-establish the connection. Similarly, if a process starter of a service fails to start up properly, the service can be automatically restarted a predetermined number of times before the anomaly is flagged for human review. The monitoring system also automatically implements rules whenever service configurations are changed in addition to validating web service ports and cloud provider queues.

First claim

What is claimed is:

1. An application health monitoring system comprising:
at least one processor;
a non-transitory processor-readable medium storing machine-readable instructions that cause the at least one processor to:
 receive data regarding one or more messaging server clients (MSCs) serviced by a messaging server,
the messaging server supplying the MSCs with messages,
the MSCs including a plurality of applications, and
the applications comprising one or more services;

 obtain a MSC comparison report,
the MSC comparison report providing comparisons of current states of each of the MSCs with a standard state;
 identify one or more MSC anomalies from the comparison report,
the MSC anomalies signifying disconnected sessions with at least one of the MSCs;
 restart at least one of the services associated with the disconnected sessions;
 generate another MSC comparison report,
the another MSC comparison report providing comparisons of the current states of each of the MSCs with the standard state after the at least one service is restarted;
 determine if a MSC validation stop condition is present,
the MSC validation stop condition including validation of the at least one MSC, and
the validating of the at least one MSC performed via establishing connections with the at least one MSC;
 prevent, when the consumer validation stop condition is present, performing the steps of:
accessing the MSC comparison report,
identifying the one or more MSC anomalies,
restarting at least one of the services, and
generating another MSC comparison report; and
 validate one or more process starters included in the services upon the validation of the at least one MSC, wherein the validation of the one or more process starters includes an automatic comparison of current attribute values of the one or more process starters with respective standard states that include attribute values to be maintained for a stable environment at the MSC.

2. The application health monitoring system of claim 1 , where the instructions for validating the process starters further comprise instructions that cause the processor to:
detect process starter anomalies between the current states and the respective standard states; and
restart the services including the process starters associated with the process starter anomalies.

3. The application health monitoring system of claim 2 , where the instructions for validating the process starters further comprise instructions that cause the processor to:
repeating the steps of comparing the current states, detecting the process starter anomalies and restarting the services until a process starter validation stop condition is reached.

4. The application health monitoring system of claim 3 , where the process starter validation stop condition further includes one of resolution of the process starter anomalies and repeating the steps of accessing the comparison report, identifying the one or more process starter anomalies, restarting at least one of the services and generating another comparison report at least three times.

5. The application health monitoring system of claim 3 , further comprising instructions that cause the processor to:
flag the process starter anomalies for human review if the process starter anomalies persist even after restarting the at least one of the services at least three times.

6. The application health monitoring system of claim 1 , where the MSC validation stop condition further includes repeating the steps of accessing the MSC comparison report, identifying the one or more MSC anomalies, restarting a server including the plurality of applications and generating another MSC comparison report at least three times.

7. The application health monitoring system of claim 6 , where the processor-readable medium stores further instructions that cause the processor to:
flag the anomalies for human review if the MSC anomalies persist even after restarting the server at least three times.

8. The application health monitoring system of claim 1 , where process starters include one or more of web services and queue receivers.

9. The application health monitoring system of claim 1 , where the processor-readable medium stores further instructions that cause the processor to:
provide one or more user interfaces that receive data regarding the standard states of the process starters.

10. The application health monitoring system of claim 1 , where the processor-readable medium stores further instructions that cause the processor to:
receive data regarding addition of one or more new services associated with the plurality of applications.

11. The application health monitoring system of claim 10 , where the processor-readable medium stores further instructions that cause the processor to:
automatically implement rules existing for the services to the one or more new services.

12. The application health monitoring system of claim 1 , where the one or more services include at least a web service the processor-readable medium stores further instructions that cause the processor to:
validate the web service via automatically connecting to a specific server and port number.

13. A method of monitoring application health comprising:
validating one or more messaging server clients (MSCs) serviced by a messaging server, the MSCs include a plurality of applications and one or more services associated with the plurality of applications;
validating one or more process starters upon validating the MSCs, the validation of the process starters includes:
comparing current attribute values of one or more process starters with respective predefined standard states of the process starters that include attribute values to be maintained for a stable environment at the MSCs;
detecting process starter anomalies between the current states of the process starters and the respective standard states;
restarting the services including the process starters associated with the process starter anomalies;
determine a process starter validation stop condition is reached where the process starter validation stop condition includes resolution of the process starter anomalies;
preventing, if the process starter validation stop condition is reached, recurrence of the steps of comparing the current states of the process starters, detecting the process starter anomalies and restarting the services; and
flagging the anomalies for human review if the process starter anomalies persist even after restarting the at least one of the services at least multiple times.

14. The method of claim 13 , where validating the one or more MSCs further comprises:
identify one or more MSC anomalies from a MSC comparison report, the MSC anomalies signifying disconnected sessions with at least one of the MSCs;
restart at least one of the services associated with the disconnected sessions; and
generate another MSC comparison report providing the current states of each of the MSCs after at least one service is restarted.

15. The method of claim 14 , where validating the one or more MSCs further comprises:
repeat steps of accessing the MSC comparison report, identifying the one or more MSC anomalies, restarting at least one of the services and generating another MSC comparison report until a MSC validation stop condition is reached, the MSC validation stop condition includes validation of the at least one MSC via establishment of connections with the at least one MSC.

16. The method of claim 13 , further comprising:
accessing a respective predefined standard state for each of the process

Assignees

• Accenture Global Solutions Ltd

Inventors

• Singh Jaskaran
• Singh Tishir

Classifications

• G06F11/302

  where the computing system component is a software system · CPC title

• G06F2201/87

  Monitoring of transactions · CPC title

• G06F11/3055

  Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available (error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction of the data by redundancy in operations G06F11/14; error detection or correction by redundancy in hardware G06F11/16) · CPC title

• G06F2201/865

  Monitoring of software · CPC title

• G06F11/076

  by exceeding a count or rate limit, e.g. word- or bit count limit · CPC title