Browse Prior Art Database

A method to simplify Resource Models configuration Disclosure Number: IPCOM000033309D
Original Publication Date: 2004-Dec-06
Included in the Prior Art Database: 2004-Dec-06
Document File: 6 page(s) / 97K

Publishing Venue



The present publication discloses a method and a software system useful to simplify the definition and configuration of a System Monitoring Application through a Graphical User Interface. At the same time it exploits more powerful run-time features to dynamically adapt whenever conditions change on the managed environment. The publication describes the main idea as an extension of the IBM Tivoli Monitoring product.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 25% of the total text.

Page 1 of 6

A method to simplify Resource Models configuration


One fundamental artifact for a Monitoring Application is the model defining the sources (aka probes), the info and the algorithms needed to monitor and to manage the selected Managed Resources. Such conceptual model is called (by ITM) the Resource Model (RM). A GUI development tool (e.g. the Resource Model Builder for the ITM product) is provided to develop and configure the RM. Then the RM is then deployed on the Run-Time Engine that executes it. In this publication we'll talk about Generalized Resource Model (GRM) thus introducing a more extendible way of building a RM. The main concepts of a GRM can be resumed as follows:

Retrieve/Receive Monitoring Samples (the probes needed to gather info about status of the managed resources), Filter Samples, Analyze Samples (the data samples can be combined to define the input to a rule-based analyzer. The analyzer must be configured to discover situations on the Managed Resources yielding a user-defined output to signal such conditions), Execute feedback actions on the Managed Node (the analyzer output can be used to trigger corrective feedback actions or notifications)

Problem Statement

    We discuss how to decrease the effort involved for the GRM construction and configuration. In fact, today, the IT administrators encounter great technical difficulties in developing and configuring effective RMs for monitoring and managing Managed Resources. This is due to a set of specific causes:

1) The use of crisp numbers (i.e. numerical thresholds) inside the analyzer configuration affects dramatically the complexity of the GRM configuration. So, the GRM configuration strongly depends upon a deep IT knowledge and many proven best practices about the resources to manage. Furthermore, the GRM configuration changes on different target endpoints increasing the needed effort.

2) The GRM runs on the managed environment for long time periods. Even though the GRM instance is initially well configured by the IT specialist, the time-variant conditions on the target endpoint can dramatically decrease the effectiveness of monitoring action.

3) The GRM development phase is a complicate task since involves deep knowledge of a programming languages and relative APIs.


    This proposal introduces an extension of the ITM monitoring system needed to solve the problems stated in the previous paragraph. Our system is composed by a GUI Toolkit for developing GRM (GRM Toolkit) and a GRM Run-Time Engine (aka GRM RTE). The fundamental requirements are:

1) The GRM Toolkit must allow the developer to create a GRM without specifying any crisp value at design time. In particular, we'll eliminate the crisp thresholds


Page 2 of 6

usage for the analyzer configuration using, instead, Linguistic Variables (LV).

2) The GRM Toolkit must support the developer by automatically building the GRM analyzer algorithm without any knowledge of the underlying rule set, using an...