Model and Method for Report-Driven Monitoring
Original Publication Date: 2005-Sep-29
Included in the Prior Art Database: 2005-Sep-29
The current way for compiling reports is to define a report against data gathered in a data store, and then compile the report from the data available. However, if the data you wish to use in your report is not currently being gathered, and the IT staff must be engaged. This article discusses a method to bring report creation and generation to the end consumer without having to continuously involve the technical staff.
Model and Method for Report -Driven Monitoring
The current way for compiling reports is to define a report against data gathered in a data store, and then compile the report from the data available. However, if the data you wish to use in your report is not currently being gathered, a member of the IT staff must modify the data gathering apparatus in order to collect this new data. This is not an optimal situation, as it consumes the time of the IT staff, and it makes the report definers painfully aware of the underlying IT infrastructure. This article describes a method to help alleviate the problem by automating the process of setting up the IT infrastructure to gather the required data, thus keeping the IT staff out of the picture, and allowing the report creator more control over what he can report upon.
Basically, we are moving report creation from the last step in the process to the first.
Simply put, a report is an organized compilation of a set of data. When a person defines the report he or she wishes to create, the data necessary for the creation of the report is implicit in the definition. As such, a system could derive the data gathering rules from the needs of the report. In other words; the system, when presented with a desired report, will automatically configure itself to gather the data required for the report. This methodology is advantageous in that it allows creators of reports to remain completely ignorant of the mechanics of data gathering, thus allowing them to take full advantage of the reporting capabilities. Meanwhile, the IT staff will save time by no longer having to cater to the needs of the report creators by tinkering with the data gathering system. Finally, since the data gathering rules created through this methodology will be correlated with a report, it allows for automatic removal of obsolete rules when the report is no longer needed.
This concept consists of four major components:
1. Report System - This component interacts with the user, and allows for the definition of reports. It then derives the data collection rules from the report definition...