• Site Reliability Engineer, takes care of the platform/site reliability and stability.
• Bridges the gap between development and operations.
• Manages risk.
• Leverages automation to reduce toil.
• Engineering approach to operations.

5 Action items to perform to transform from Ops to SRE.

• Work closely with product/development team.
• Break down the silos between product and ops.
• Automate as much as possible to reduce the toil.
• Incorporate engineering approach to operations.
• Being proactive rather than reactive.
• Set sli’s, slo’s, sla’s.
• Set Error budjets.
• Incident Management.

Top 10 SRE tools.

• Datadog
• Prometheus
• Grafana
• Kubenetes
• Docker swarm
• Gitlab CI/CD
• Docker
• Jenkins
• Chef
• Confluence
• Jira
• Ansible
• Terraform
• runDeck
• ELK

• Site Reliability Engineer, takes care of the platform/site reliability.
• Bridges the gap between development and operations.
• Engineering approach to operations.

2. Define 3-4 bullets points on migrating process of Ops to SRE?

• Work closely with product/development team.
• Automate as much as possible to reduce the toil.
• Incorporate engineering approach to operations.

3. 3 Characteristics to identify Toil in SRE

The task is said to be toil if it is:

• Manual
• Repetitive
• Not so value adding

4. 1 line explanation of SLI – SLO and SLA

• SLI – Indicators or Metrics that gauge service availability, latency, performance etc.
• SLO – Objectives set by product owner or SRE on availability, performance of a service etc.
• SLA – Agreement between product owner and client.

Ans: Devops is like an interface and SRE implements DevOps

Q2 – What SRE team is responsible for?

Ans: Monitoring, Automation of Operations.

Q3 – What is an error budget?

Ans: The amount of errors/downtime that is acceptable.

Q4 – What are MTTF (mean time to failure) and MTTR (mean time to repair)? What these metrics help us to evaluate?

Ans: MTTF is mean of times between the failure occurrences.
MTTR is is mean of times that took for repairing or solving the problem.

Q5 – What is the role of monitoring in SRE?

Ans: If any thing goes down, SRE steps in to the field, alerts the concerned application owner 

and makes efforts to get the app up again.

Q6 – How do you differentiate between process and thread?

Ans:  Process is like a molecule and threads are like atoms.

Q7 – What activity means Reducing Toil?

Ans: Automating the manual stuff.

Q8 – Have you ever heard of SLO? If yes then explain.

Ans: Yes, Service Level Objectives these are the objectives there are need to meet the SLA’s (Service Level Agreements).

Q9 – Enlist all the Linux signals you are aware of

Ans: SIGTERM, SIGKILL.

Q10 – What is obserbability

Ans: No idea, I think the extent of monitoring.