Real-time SLA impact analysis

• US 9,667,552 B2
• Filed: 09/26/2003
• Issued: 05/30/2017
• Est. Priority Date: 09/26/2003
• Status: Active Grant

• Current Assignee: Maplebear Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Rendahl, Randy Allan, Fisher, Bradford Austin
• Primary Examiner(s): Nguyen, Phuoc
• Assistant Examiner(s): Belani, Kishin G
• Application Number:
  US10/672,777
• Publication Number:
  US 20050071458A1
• Time in Patent Office: 4,995 Days
• Field of Search: 709224
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 43/091 Measuring contribution of individual network components to actual service level
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS

Abstract

A system, method and apparatus for performing a real-time service level agreement (SLA) impact analysis. In the system of the invention, a service level manager can be programmed to establish a plurality of SLAs directly implicating selected resources. A relationship database further can be configured for coupling to one or more management applications programmed to manage the selected resources. Finally, a modeling and evaluation system can be communicatively coupled to the relationship database and the service level manager and programmed to perform a real-time SLA impact analysis based both upon resources directly implicated by the SLAs and also upon resources which are related to the resources directly implicated by the SLAs.

Claims

1. A method for performing a real-time service level agreement (SLA) impact analysis, the method comprising the steps of:

detecting by a processor of the computer an event arising from a specific resource from amongst the different resources within a first SLA;

identifying the specific resource for the detected event;

analyzing the first SLA to identify different resources within the first SLA;

determining whether based upon said event said specific resource cannot perform adequately enough so as to meet a term within the first SLA that directly specifies said specific resource;

on condition that it is determined that the first SLA specifies the specific resource and that the specific resource in consequence of the event cannot perform adequately enough to meet the term within the first SLA, generating a notification in the memory of the computer, but otherwise consulting a hierarchy of resources to determine whether other resources in the hierarchy depend upon the specific resource and if so, also generating the notification;

analyzing each of several different SLAs to identify different resources within the several different SLAs and further determining whether based upon said event said specific resource inhibits another different resource from performing adequately enough so as to meet a different term within the several different SLAs; and

,

generating the notification in the memory of the computer on condition that based upon said event said specific resource inhibits another different resource from performing adequately enough so as to meet a different term within the different SLAs but otherwise consulting a hierarchy of resources to determine whether other resources in the hierarchy depend upon the specific resource and if so, also generating the notification.

2. The method of claim 1, further comprising the step of establishing the hierarchy of resources within a shared database through which a relationship can be recognized between said specific resource and said another resource in said further determining step.

3. The method of claim 1, wherein said detecting event comprises the step of receiving an event from a management application charged with managing said specific resource.

4. A system of performing a real-time service level agreement (SLA) impact analysis comprising:

a hardware processor configured to;

detect an event arising from a specific resource from amongst the different resources within a first SLA;

identify the specific resource for the detected event;

analyze a first SLA to identify different resources within the first SLA;

determine whether based upon the event the specific resource cannot perform adequately enough so as to meet a term within the first SLA that directly specifies said specific resource;

on condition that it is determined that the first SLA specifies the specific resource and that the specific resource in consequence of the event cannot perform adequately enough to meet the term within the first SLA, generate a notification in the memory of the computer, but otherwise consult a hierarchy of resources to determine whether other resources in the hierarchy depend upon the specific resource and if so, also generating the notification;

analyze each of several different SLAs to identify different resources within the several different SLAs and further determine whether based upon the event the specific resource inhibits another different resource from performing adequately enough so as to meet a different term within the several different SLAs; and

,

generate the notification on condition that based upon the event, the specific resource inhibits another different resource from performing adequately enough so as to meet the different term within the different SLAs but otherwise consult a hierarchy of resources to determine whether other resources in the hierarchy depend upon the specific resource and if so, also generate the notification.

5. The system of claim 4, wherein the hierarchy of resources is established within a shared database through which a relationship can be recognized between the specific resource and the another resource.

6. A non-transitory machine readable storage having stored thereon a computer program for performing a real-time service level agreement (SLA) impact analysis, the computer program comprising a routine set of instructions for causing the machine to perform the steps of:

detecting by a processor of the computer an event arising from a specific resource from amongst the different resources within a first SLA;

identifying the specific resource for the detected event;

analyzing the first SLA to identify different resources within the first SLA;

determining whether based upon said event said specific resource cannot perform adequately enough so as to meet a term within the first SLA that directly specifies said specific resource;

on condition that it is determined that the first SLA specifies the specific resource and that the specific resource in consequence of the event cannot perform adequately enough to meet the term within the first SLA, generating a notification in the memory of the computer, but otherwise consulting a hierarchy of resources to determine whether other resources in the hierarchy depend upon the specific resource and if so, also generating the notification;

analyzing each of several different SLAs to identify different resources within the several different SLAs and further determining whether based upon said event said specific resource inhibits another different resource from performing adequately enough so as to meet a different term within the several different SLAs; and

,

generating the notification in the memory of the computer on condition that based upon said event said specific resource inhibits another different resource from performing adequately enough so as to meet a different term within the different SLAs but otherwise consulting a hierarchy of resources to determine whether other resources in the hierarchy depend upon the specific resource and if so, also generating the notification.

7. The machine readable storage of claim 6, further comprising the step of establishing the hierarchy of resources within a shared database through which a relationship can be recognized between said specific resource and said another resource in said further determining step.

8. The machine readable storage of claim 6, wherein said detecting event comprises the step of receiving an event from a management application charged with managing said specific resource.