Monitoring a cloud service modeled as a topology

• US 10,230,568 B2
• Filed: 10/30/2013
• Issued: 03/12/2019
• Est. Priority Date: 10/30/2013
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Maes, Stephane Herman
• Primary Examiner(s): Madamba, Glenford J
• Application Number:
  US15/028,551
• Publication Number:
  US 20160254943A1
• Time in Patent Office: 1,959 Days
• Field of Search: 709224
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• 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

Abstract

A method of monitoring a cloud service modeled as a topology with a processor includes establishing a number of monitoring policies to monitor an instantiated topology, detecting an event at a node based on the number of monitoring policies, and processing the detected event based on the number of monitoring policies.

Claims

1. A method executed by a system comprising a processor, comprising:

establishing a number of monitoring policies to monitor a service created by instantiating a service topology, the monitoring policies defined in a monitoring system topology that is in addition to the service topology and describes how a monitoring system is deployed, the service topology comprising nodes representing resources that provide the service, and the monitoring system topology comprising nodes representing resources of the monitoring system;

setting up the monitoring system based on the monitoring system topology;

collecting metric data, as the service runs, by the monitoring system based on the number of monitoring policies, a monitoring policy of the number of policies comprising instructions executed by the monitoring system to monitor the service; and

in response to an incident identified based on the metric data, causing a remediation engine to apply a remediation action that addresses the incident.

2. The method of claim 1, wherein the number of monitoring policies comprise event handler instructions related to at least one selected from the group consisting of filtering events, correlating events, aggregating events, generating incidents, and generating incident notifications.

3. The method of claim 1, wherein the number of monitoring policies indicate at least one selected from the group consisting of a number of notification recipients, a number of nodes to monitor, what metric data to collect, and processes to perform on events.

4. The method of claim 1, wherein collecting the metric data comprises collecting at least one selected from the group consisting of operation data, security data, compliance data, usage data, analytics data, and big data,

wherein the operation data includes at least one selected from the group consisting of performance data, service level agreement data, performance degradation data, service level agreement degradation data, and trend data, and

wherein the analytics data includes at least one selected from the group consisting of business activity monitoring data (BAM) and business intelligence data (BI).

5. The method of claim 1, further comprising updating the number of monitoring policies based on the remediation action.

6. The method of claim 1, further comprising converting, by an interpreter, the number of monitoring policies into the monitoring system topology.

7. The method of claim 1, further comprising:

configuring the monitoring system using the number of monitoring policies.

8. The method of claim 1, further comprising:

associating a remediation policy with an individual node of the service topology,

wherein causing the remediation engine to apply the remediation action is based on the remediation policy, the remediation action applied on a resource represented by the individual node of the service topology.

9. The method of claim 1, wherein causing the remediation engine to apply the remediation action comprises modifying the service topology to produce a modified service topology and creating another service using the modified service topology.

10. The method of claim 1, wherein causing the remediation engine to apply the remediation action comprises retiring the service and retiring the monitoring system.

11. A system comprising:

an interface to assist in establishing a number of monitoring policies included in a monitoring system topology that describes how a monitoring system is deployed and comprising nodes representing resources of the monitoring system;

a processor; and

a non-transitory storage medium storing instructions executable on the processor to;

provision the monitoring system based on the monitoring system topology;

provision a cloud service based on a service topology comprising nodes representing resources that provide the service; and

collect metric data, as the cloud service runs, by the monitoring system based on the number of monitoring policies, a monitoring policy of the number of policies comprising instructions executable by the monitoring system to monitor the cloud service; and

in response to an incident identified based on the metric data, cause a remediation engine to apply a remediation action that addresses the incident.

12. The system of claim 11, further comprising an event handler executable on the processor to:

process events corresponding to the metric data based on the number of monitoring policies;

create the incident based on the events; and

send a notification of the incident to the remediation engine.

13. The system of claim 11, wherein the instructions are executable on the processor to:

access the number of monitoring policies by accessing a number of application programming interfaces (APIs) corresponding to the number of monitoring policies.

14. The system of claim 12, wherein the event handler is executable on the processor to process the events by at least one selected from the group consisting of filtering the events, correlating the events, and aggregating the events.

15. The system of claim 11, wherein the instructions are executable on the processor to:

associate a remediation policy with an individual node of the service topology,

wherein causing the remediation engine to apply the remediation action is based on the remediation policy, the remediation action applied on a resource represented by the individual node of the service topology.

16. The system of claim 11, wherein causing the remediation engine to apply the remediation action comprises modifying the service topology to produce a modified service topology and provisioning another cloud service using the modified service topology.

17. The system of claim 11, wherein causing the remediation engine to apply the remediation action comprises retiring the cloud service and retiring the monitoring system.

18. A non-transitory machine-readable medium storing instructions that upon execution cause a system to

establish a number of monitoring policies to monitor a service created by instantiating a service topology, the monitoring policies defined in a monitoring system topology that is in addition to the service topology and describes how a monitoring system is deployed, the service topology comprising a graph of nodes representing resources that provide the service, and the monitoring system topology comprising a graph of nodes representing resources of the monitoring system;

set up the monitoring system based on the monitoring system topology;

collect metric data, as the service runs, by the monitoring system based on the number of monitoring policies, a monitoring policy of the number of policies comprising instructions executable by the monitoring system to monitor the service;

determine a number of processes to be performed on events detected based on the metric data, the number of processes being identified in the number of monitoring policies; and

in response to an incident identified based on performance of the number of processes on the events, cause a remediation engine to apply a remediation action that addresses the incident.

19. The non-transitory machine-readable medium of claim 18, wherein causing the remediation engine to apply the remediation action comprises modifying the service topology to produce a modified service topology and provisioning another service using the modified service topology.

20. The non-transitory machine-readable medium of claim 18, wherein causing the remediation engine to apply the remediation action comprises retiring the cloud service and retiring the monitoring system.