Model-based system monitoring

• US 7,797,147 B2
• Filed: 04/15/2005
• Issued: 09/14/2010
• Est. Priority Date: 04/15/2005
• Status: Active Grant

• Current Assignee: ServiceNow Incorporated
• Original Assignee: Microsoft Corporation
• Inventors: Tabbara, Bassam, Voloshin, Vitaly, Rajarajan, Vij, Mensching, Rob, Sanghvi, Ashvinkumar J., Outhred, Geoffrey, Hunt, Galen C., Lakshminarayanan, Anand, Grealish, Kevin, Welland, Robert V., Vinberg, Anders B., Hydrie, Aamer
• Primary Examiner(s): Rodriguez; Paul L
• Assistant Examiner(s): Janakiraman; Nithya
• Application Number:
  US11/107,339
• Publication Number:
  US 20060232927A1
• Time in Patent Office: 1,978 Days
• Field of Search: 703/1, 703/22, 715/964, 715/733
• US Class Current: 703/22
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5019 Ensuring fulfilment of SLA
• CPC Class Codes: Y10S 715/964 CAD or CAM, e.g. interactive design tools

Abstract

Model-based system monitoring includes accessing a model of a system that includes multiple components and identifying relationships among the multiple components based on the model of the system. A proposed change to at least one of the multiple components is identified. A determination is made regarding an expected impact on the system caused by the proposed change. This determination is made, at least in part, based on the model of the system.

Claims

1. A method to determine whether one or more performance criteria of one or more service level agreements would be satisfied after implementing a proposed change to a software component, the method comprising:

accessing a scalable model of a system that includes a plurality of components, the scalable model expressed at least in part in an extensible language and adhering to a system definition model, the plurality of components comprising software components, and the scalable model comprising;

one or more service level agreement information pages accessible during operation of the system;

a plurality of associated pages of data for each of the plurality of components, and wherein the plurality of associated pages comprises;

an installation page;

a constraints page;

a monitoring page; and

a description page, wherein the description page comprises data describing characteristics of a component, wherein the characteristics comprise;

name of the component;

manufacturer of the component;

installation date of the component; and

performance characteristics of the component;

identifying relationships among the plurality of components based on the model of the system wherein the relationships comprise parent-child relationships wherein a parent component represents a roll-up of its child components;

providing one or more rules that use at least some of the identified relationships to express logic of the scalable model of the system;

identifying a proposed change to at least one of the software components;

determining an expected impact on performance of the system caused by the proposed change, the determination being made at least in part based on the logic of the scalable model of the system and at least in part based on expected impact on performance for one or more parent components of the system based on cumulative expected impact on performance of related child components wherein expected impact on performance comprises one or more causes other than component failure; and

based on the expect impact on performance of the system, determining whether one or more performance criteria of the one or more service level agreements information pages would be satisfied after implementing the proposed change wherein one or more performance criteria of a parent component depend on performance of the parent component'"'"'s child components.

2. A method as recited in claim 1, further comprising determining whether to implement the proposed change based on the expected impact on the system.

3. A method as recited in claim 1, wherein determining an expected impact on the system caused by the proposed change includes determining an expected impact on one or more of the plurality of components.

4. A method as recited in claim 1, wherein determining an expected impact on the system caused by the proposed change includes determining potential problems caused by implementing the proposed change.

5. A method as recited in claim 1, wherein the proposed change is the removal of a particular component from the system.

6. A method as recited in claim 1, wherein the proposed change is the addition of a new component to the system.

7. A method as recited in claim 1, further comprising:

identifying a second proposed change to another of the plurality of components; and

determining an expected impact on the system caused by the proposed changes.

8. A method to determine whether one or more performance criteria of one or more service level agreements would be satisfied after implementing a proposed change to a software component, the method comprising:

accessing a scalable model of a system that defines a plurality of components and defines relationships between those components, the scalable model expressed at least in part in an extensible language and adhering to a system definition model, the plurality of components comprising software components, and the scalable model comprising one or more service level agreement information pages accessible during operation of the system;

providing one or more rules that use at least some of the defined relationships to express logic of the scalable model of the system;

identifying a proposed change to at least one of the software components;

determining an expected impact on performance of a particular parent component in the system caused by the proposed change, the determination being made at least in part based on the logic of the scalable model of the system and being made at least in part based on cumulative expected impact on performance of the particular parent component'"'"'s related child components;

determining an expected impact on performance of the system caused by the proposed change, the determination being made at least in part based on the logic of the scalable model of the system and being made at least in part based on the expected impact on performance of the particular parent component wherein expected impact on performance comprises one or more causes other than component failure; and

based on the expect impact on performance of the particular parent component or based on the expected impact on performance of the system, determining whether one or more performance criteria of the one or more service level agreements information pages, associated with the particular parent component or the system, would be satisfied after implementing the proposed change wherein one or more performance criteria of the particular parent component depend on performance of the particular parent component'"'"'s child components.

9. A method as recited in claim 8, wherein determining an expected impact on performance of the system caused by the proposed change includes determining expected changes in a health of the system.

10. A method as recited in claim 8, further comprising determining whether to implement the proposed change based on the determined impact on the particular component and the determined impact on the performance of the system.

11. A method as recited in claim 8, further comprising:

identifying a second proposed change to another of the plurality of components; and

determining an expected impact on the system caused by the proposed changes.

12. A method as recited in claim 8, further comprising:

identifying a second proposed change to another of the plurality of components; and

determining an expected impact on a plurality of other components in the system caused by the proposed changes.

13. One or more computer readable storage media having stored thereon a plurality of instructions to determine whether one or more performance criteria of one or more service level agreements would be satisfied after implementing a proposed change to a software component that, when executed by one or more processors, causes the one or more processors:

identify a plurality of components in a system based in part on a system definition model wherein the plurality of components comprise software components and wherein the system definition model comprises one or more service level agreement information pages accessible during operation of the system;

express the identified components in an extensible language as a scalable model of the system that adheres to the system definition model;

identify relationships among the plurality of components;

provide one or more rules that use at least some of the identified relationships to express logic of the system;

define a proposed change to at least one of the software components;

determine an expected result of implementing the proposed change based at least in part on the logic of the system, wherein the expected result includes;

performance changes associated with at least one parent component of the plurality of components, the performance changes based on cumulative expected impact on performance of related child components wherein expected impact on performance comprises one or more causes other than component failure; and

performance changes associated with the system; and

based on the performance changes associated with the at least one parent component of the plurality of components or the performance changes associated with the system, determine whether one or more performance criteria of the one or more service level agreement information pages, associated with the at least one parent component of the plurality of components or the system, would be satisfied after implementing the proposed change wherein one or more performance criteria of a parent component depend on performance of the parent component'"'"'s child components.

14. One or more computer readable media as recited in claim 13, wherein the relationships among the plurality of components are identified based on the scalable model of the system.

15. One or more computer readable media as recited in claim 13, wherein the one or more processors further determine whether to implement the proposed change based on the expected result of implementing the proposed change.