Application Resilience System and Method Thereof for Applications Deployed on Platform

• US 20190149622A1
• Filed: 01/14/2019
• Published: 05/16/2019
• Est. Priority Date: 07/13/2016
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Kumar, Krishna Mankili, Vij, Deepak, Tang, Shengjun
• Granted Patent: US 10,462,234 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 24/04 Arrangements for maintaining operational condition

Abstract

An application resilience framework, where a monitoring engine of the framework monitors an application and captures data associated with the application. A processor analyzes the data captured to associate an event retrieved from the data captured with an action in a pre-stored template, executes the action associated to the event as specified in the pre-stored template, identifies a status of the application, fetches the data captured, the event retrieved from the data captured, the action associated with the event retrieved the action executed, stores in a repository, and notifies at least the status of the application based on at least one notification template storing at least one value.

Claims

1. An application resilience system for an application, comprising:

a memory comprising instructions; and

a processor coupled to the memory, the instructions causing the processor to be configured to;

analyze data captured, using a monitoring engine associated with the application, to associate an event retrieved from the data captured with an action in a pre-stored template;

execute the action associated to the event, the action being specified in the pre-stored template;

identify a status of the application;

fetch at least the data captured, the event retrieved from the data captured, or the action associated with the event retrieved;

store that at least the data captured, the event retrieved from the data captured, or the action associated with the event retrieved in a repository; and

notify the statues of the application based on at least one notification template storing at least one value.

2. The application resilience system of claim 1, wherein the pre-stored template is at least one of a default template or a custom template, the default template comprising at least one event and an action to be performed associated with the at least one event for the application, and the custom template comprising another at least one event and an action to be performed associated with the other at least one event for a specific application.

3. The application resilience system of claim 2, wherein the default template comprises at least one file describing events and actions associated with the events to be taken for application resilience.

4. The application resilience system of claim 2, wherein the default template comprises at least one standard meta-tag to capture actions associated with the application.

5. The application resilience system of claim 2, wherein the pre-stored template is customizable and comprises actions to be performed for application resilience.

6. The application resilience system claim 1, wherein the instructions further cause the processor to be configured to set a data association technique to fetch the data captured stored in the repository when a similar event occurs for the application.

7. The application resilience system of claim 1, wherein the instructions further cause the processor to be configured to:

fetch at least the data captured, the event retrieved from the data captured, or the action associated with t he even retrieved;

filter the data captured by fetching a relationship of the action taken for the event, the relationship being stored in the repository.

8. The application resilience system of claim 1, wherein the repository stores the data in a form of an action performed per application along with an associated time of the action performed.

9. The application resilience system of claim 1, wherein the application is deployed on a platform-as-a-service (PaaS) cloud.

10. An application resilience method for an application, comprising:

monitoring the application and capturing data associated with the application;

analyzing the data captured to associate an event retrieved from the data captured with an action in a pre-stored template;

executing the action associated to the event, the action being specified in the pre-stored template;

identifying a status of the application;

fetching at least the data captured, the event retrieved from the data captured, or the action associated with the event retrieved; and

store the at least the data captured, the event retrieved from the data captured, or the action associated with the event retrieved in at least a repository.

11. The application resilience method of claim 10, wherein the pre-stored template is at least one of a default template or a custom template, the default template comprising at least one event and an action to be performed associated with the at least one event for the application, and the custom template comprising another at least one event and an action to be performed associated with the other at least one event for a specific application.

12. The application resilience method of claim 11, wherein the default template comprise at least one file describing events and actions associated with the events to be taken for application resilience.

13. The application resilience method of claim 11, wherein the default template comprises at least one standard meta-tag to capture actions associated with the application.

14. The application resilience method of claim 11, wherein the pre-stored template is customizable and comprises actions to be performed for application resilience.

15. The application resilience method of claim 10, further comprising fetching, using a data association technique, the data captured stored in the repository when a similar event occurs for the application.

16. The application resilience method of claim 10, further comprising:

fetching the at least the data captured, the event retrieved from the data captured, or the action associated with the event retrieved; and

filtering the data captured by fetching a relationship of the action taken for the event, the relationship being stored in the repository.

17. The application resilience method of claim 10, further comprising storing, in the repository, the data a form of an action performed per application along with an associated time of the action performed.

18. The application resilience method of claim 10, wherein the application is deployed on a platform-as-a-service (PaaS) cloud.

19. A non-transitory computer readable storage medium storing instructions which, when executed by a computer device, cause the computer device to:

analyze data captured by monitoring an application to associate an event retrieved from the data captured with an action in a pre-stored template, the pre-stored template being customizable;

execute the action associated to the event, the action being specified in the pre-stored template;

identify a status of the application;

fetch at least the data captured, the event retrieved from the data captured, or the action associated with the event retrieved; and

store the at least the data captured, the event retrieved from the data captured, or the action associated with the event retrieved in at least a repository.

20. The non-transitory computer readable storage medium of claim 19, wherein the application is deployed on a platform-as-a-service (PaaS) cloud.