Browse Prior Art Database

Persisting Event Data into Component and Measurement Data into Data Warehouse

IP.com Disclosure Number: IPCOM000030811D
Original Publication Date: 2004-Aug-27
Included in the Prior Art Database: 2004-Aug-27
Document File: 1 page(s) / 34K

Publishing Venue

IBM

Abstract

Disclosed in this article is an efficient and resource-limiting method to persist event data into a data warehouse.

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

Page 1 of 1

Persisting Event Data into Component and Measurement Data into Data Warehouse

Disclosed in this article in an efficient and resource-limiting method to persist event data into a data warehouse. The method described limits the amount of physical resources required when persisting event data. In an enterprise environment event data can be quite voluminous and storing this data in a data warehouse can be overwhelming, and quite costly.

To limit the number of data entries into the data warehouse, events are aggregated into "availability outage" measurements. Based on some pre-defined rules in the event management system these outage records are created and stored in the operational data store. The ruleset significantly reduces the number of event entries by combining multiple events into a single "availability outage" record. These "availability outage" records are then stored in the data warehouse for future reporting requirements.

An "availability outage" is a unique way to store availability data. The premise behind an "availability outage" is to report on outages versus availability time, or steady state time. This reduces the volume of data, because the assumption is that the component being monitored for availability spends most of its time in the steady state. When the component enters the non-steady state the "availability outage" begins, and when the component goes back to the steady state the "availability outage" ends. This model lends itself well for use...