US 7,398,511 B2Granted

System and method for providing a health model for software

AssigneeMicrosoft Corporation

InventorsAhmed El-Shimi, Christopher W. Hallum, Martin Edward Hough, Lorenzo Rizzi, Anil Kumar Yadav

Life of this patent

Estimating the term…

Loading patent…

Abstract

A health model builder may construct a health model from instrumentation of software. To do so, the instrumentation of the software component may be mapped to states of operation of the software component and the instrumentation may be grouped together. A health model may be built with the states of operation resulting from mapping the instrumentation to states of operation of the software component and with transitions between the states of the health model that represent an occurrence of instrumentation in an instrumentation group. The system allows for identification of anti-alert instrumentation to be added where instrumentation is missing for reporting recovery from failure. Moreover, a blame component may be identified for any instrumentation of a software component that indicates it failed because of another software component.

Claims37

Dependent claims

A computer system for building a health model of software components, comprising one or more computer processors, system memory, and one or more physical computer-readable media having stored thereon computer-executable instructions which, when executed, perform a method comprising:

creating an inventory of instrumentation of the software components:
mapping each individual instrumentation in the inventory of instrumentation to a state of operation of the software components before the instrumentation is generated, the state of operation before the instrumentation is generated being from a list comprising running, failed, stopped, paused, non-activated, and activated;
mapping each individual instrumentation in the inventory of instrumentation to a state of operation of the software components after the instrumentation is generated, the state of operation before the instrumentation is generated being from a list comprising running, failed, stopped, paused, non-activated, and activated;
analyzing the inventory to identify instrumentation that result in the same transition from one state of operation of the software components to another state of operation of the software components;
grouping the identified instrumentation that result in the same transition from one state of operation of the software components to another state of operation of the software components by filtering the instrumentation based upon the state of the operation of the software component before instrumentation was generated and the state of operation after the instrumentation was generated;
generating the health model using the states of operation and at least one transition representing a group of instrumentation from one state of operation of the software components to another state of operation of the software components;
and
representing the health model in a table comprising fields including an event group, an event identification, the state before an event occurs, the state after an event occurs, an anti-alert, a remedy, a blame component, and a description.

5 more elements

A method for building a health model of a software component, comprising the steps of:

creating an inventory of instrumentation of the software component;
mapping each individual instrumentation in the inventory of instrumentation to a state of operation of the software component before the instrumentation is generated, the state of operation before the instrumentation is generated being from a list comprising running, failed, stopped, paused, non-activated, and activated;
mapping each individual instrumentation in the inventory of instrumentation to a state of operation of the software component after the instrumentation is generated, the state of operation before the instrumentation is generated being from a list comprising running, failed, stopped, paused, non-activated, and activated;
analyzing the inventory to identify instrumentation that result in the same transition from one state of operation of the software component to another state of operation of the software component;
grouping the identified instrumentation that result in the same transition from one state of operation of the software component to another state of operation of the software component by filtering the instrumentation based upon the state of the operation of the software component before instrumentation was generated and the state of operation after the instrumentation was generated;
generating the health model using the states of operation and at least one transition representing a group of instrumentation from one state of operation of the software component to another state of operation of the software;
and
representing the health model in a table comprising fields including an event group, an event identification, the state before an event occurs, the state after an event occurs, an anti-alert, a remedy, a blame component, and a description.

5 more elements

Dependencies are inferred from the claim text.