Q: Can you define SLA, SLO, and SLI?
SLI (Service Level Indicator): A quantitative, mathematical measure of some aspect of the level of service provided. Example: "The percentage of HTTP GET requests to /home that return a 200 OK within 100ms.
Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In an interview, I explain how we designed actionable, symptom-based alerting using the Four Golden Signals. The interviewer is testing: SRE terminology and hierarchy.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
- SLI (Service Level Indicator): A quantitative, mathematical measure of some aspect of the level of service provided. Example: "The percentage of HTTP GET requests to
/homethat return a 200 OK within 100ms." - SLO (Service Level Objective): A target value or range of values for a service level that is measured by an SLI. Example: "The SLI will be 99.9% measured over a rolling 30-day window." It represents what the business defines as "healthy."
- SLA (Service Level Agreement): A legal and financial contract with the customer that outlines the consequences (penalties, refunds) if the SLO is not met. Example: "If we drop below 99.9%, we refund 10% of the monthly bill." SREs manage SLOs and SLIs; lawyers manage SLAs.
Remediation & Permanent Safeguards
Execute the resolution runbook and verify workload health:
- SLI (Service Level Indicator): A quantitative, mathematical measure of some aspect of the level o...
- SLO (Service Level Objective): A target value or range of values for a service level that is meas...
- SLA (Service Level Agreement): A legal and financial contract with the customer that outlines the...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability define High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
- Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability define Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
- Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability define Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
- Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability define Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.