Search for a command to run...
Cloud Specialist with expertise in SRE, infrastructure, and security. Certified in CKA, LPIC-3 (Security), and AZ-104 My focus rests on three pillars: Cloud Architecture, Security, and Containerization, currently integrating AI to drive operational efficiency.
No comments yet. Be the first to comment.
1. Container Management (Lifecycle) CommandPurposeExample docker psList running containers.docker ps -a (to see all containers, including those that exited with errors). docker runCreate and start a container.docker run -d --name web nginx (r...
1. System Observability & Performance CommandPurposeReal-World SRE Example top / htopProcess monitoring.htop (to visually identify which CPU core is pinned at 100%). uptimeSystem load average.uptime (to check if the load average exceeds the n...
Automate to scale, not just to survive In the world of Site Reliability Engineering (SRE), not all automation is created equal. There is a silent enemy that consumes engineer’s time, stalls innovation, and drains operational budgets: Toil. If your da...
In infrastructure, you don't guess—you verify. Whether you're debugging a Kubernetes CNI or a cloud-native database, knowing the underlying protocol is the key to faster troubleshooting. Here is a cheat sheet of the 25 most important protocols and th...
The Incident Doesn't End at the "Fix" In the daily life of an SRE, the first reaction to a downtime is the "Quick Fix": restarting a pod, scaling a node, or triggering a rollback. However, an incident isn’t truly closed when the service returns to no...
In the world of infrastructure, we often obsess over whether a server is "alive" (ping). But a business doesn't care about a ping; it cares about the user experience.
To understand this, let's step away from the data center for a moment and imagine we are the owners of a busy Burger Restaurant.
The SLI is the raw, real-time measurement of what is happening right now. It is a snapshot of reality.
In the Restaurant: It’s the exact time it takes for a waiter to bring a burger to the table after the customer orders.
In SRE: It’s the latency (e.g., 300ms) or the success rate of requests (e.g., 99.9% of responses are 200 OK).
Rule of thumb: The SLI answers the question: "How is the service performing at this very second?"
The SLO is the target you set for your team to keep the customers happy. It’s your "Line in the Sand."
In the Restaurant: You decide that 95% of burgers must be served in under 15 minutes.
In SRE: 99.9% of requests to the Azure API must respond in less than 200ms over a rolling 30-day window.
Key Concept: The SLO is the balance between user happiness and operational cost.
The SLA is what you promise the customer in writing, including the consequences if you fail.
In the Restaurant: You hang a sign on the door: "If your food takes longer than 30 minutes, it’s free!" * Note that the SLA (30 min) is much more relaxed than your internal goal/SLO (15 min). This gives you a "safety buffer."
In SRE: This is the legal contract. If the platform falls below 99% uptime, the provider must pay back credits or refunds.
| Acronym | Name | Who watches it? | What happens if it fails? |
| SLI | Indicator | The Engineer | We tune the code or the resources. |
| SLO | Objective | The SRE Team | We stop new changes (Error Budget). |
| SLA | Agreement | The Lawyer / Client | There are financial consequences. |
If your SLO is to deliver 95% of burgers on time, you have a 5% margin of error. That is your Error Budget.
Budget is full? You can spend that 5% experimenting with a risky new recipe (Innovation).
Budget is empty? You made too many mistakes this month. Stop experimenting and focus 100% on making the kitchen stable (Reliability).
The AI acts like a Highly Intelligent Kitchen Supervisor:
Detection: The AI notices the oil is taking 2 degrees longer to heat up before the meat comes out undercooked (AIOps).
Prediction: It warns you: "At the current rate you're burning burgers, you'll have to start giving them away for free in 3 days (SLA breach prediction)."
Action: If it sees a crowd coming, it automatically fires up a second grill (e.g. Auto-scaling in Azure).
At the end of the day, whether you are managing a Raspberry Pi at home or a multi-region infrastructure with Azure or AWS, the lesson is the same: You cannot manage what you do not measure.
The SLI, SLO, and SLA framework isn't just a set of acronyms; it is a shared language between technology and business.
SLIs give us the truth.
SLOs give us a goal.
SLAs define our commitment.
By mastering this framework—and accelerating it with AI—you stop being the person who "fixes servers" and become the architect who ensures the business can keep its promises to its users. Reliability is not a lucky accident; it is a calculated decision.
