Framework for providing metrics from any datasource

• US 8,234,240 B2
• Filed: 04/26/2007
• Issued: 07/31/2012
• Est. Priority Date: 04/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Myerson, Neal R., Justus, Darren C., Luniya, Jitendra, Moon, Carroll W., Pallini, Susan
• Primary Examiner(s): Jalil, Neveen Abel
• Assistant Examiner(s): PEACH, POLINA G
• Application Number:
  US11/740,723
• Publication Number:
  US 20080270369A1
• Time in Patent Office: 1,923 Days
• Field of Search: None
• US Class Current: 707/603
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses

Abstract

A metrics generation system provides IT and other computing system metrics from different data sources in a single display. Configuration files containing parameters and instructions are loaded by the system to access different data sources. The metrics generation system retrieves IT system health data, processes and aggregates metrics from the retrieved data and displays the metrics based on user defined parameters and instructions in the configuration files. The metrics generation system is flexible in that it can be changed to extract data from different IT data sources, calculate different metric information having a hierarchy of attribute types and values, and display a variety of metric data in different formats.

Claims

1. A method for providing a flexible and dynamic metric generation system for efficiently generating a metric, comprising:

accessing one or more configuration files and loading the configuration files into a staging database, the staging database having a staging database schema for loading extracted data from two or more data stores, each of the data stores having a different schema than the staging database schema and storing metric data, calculated using the extracted data, in a hierarchical structure of attributes predefined by a user for each metric, at least one of the one or more configuration files includes server extraction parameters specifying instructions for extracting data from the two or more data stores and attribute parameters defining the hierarchical structure of the attributes associated with the metric, at least one of the configuration files identifies availability and weight information associated with the metric, the metric is associated with a trend indicating whether the metric tends to increase or decrease over time, the trend for the metric is used for comparison against a target value defined for the metric;

generating a first unique query by the staging database to extract data from a first data store associated with a first server and a second unique query by the staging database to extract data from a second data store associated with a second server based on the server extraction parameters and the attribute parameters contained in the one or more configuration files, the first server and the second server having a different communication interface and associated with different server extraction parameters;

sending the first unique query to the first server and the second unique query to the second server by the staging database;

receiving a first response with a first extracted data from the first server and a second response with a second extracted data from the second server; and

storing the first extracted data in a first set of tables and the second extracted data in a second set of tables, said storing being carried out according to the staging database schema, the first set of tables and the second set of tables located within the staging database; and

calculating metric data from the stored first extracted data and second extracted data based on the server extraction parameters and the attribute parameters contained in the one or more configuration files;

aggregating the metric data; and

packaging the aggregated metric data, packaging the aggregated metric data including packaging the aggregated metric data as a three dimensional data cube and/or packaging the aggregated metric data into a compressed file to efficiently contain a set of data to display through a user interface;

said accessing one or more configuration files includes accessing the one or more configuration files at different points in time, said accessing one or more configuration files includes merging the one or more configuration files into an XML file;

said calculating metric data includes generating a first calculation task for determining a total number of times that an event occurs, said calculating metric data includes generating a second calculation task for determining the availability of an element as a percentage of a series of data points having a certain value, said calculating metric data includes comparing a metric value for said metric against a target value to determine that the metric value is “

green”

based on said trend associated with said metric.

2. The method of claim 1, further comprising:

providing a presentation database for aggregating the first extracted data and the second extracted data at each level of the hierarchical structure associated with each metric;

providing a data set generation module for packaging selected portions of data into a package for display; and

providing a display application for accessing the selected portions of data from the data package and displaying the selected portions.

3. The method of claim 1, wherein said step of generating a unique query by the staging database includes:

generating an extraction task by the staging database based on the one or more configuration files; and

performing the extraction task by the staging database in communication with the first server and the second server.

4. The method of claim 1, wherein said step of generating a unique query includes:

determining a number of servers specified in the one or more configuration files, the servers including the first server and second server; and

generating a query for each server specified in the one or more configuration files.

5. The method of claim 1, wherein said step of storing includes:

retrieving a data value and time data from the first response; and

loading the data value and time data into a table.

6. The method of claim 1, wherein said step of storing includes:

generating an inbound data table in the staging database from the one or more configuration files; and

loading the first extracted data from the first response and the second extracted data from the second response into the inbound table.

7. The method of claim 1, further comprising:

storing the metric data in a plurality of tables based on the one or more configuration files.

8. The method of claim 7, wherein said step of calculating metric data includes:

associating one or more attributes with each generated metric, the one or more attributes also associated with at least one of the first extracted data and the second extracted data used to generate the metric.

9. The method of claim 8, further comprising:

transmitting the metric data to a presentation database; and

aggregating the metric data with respect to each metric attribute at the presentation database.

10. The method of claim 9, further comprising:

displaying the aggregated metric data for one or more metric attributes.

11. The method of claim 1, wherein a metrics engine generates the extraction tasks and provides the tasks to the staging database.

12. The method of claim 1, wherein the server extraction parameters include server identification information for one or more servers and database identification information for one or more databases located on each server.

13. The method of claim 9, further comprising:

accessing one or more display configuration files; and

displaying the aggregated metric data in a user interface based on the display configuration files.

14. The method of claim 13, further comprising configuring the user interface from the display configuration files.

15. The method of claim 14, wherein the display configuration files reference hierarchy levels from other configuration files for each metric to be displayed.

16. The method of claim 1, further comprising:

generating an outbound data table in the staging database from the one or more configuration files; and

loading the metric data into the outbound data table in the staging database.