SLA Breach Detection via Task Table CI Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for managing service level agreements (SLAs) in computing networks lack the ability to efficiently monitor and manage SLA records, particularly in relation to computing infrastructure resources, leading to difficulties in identifying breaches and ensuring compliance with SLA conditions.
Innovation Solution
The implementation of a system that extends task data in an ITSM-based system to Configuration Items (CIs) within a Configuration Management Database (CMDB), using a task table to store and maintain data indicative of task records, SLA records, and CI records, allowing for impact calculation operations to determine changes in severity and identify SLA breaches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current systems for managing SLAs are used, then basic SLA tracking is maintained, but the ability to efficiently monitor and manage SLA records related to computing infrastructure resources is insufficient
Solution Approach 1:
The patent merges SLA management with ITSM task management by integrating SLA records into the task table. This allows SLA monitoring to leverage existing task management infrastructure, improving reliability without proportionally increasing system complexity. The task table now contains both task records and SLA records, creating a unified management approach.
Solution Approach 2:
The task table is designed to serve multiple functions: storing task records, SLA records, and CI records. This multi-functional approach allows a single data structure to handle diverse monitoring needs, improving SLA compliance monitoring while avoiding the complexity of separate dedicated systems for each function.
2Measurement precision
If task data is extended to include CI records in the task table, then impact calculation operations can identify SLA breaches, but the complexity of data management increases
Solution Approach 1:
The patent combines task records, SLA records, and CI records into a single task table. This integration enables impact calculation operations to directly assess how CI status changes affect SLA compliance, improving detection precision. The unified structure allows automated breach identification without requiring complex separate systems.
Solution Approach 2:
The system implements feedback mechanisms where impact calculation operations continuously monitor CI status changes and automatically update SLA breach status in the task table. This automated feedback loop improves detection precision by immediately identifying breaches when CI status changes prevent SLA conditions from being met.
3Difficulty of detecting and measuring
If monitoring tools are used to alert system administrators, then potential issues can be identified, but the ability to specifically identify SLA breaches based on component status changes is insufficient
Solution Approach 1:
The system performs preliminary impact calculation operations that proactively assess how CI status changes will affect SLA compliance before breaches occur. By pre-establishing the relationships between CIs and SLAs in the task table, the system can immediately identify breaches when status changes happen, reducing detection time.
Solution Approach 2:
The automated feedback mechanism continuously monitors CI status and immediately updates SLA breach status when conditions change. This real-time feedback eliminates manual detection delays, allowing system administrators to be alerted instantly when breaches occur, thereby reducing the time loss associated with identifying issues.
Data Source
AI summary
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.