Task extension for service level agreement state management

Abstract

Breaches of service level agreements (SLAs) of a computer network can be identified based on changes to statuses of components of the computer network. A status of a component of the computer network can be determined to have changed responsive to an event affecting the computer network. The component can be determined to be included in a list of components used to meet conditions of the SLAs. A record of a task table can be updated according to the changed status of the component responsive to determining that the component is included in the list of components. Records of the task table are associated with ones of the SLAs. It can then be determined that the changed status of the component prevents a condition of an SLA associated with the updated record from being met. The SLA can be identified as breached responsive to that determination.

1 - 20 . (canceled) 
     
     
         21 . A system, comprising:
 a processor; and   a memory, accessible by the processor, the memory storing instructions, that when executed by the processor, cause the processor to perform operations comprising:
 receiving an alert associated with one or more nodes of a service model, wherein each of the one or more nodes represents a respective configuration item (CI) in a configuration management database (CMDB); 
 performing an impact calculation against the one or more nodes based on the alert; 
 determining that a severity of the respective CI associated with one of the one or more nodes has changed responsive to the impact calculation; 
 determining that the changed severity prevents one or more conditions of a service level agreement (SLA) associated with the service model from being met; and 
 identifying the SLA as breached. 
   
     
     
         22 . The system of  claim 21 , wherein the SLA is associated with a task to be completed within an instance of a computing network. 
     
     
         23 . The system of  claim 22 , wherein the one or more conditions comprise a time period in which the task is to be completed. 
     
     
         24 . The system of  claim 21 , wherein the operations comprise updating a record associated with the SLA with data indicative of the changed severity of the respective CI. 
     
     
         25 . The system of  claim 21 , wherein determining that the changed severity prevents the one or more conditions of the SLA associated with the service model from being met comprises:
 determining that the condition requires an attribute associated with the respective CI to have a particular value; and   determining that the changed severity of the respective CI causes the attribute to have a different value than the particular value.   
     
     
         26 . The system of claim of  claim 21 , wherein the operations comprise providing, to a computing device, an indication that a computer infrastructure resource associated with the respective CI has been affected by the alert in response to determining that the severity of the respective CI has changed. 
     
     
         27 . The system of  claim 21 , wherein the operations comprise identifying the SLA from a plurality of SLAs associated with the service model in a database based on a determination that the respective CI is associated with the SLA. 
     
     
         28 . A method, comprising:
 receiving, via one or more processors, an alert associated with one or more nodes of a service model, wherein each of the one or more nodes represents a respective configuration item (CI) in a configuration management database (CMDB);   performing, via the one or more processors, an impact calculation against the one or more nodes based on the alert;   determining, via the one or more processors, that a severity of the respective CI associated with one of the one or more nodes has changed responsive to the impact calculation;   determining, via the one or more processors, that the changed severity prevents one or more conditions of a service level agreement (SLA) associated with the service model from being met; and   identifying, via the one or more processors, the SLA as breached.   
     
     
         29 . The method of  claim 28 , wherein the SLA is associated with a task to be completed within an instance of a computing network. 
     
     
         30 . The method of  claim 29 , wherein the one or more conditions comprise a time period in which the task is to be completed. 
     
     
         31 . The method of  claim 28 , comprising updating, via the one or more processors, a record associated with the SLA with data indicative of the changed severity of the respective CI. 
     
     
         32 . The method of  claim 28 , wherein determining, via the one or more processors, that the changed severity prevents the one or more conditions of the SLA associated with the service model from being met comprises:
 determining, via the one or more processors, that the condition requires an attribute associated with the respective CI to have a particular value; and   determining, via the one or more processors, that the changed severity of the respective CI causes the attribute to have a different value than the particular value.   
     
     
         33 . The method of  claim 28 , comprising providing, to a computing device via the one or more processors, an indication that a computer infrastructure resource associated with the respective CI has been affected by the alert in response to determining that the severity of the respective CI has changed. 
     
     
         34 . The method of  claim 28 , comprising identifying, via the one or more processors, the SLA from a plurality of SLAs associated with the service model in a database based on a determination that the respective CI is associated with the SLA. 
     
     
         35 . A non-transitory, computer-readable medium, comprising instructions that when executed by one or more processors, cause the one or more processors to perform operations comprising:
 receiving an alert associated with one or more nodes of a service model, wherein each of the one or more nodes represents a respective configuration item (CI) in a configuration management database (CMDB);   performing an impact calculation against the one or more nodes based on the alert;   determining that a severity of the respective CI associated with one of the one or more nodes has changed responsive to the impact calculation;   determining that the changed severity prevents one or more conditions of a service level agreement (SLA) associated with the service model from being met; and   identifying the SLA as breached.   
     
     
         36 . The non-transitory computer-readable storage medium of  claim 35 , wherein the SLA is associated with a task to be completed within an instance of a computing network. 
     
     
         37 . The non-transitory computer-readable storage medium of  claim 36 , wherein the one or more conditions comprise a time period in which the task is to be completed. 
     
     
         38 . The non-transitory computer-readable storage medium of  claim 35 , wherein the operations comprise updating a record associated with the SLA with data indicative of the changed severity of the respective CI. 
     
     
         39 . The non-transitory computer-readable storage medium of  claim 35 , wherein determining that the changed severity prevents the one or more conditions of the SLA associated with the service model from being met comprises:
 determining that the condition requires an attribute associated with the respective CI to have a particular value; and   determining that the changed severity of the respective CI causes the attribute to have a different value than the particular value.   
     
     
         40 . The non-transitory computer-readable storage medium of  claim 35 , wherein the operations comprise providing, to a computing device, an indication that a computer infrastructure resource associated with the respective CI has been affected by the alert in response to determining that the severity of the respective CI has changed.