Autonomous service management

• US 9,292,402 B2
• Filed: 04/15/2013
• Issued: 03/22/2016
• Est. Priority Date: 04/15/2013
• Status: Active Grant

• Current Assignee: CenturyLink Intellectual Property LLC (Lumen Technologies, Inc.)
• Original Assignee: Century Link Intellectual Property LLC
• Inventors: Mallige, Ramapriya, Plakkatt, Santhosh, Ramchandra, Manoj, Seetharam, Viswanath
• Primary Examiner(s): DUNCAN, MARC M
• Application Number:
  US13/863,106
• Publication Number:
  US 20140310564A1
• Time in Patent Office: 1,072 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0706 the processing taking place on a specific hardware platform or in a specific software environment
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/0781 Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/3003 Monitoring arrangements specially adapted to the computing system or computing system component being monitored
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

Novel tools and techniques that offer more robust solutions for application service management. Some such solutions provide a service management framework for managing a software application. In some cases, the framework can include multiple tools to detect and/or remedy application problems at a variety of different levels. In another aspect, some solutions can define multiple application lifecycle phases, ranging from minor impairment to catastrophic failure. For each of such phases, the service management framework can define one or more diagnostic criteria and/or one or more corrective actions that can be taken to remedy a suboptimal condition of the application.

Claims

1. A method of providing service management for a software application, the method comprising:

implementing, with a computer, a service management framework to manage the software application, the service management framework comprising;

an early warning system;

a self-healing system; and

a subject matter expert intervention mechanism;

monitoring, with the computer, the software application;

detecting, with the computer, that the software application has encountered deterioration of operation;

determining, with the computer, which one of a plurality of pre-defined performance deterioration phases into which the software application has entered, the pre-defined performance deterioration phases comprising one of;

an attenuation phase, in which the function of the software application deviates from at least one baseline metric but still remains generally operational;

a degeneration phase, characterized by an anomaly in the function of the software application and initialization of the self-healing system;

a debilitation phase, characterized by partial loss of function in the software application and failure of the self-healing system to repair the function of the software application; and

a breach phase, characterized by complete loss of function of the software application; and

based on the determination of the pre-defined performance deterioration phase, performing, with the computer, one or more actions specified by the service management framework.

2. The method of claim 1, wherein the one or more actions specified by the service management framework for the attenuation phase comprise generating one or more automatic alert notifications with the early warning system, in response to detecting that the software application has encountered a condition that indicates the software application has entered the attenuation phase.

3. The method of claim 2, wherein detecting that the software application has encountered a condition that indicates the software application has entered the attenuation phase comprises detecting the condition with a monitoring component that compares one or more application performance statistics with baseline performance statistics.

4. The method of claim 2, wherein the early warning system generates one automatic alert notification each time the computer detects that the software application has encountered a condition that indicates the software application has entered the attenuation phase.

5. The method of claim 1, wherein the one or more actions specified by the service management framework comprise invocation of a self healing system in response to receiving a specified number of automatic alert notifications, the specified number of alert notifications indicating that the software application has entered the degeneration phase.

6. The method of claim 5, wherein the self healing system performs an automated analysis of the detected condition and attempts to implement an automated resolution of the condition.

7. The method of claim 6, wherein the automated analysis comprises behavioral monitoring.

8. The method of claim 6, wherein the automated resolution of the condition comprises implementation of an executor or an exception handler.

9. The method of claim 1, wherein the one or more actions specified by the service management framework comprise automatic notification of a subject matter expert, in response to detecting a condition indicating that the software application has entered the debilitation phase.

10. The method of claim 9, wherein the condition indicating that the software application has entered the debilitation phase comprises a notification from a self healing system that the self healing system attempted to repair an anomaly but was unable to repair the anomaly.

11. The method of claim 9, wherein notification of a subject matter expert comprises displaying a notification in a dashboard display.

12. The method of claim 9, wherein notification of a subject matter expert comprises transmitting a message addressed to the subject matter expert.

13. The method of claim 1, wherein the one or more actions specified by the service management framework comprises implementation of an automated disaster recovery solution, in response to detecting that the software application has encountered the breach phase.

14. The method of claim 13, wherein the automated disaster recovery solution comprises offloading one or more tasks of the software application to a failover application.

15. The method of claim 13, wherein the automated disaster recovery solution comprises automatic recovery of one or more configuration files.

16. The method of claim 1, wherein the service management framework specifies that management of the software application will proceed through the pre-defined performance deterioration phases in a specified order when performance degradation is detected.

17. The method of claim 16, further comprising:

detecting, with the computer, a condition of the software application; and

in response to the detected condition, varying management of the software application by proceeding through the pre-defined performance deterioration phases in an order other than the specified order.

18. An apparatus, comprising:

a non-transitory computer readable medium having encoded thereon a set of instructions executable by one or more computers to perform one or more operations for providing service management for a software application, the set of instructions comprising;

instructions for implementing a service management framework to manage the software application, the service management framework comprising;

an early warning system;

a self-healing system; and

a subject matter expert intervention mechanism;

instructions for monitoring the software application;

instructions for detecting that the software application has encountered deterioration of operation;

instructions for determining one of a plurality of pre-defined performance deterioration phases into which the software application has entered, the pre-defined performance deterioration phases comprising one of;

an attenuation phase, in which the function of the software application deviates from at least one baseline metric but still remains generally operational;

a degeneration phase, characterized by an anomaly in the function of the software application and initialization of the self-healing system;

a debilitation phase, characterized by partial loss of function in the software application and failure of the self-healing system to repair the function of the software application; and

a breach phase, characterized by complete loss of function of the software application; and

instructions for performing, based on the determination of the pre-defined performance deterioration phase, one or more actions specified by the service management framework.

19. A computer system for providing service management for a software application, comprising:

one or more processors; and

a non-transitory computer readable medium in communication with the one or more processors, the computer readable medium having encoded thereon a set of instructions executable by the computer system to perform one or more operations, the set of instructions comprising;

instructions for implementing a service management framework to manage the software application, the service management framework comprising;

an early warning system;

a self-healing system; and

a subject matter expert intervention mechanism;

instructions for monitoring the software application;

instructions for detecting that the software application has encountered deterioration of operation;

instructions for determining one of a plurality of pre-defined performance deterioration phases into which the software application has entered, the pre-defined performance deterioration phases comprising one of;

an attenuation phase, in which the function of the software application deviates from at least one baseline metric but still remains generally operational;

a degeneration phase, characterized by an anomaly in the function of the software application and initialization of the self-healing system;

a debilitation phase, characterized by partial loss of function in the software application and failure of the self-healing system to repair the function of the software application; and

a breach phase, characterized by complete loss of function of the software application; and

instructions for performing, based on the determination of the pre-defined performance deterioration phase, one or more actions specified by the service management framework.