Get full access to Business Intelligence and the Cloud: Strategic Implementation Guide and 60K+ other titles, with a free 10-day trial of O'Reilly.
There are also live events, courses curated by job role, and more.
Traditionally, the service level agreement (SLA) has been thought of as pertaining to technologies that require a particular quality of service (QOS) in order to ensure availability and response time on a network. QOS also applies to cloud computing but in that context must be expanded past availability and response time to include other business parameters, like data retention and drivers of business continuity. The cloud SLA is essential so organizations know the minimum level of service they can expect and the providers know the minimum level of service they must provide. The SLA must also specify what occurs when a provider does not meet the SLA's business parameters. The overarching purposes of the SLA are as follows:
A typical SLA includes the following specifications: (1) service availability, (2) the length of time a provider has to rectify any issue with the service, and (3) service monitoring. These specifications are set out in a number of measurable objectives and consequences in case they are not met. Typically, there are two types of QOS objectives: (1) operational (e.g., mean time between failures), and (2) service specific (e.g., availability or delay). 2 Operational and service specific objectives are discussed next .
Get Business Intelligence and the Cloud: Strategic Implementation Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.