AUTOMATED CREATION OF MONITORING CONFIGURATION TEMPLATES FOR CLOUD SERVER IMAGES

• US 20120297059A1
• Filed: 03/26/2012
• Published: 11/22/2012
• Est. Priority Date: 05/20/2011
• Status: Abandoned Application

• Current Assignee: Silverspore LLC
• Original Assignee: Silverspore LLC
• Inventors: Bross, Richard A
• Application Number:
  US13/429,636
• Publication Number:
  US 20120297059A1
• Time in Patent Office: Days
• US Class Current: 709/224
• 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 11/3093 Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0843 based on generic templates
• 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

Monitoring configurations for monitoring systems are automatically created for cloud server instances by polling the cloud controller to detect creation of each new instance, obtaining the image ID for the new instance from the cloud controller, and using a monitoring configuration template associated with the image ID to create the monitoring configuration. If a monitoring configuration template is not available for the image ID, a new template is created, either manually and/or automatically, and added to the template database. Automated template creation can include polling and analyzing instance ports and/or detecting and interrogating embedded monitoring agents such as WMI or SNMP. Monitor packs including detection criteria and interrogation checks can be used to detect monitoring agents and construct appropriate templates. Embodiments further monitor the cloud controller to detect termination of instances, and remove corresponding monitoring configurations from the monitoring to avoid generating false alerts.

Claims

1. Non-transient media comprising software which, when executed on a computing system, causes the computing system to execute steps leading to creation of a monitoring configuration usable by a monitoring system for monitoring an instance in a cloud computing network, the instance being created by a cloud controller according to an image or provisioning template, the steps executed by the computing system under control of the software comprising:

maintaining a database of monitoring configuration templates, each monitoring configuration template being associated with an image or provisioning template;

obtaining from the cloud controller information indicating that a new instance has been created using an image or provisioning template;

obtaining from the cloud controller information identifying the image or provisioning template used for creating the new instance;

determining if any of the monitoring configuration templates stored in the database of monitoring configuration templates is associated with the image or provisioning template used for creating the new instance;

if none of the monitoring configuration templates stored in the database of monitoring configuration templates is associated with the image or provisioning template used for creating the new instance;

creating a new monitoring configuration template;

associating the new monitoring configuration template with the image or provisioning template used for creating the new instance; and

adding the new monitoring configuration template to the database of monitoring configuration templates;

using the monitoring configuration template that is associated with the image or provisioning template used for creating the new instance to create a monitoring configuration associated with the new instance; and

providing the monitoring configuration associated with the new instance to the monitoring system.

2. The media of claim 1, wherein the information identifying the image or provisioning template used for creating the new instance includes an image ID or provisioning template ID.

3. The media of claim 1, wherein the steps further comprise obtaining from the cloud controller at least one of a private and a public IP address assigned to the new instance.

4. The media of claim 3, wherein creating a monitoring configuration for the new instance includes inserting the IP address into the monitoring configuration template that is associated with the image or provisioning template used for creating the new instance.

5. The media of claim 1, wherein the steps further comprise:

obtaining from the cloud controller information indicating that an instance has been terminated; and

removing the monitoring configuration associated with the terminated instance from the monitoring system, thereby avoiding an issuing by the monitoring system of a false alert regarding the terminated instance.

6. The media of claim 1, wherein creating a new monitoring configuration template includes providing to the computing system by a user of information regarding the image or provisioning template used for creating the new instance.

7. The media of claim 1, wherein creating a new monitoring configuration template includes using a discovery process to automatically discover information regarding the new instance.

8. The media of claim 7, wherein the discovery process includes querying ports of the new instance and analyzing responses therefrom.

9. The media of claim 7, wherein the discovery process includes detecting an embedded agent running on the instance and obtaining configuration information from the embedded agent.

10. The media of claim 9, wherein detecting the embedded agent includes receiving from a user credentials for the embedded agent and submitting the credentials to the new instance.

11. The media of claim 9, wherein the embedded agent is an SNMP agent.

12. The media of claim 9, wherein the embedded agent is a WMI agent.

13. The media of claim 9, wherein the embedded agent is a ws-man agent.

14. The media of claim 9, wherein the embedded agent is a CIM/SMASH agent.

15. The media of claim 9, wherein the embedded agent is a proprietary agent.

16. The media of claim 7, wherein the steps further comprise:

maintaining at least one monitor pack, the monitor pack including detection criteria useful for detecting an embedded agent running on an instance, the monitor pack further including checks useful for interrogating the embedded agent if it is found;

using the monitor pack to determine if the embedded agent is running on the new instance; and

if the embedded agent is running on the new instance, incorporating the monitor pack checks into the new monitoring configuration template.

17. The media of claim 1 wherein communicating with the cloud controller includes using an API.

18. The media of claim 17, wherein the API is the Amazon EC2 API.