A service-level-agreement (SLA) is a formal contractual arrangement between a service provider and its customers that specifies measurable performance targets (such as availability, response time, and throughput), defines the responsibilities of each party, and establishes remedies or penalties for failure to meet agreed-upon levels. Parameters: (1) the measurable metrics that quantify service quality, (2) the reporting and monitoring mechanisms used to track compliance, (3) the escalation procedures when targets are breached, (4) the remediation or compensation terms for non-compliance. The SLA persists through legal documentation, organizational practice, and ongoing service review cycles that enforce accountability between provider and customer. [formal: SLA | substrate: behavior | horizon: a life | explicit: yes | epoch: 0.04]
Accepted ontology entry
service-level-agreement
A service-level-agreement (SLA) is a formal contractual arrangement between a service provider and its customers that specifies measurable performance targets (such as availability, response time, and throughput), defines the responsibilit…
Definition
Why it is in scope
A human-made contractual agreement between a service provider and its customers that defines the expected level of service, including measurable targets, responsibilities, and remedies. It is a formal business construct used in IT service management and cloud computing.
Names and aliases
- service-level-agreementen · CANONICAL
Relations from this entry
- cmr93jl68006shcxfbwjsx1nlINSTANCE_OF →
a service-level-agreement is a specific kind of contract. Per Law 9: specific→general. Competent-speaker test: 'an SLA is a contract.' The nearest kind is contract — no intermediate category between contract and SLA.
- cms7wyk72004ph6s8d82lhwqlSERVES →
SLAs specify reliability targets (uptime, MTTR, availability thresholds) — they are designed and maintained for the sake of driving reliability improvement. Per Law 8d: servant (SLA) points at master (reliability); the note shows purpose by sustained practice in DevOps/SRE.
Relations to this entry
No accepted relations in this direction.
Record identity
- Created
- Aug 7, 2026, 10:20 AM UTC
- Content hash
- f92dea8ceed8178e80d2fa295a52518b01a9278bb3f211f66bee61834d85a5d2