Root at 16:21, 22 October 2025

2025-10-22T16:21:46Z

← Older revision		Revision as of 17:21, 22 October 2025
Line 104:		Line 104:

	== Service Level Agreements (SLAs) ==		== Service Level Agreements (SLAs) ==
	Formalized agreements with users or customers about the level of service they can expect. They often include consequences for not meeting those levels, such as financial reimbursements.~~<span id="purpose-of-an-sla"></span>~~		Formalized agreements with users or customers about the level of service they can expect. They often include consequences for not meeting those levels, such as financial reimbursements.

	== Purpose of an SLA ==		=== Purpose of an SLA ===
	* '''Define Expectations''': SLAs clearly define what the client can expect from the service provider. This clarity helps avoid misunderstandings.		* '''Define Expectations''': SLAs clearly define what the client can expect from the service provider. This clarity helps avoid misunderstandings.
	* '''Measurement and Monitoring''': They offer concrete metrics against which the service can be measured. This is crucial for assessing the service provider's performance.		* '''Measurement and Monitoring''': They offer concrete metrics against which the service can be measured. This is crucial for assessing the service provider's performance.
	* '''Compensation''': In cases where the agreed-upon service levels are not met, SLAs can provide a framework for compensations or penalties.		* '''Compensation''': In cases where the agreed-upon service levels are not met, SLAs can provide a framework for compensations or penalties.
	* '''Legal Protection''': In the event of disagreements or disputes, the SLA can serve as a reference or even as evidence.<span id="common-components-of-an-sla"></span>		* '''Legal Protection''': In the event of disagreements or disputes, the SLA can serve as a reference or even as evidence.<span id="common-components-of-an-sla"></span>
	~~== Common Components of an SLA ==~~

			=== Common Components of an SLA ===
	* '''Service Description''': A detailed description of the service being provided.		* '''Service Description''': A detailed description of the service being provided.
	* '''Performance Metrics''': Clear metrics that will be used to measure the performance of the service. Examples include uptime percentages, response times, and resolution times.		* '''Performance Metrics''': Clear metrics that will be used to measure the performance of the service. Examples include uptime percentages, response times, and resolution times.
Line 123:		Line 123:
	* '''Termination Conditions''': Under what circumstances the agreement can be terminated by either party.		* '''Termination Conditions''': Under what circumstances the agreement can be terminated by either party.
	* '''Review and Modification Procedures''': Specifies how and when the SLA will be reviewed and the procedures to modify it.<span id="types-of-slas"></span>		* '''Review and Modification Procedures''': Specifies how and when the SLA will be reviewed and the procedures to modify it.<span id="types-of-slas"></span>
	~~== Types of SLAs ==~~

			=== Types of SLAs ===
	* '''Customer-Based SLA''': An agreement with an individual customer group, covering all the services they use. For instance, a company might have an SLA with its ISP or cloud provider.		* '''Customer-Based SLA''': An agreement with an individual customer group, covering all the services they use. For instance, a company might have an SLA with its ISP or cloud provider.
	* '''Service-Based SLA''': An agreement for a specific service, irrespective of the customer using it. For example, a cloud provider might have an SLA that applies to all its storage or compute services.		* '''Service-Based SLA''': An agreement for a specific service, irrespective of the customer using it. For example, a cloud provider might have an SLA that applies to all its storage or compute services.
	* '''Multi-Level SLA''': This divides the agreement into different levels, each addressing different sets of customers for the same services, in the same SLA.<span id="monitoring-and-enforcement"></span>		* '''Multi-Level SLA''': This divides the agreement into different levels, each addressing different sets of customers for the same services, in the same SLA.<span id="monitoring-and-enforcement"></span>

	= Monitoring and Enforcement =		=== Monitoring and Enforcement ===
	It's crucial for both parties to continuously monitor the parameters mentioned in the SLA. Many companies use specialized software to automate this process. If an SLA is breached, the agreed-upon remedies or penalties come into play.~~<span id~~=~~"sla-~~vs.~~-ola"></span>~~		It's crucial for both parties to continuously monitor the parameters mentioned in the SLA. Many companies use specialized software to automate this process. If an SLA is breached, the agreed-upon remedies or penalties come into play.

			== SLA vs. OLA ==
			It's worth noting the distinction between SLAs and OLAs (Operational Level Agreements). While SLAs are made with external customers or between departments, OLAs exist internally between different teams in an organization, helping them provide a consistent level of service to each other.

	~~= SLA vs. OLA =~~
	It's worth noting the distinction between SLAs and OLAs (Operational Level Agreements). While SLAs are made with external customers or between departments, OLAs exist internally between different teams in an organization, helping them provide a consistent level of service to each other.<span id="error-budget"></span>
	= Error Budget =		= Error Budget =

	The difference between 100% uptime and the SLO. If a service has an SLO of 99.9% uptime, then it has an error budget of 0.1% downtime. This budget allows for planned outages, deployments, and other activities without breaching the SLO.		The difference between 100% uptime and the SLO. If a service has an SLO of 99.9% uptime, then it has an error budget of 0.1% downtime. This budget allows for planned outages, deployments, and other activities without breaching the SLO.
	[[Category:Devops definitions]]		[[Category:Devops definitions]]

Root at 16:20, 22 October 2025

2025-10-22T16:20:31Z

Show changes

Maintenance script: Added category Devops definitions

2025-10-19T17:51:07Z

Added category Devops definitions

← Older revision		Revision as of 18:51, 19 October 2025
Line 142:		Line 142:
	<!-- From bodyContent 1543245.mraw -->		<!-- From bodyContent 1543245.mraw -->

			[[Category:Devops definitions]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/Devops definitions/Site Reliability Engineering to Site Reliability Engineering: Cleaned title and categorized

2025-10-19T17:51:06Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/Devops definitions/Site Reliability Engineering to Site Reliability Engineering: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 06:30, 21 April 2025

2025-04-21T06:30:00Z

Show changes

imported>Unknown user at 06:30, 21 April 2025

2025-04-21T06:30:00Z

← Older revision	Revision as of 07:30, 21 April 2025
(No difference)

imported>Unknown user at 06:30, 21 April 2025

2025-04-21T06:30:00Z

New page

Site Reliability Engineering - Revision history

Root at 16:21, 22 October 2025

Root at 16:20, 22 October 2025

Maintenance script: Added category Devops definitions

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/Devops definitions/Site Reliability Engineering to Site Reliability Engineering: Cleaned title and categorized

imported>Unknown user at 06:30, 21 April 2025

imported>Unknown user at 06:30, 21 April 2025

imported>Unknown user at 06:30, 21 April 2025