Model-based system monitoring

• US 20060232927A1
• Filed: 04/15/2005
• Published: 10/19/2006
• 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., Hydrie, Aamer, Vinberg, Anders
• Granted Patent: US 7,797,147 B2
• Time in Patent Office: Days
• US Class Current: 361/679.20
• 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 comprising:

accessing a model of a system that includes a plurality of components;

identifying relationships among the plurality of components based on the model of the system;

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

determining an expected impact on the system caused by the proposed change, the determination being made at least in part based on the model of the system.

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 expected changes in performance of the system.

5. A method as recited in claim 1, wherein determining an expected impact on the system caused by the proposed change includes determining whether a service level agreement associated with the system would be satisfied after implementing the proposed change.

6. 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.

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

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

9. A method as recited in claim 1, wherein the model of the system includes an associated page of data for each of the plurality of components, and wherein the associated page of data defines an operation of the associated component.

10. 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.

11. A method comprising:

accessing a model of a system that defines a plurality of components and defines relationships between those components;

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

determining an impact on a particular component in the system caused by the proposed change, the determination being made at least in part based on the model of the system; and

determining an impact on performance of the system caused by the proposed change, the determination being made at least in part based on the model of the system.

12. A method as recited in claim 11, 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.

13. A method as recited in claim 11, wherein determining an expected impact on performance of the system caused by the proposed change includes determining whether a service level agreement associated with the system would be satisfied after implementing the proposed change.

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

15. A method as recited in claim 11, 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.

16. A method as recited in claim 11, 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.

17. One or more computer readable media having stored thereon a plurality of instructions that, when executed by one or more processors, causes the one or more processors to:

identify a plurality of components in a system;

identify relationships among the plurality of components;

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

determine an expected result of implementing the proposed change, wherein the expected result includes;

performance changes associated with at least one of the plurality of components; and

performance changes associated with the system.

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

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

20. One or more computer readable media as recited in claim 17, wherein the one or more processors further determine whether a service level agreement associated with the system would be satisfied if the proposed change is implemented.