Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method for automating the deployment of large scale enterprise monitoring solution in a cloud environment

IP.com Disclosure Number: IPCOM000235486D
Publication Date: 2014-Mar-04
Document File: 4 page(s) / 81K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method for automating the deployment of large scale enterprise monitoring solution in a cloud environment is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 01 of 4

Method for automating the deployment of large scale enterprise monitoring solution in a cloud environment

Disclosed is a method for automating the deployment of large scale enterprise monitoring solution in a cloud environment.

Traditionally, in-house monitoring solutions are deployed by planning, acquiring physical hardware, performing manual installations, and static configurations. Scaling to monitoring more resources is achieved by purchasing more hardware and deploying a scalable component of the overall solution onto the hardware. Agents that are monitoring applications and software resources are also deployed and configured typically via a manual processes. The Time To Value on these typical deployments is lengthy and error prone.

The disclosed method has the following objectives:

Deliver a scalable monitoring system that can automatically grow as the target environment grows.


1.

Enable automatic agent configuration allowing for agent Failover and Load-Balancing.


2.

Enable monitoring system that can "shrink" as the workloads shrink.


3.

The method is illustrated by applying steps to IBM

The first step is to decompose a single combined image into reusable components instead of just one image, with components that can be scaled out. In the IBM Tivoli Monitoring case, the scaling component is Remote Tivoli Enterprise Monitoring Server (RTEMS). Figure 1 depicts an example monitored environment.

® Tivoli

® Monitoring.


1.

1


Page 02 of 4

Figure 1


2. The method may leverage an automation system such as IBM Workload Deployer to enable life cycle operations to configure the decomposed image to work as an overall solution. Figure 1 may be implemented as depicted in Figure 2.

2


Page 03 of 4

Figure 2


3. Scaling metrics are provided to determine when to launch a new instance of the scaling component - RTEMS. Agents connect to RTEMS as described below:
§The RTEMS provides the scripts that:

-Register a collector meta data -Script that collects the data


•NumberOfActiveMS

§Consumers:
-Autoscaling policies enables the definition of a trigger event:

"triggerEvents": [

{

"metric": "RTEMS.NumberOfActiveMS",

"scaleOutThreshold": {

"value": 800,

"type": "CONSTANT",

"relation": ">="

} ]


4. Agents are enabled to be configured in monitored workloads. Registry information is defined to enable agents to automatically configure themselves to point to an appropriate monitoring server.

 IBM Workload Deployer provides a registry Service that ena...