SLA Decomposition: given high level Service Level Objectives (SLOs), translate the SLOs to low level system thresholds. The system thresholds are used to created an effective design to meet the SLOs. determine resource allocation for each individual component. determine software configuration. SLOs monitoring and assessment. SLA Decomposition. Service Level Objectives (SLOs) response time. throughput. workload. system. metrics. application. attributes. healthy. ranges. low level system thresholds. Enterprise applications and services have to be designed to meet service level agreements or SLA. Enterprise applications and services are typically comprised of a number of components or systems, which interact with one another in a complex manner. Each sub-system or component potentially affects the overall behavior of the service, and the high level goal. Any high level goal specified for a service in SLA potentially relates to low level system components. One of the key tasks during the design state is to ensure the service to behave satisfactorily before putting in production. The problem we are trying to solve is the given an SLA, translate the service level objectives specified in the SLA to low level system thresholds. Resource requirements of each component involved in providing the service, Configuration parameters for software. Healthy ranges or bounds of low level metrics. These low level thresholds can be then used to create an effective design and ensure the SLAs. For example The system thresholds are used to determine how much and how many of the resources should be allocated to satisfy the proposed SLOs. For configure the software and for online SLA monitoring and assessment. 60 sec. Company Confidential.