SRE

99.999% of environment availability :)

SRE brings a perspective of the value being delivered to the customer more so than devops which usually stops at delivery into production.

turning around the business model. - from reactive to proactive

SRE practices is rather complementary to DevOps. It focuses on customer satisfaction.

@drkurta Excellent - so Ops into DevOps :-)

@RjSriram15 But why? Can you substantiate the cost/value trade-off? Especially if the underlying network infra is less reliable?

Understanding customer journey is really hard for eng teams #sre

treat issues with same respect as new features / enhancements

Establishing a "universal language" across the whole org of reliability based on user happiness

Top to down approach - renegotiating contracts. - move away from SLA driven approach

SRE can also help with scaling individual devops team practices across the organization - working as a platform team (a la _Team Topologies_)

preventing churn - continuous relationship rather one -time contract

SLA --> SLOs & SLIs --> OKRs

focusing on how the end user/customer is impacted across all aspects of development and operations

Writing your customer journey + success is hard. If the business can't do it - engineers don't have a chance to succeed. #sre #devops

@RjSriram15 At a certain point of baseline reliability, you need to focus on containment and quick remediation of incidents to achieve more overall reliability.

> SLIs --> OKRs

This part is a subject for debate. SLIs should be indeed metrics for measuring Key Results in the OKR framework, but at the same time not all KRs should be measurable as SLIs

@oleg_nenashev yes indeed words matter too. sticking with the agreed objective for time to learn is key. orgs tend to have little patience

(edited)

@RjSriram15 or the other direction?

@dbmahon indeed many orgs have little patience and even less long-term strategy. Some of them confuse lack of patience and failing fast unfortunately. So they always fail...

@DBMahon most of the organizations today are reactive and are still at SLAs.. There should be a roadmap to move in both the directions

Do not hire sre engineers from market. in house talents with environment knowledge are their assets

Hopefully it starts with the right mindset and desire to become more proactive.

set realistic goals

@RjSriram15 +1 yes but don't leave to their own devices. give them resources, training and tools

The mindset is really critical - along with executive support.

Focus on Ops aspects of DevOps. - Toil reduction , Error Budgets , Measurement (SLI,SLO ..) , Observability

differentiate practices for DevOps and SRE. People has many misconception

@drkurta yes it costs money and time to improve reliability and it's a journey. never one and done.

@_YEG yes get clear definitions and roles and don't overload the teams with unrealistic expectations.

get management buy-in ? do you have a business case here ..

We actually wrote an ebook on this very subject! Check it out: https://info.blameless.com/bridging-the-gap-devops...

If you're invested in DevOps, you have a lot of resources to leverage for your SRE solution. It's all about orienting to new practices with the tools you have :)

not one size fit all

perhaps drowning in sev0 or sev1 incidents will get attention. Not ideal however.

Mindset regarding culture change needs to show that you are not a prisoner of your past, you are a pioneer of your future.

SRE brings human in the loop #SRE

Small improvements, implemented on an ongoing basis, compound into significant changes. See @bvssh (and the book)!

have a team of experts from varied skills and solve problems collectively

AI based monitoring

-Buy-in mindset and not carrying the same baggage from the past

Reliability Engineering platform - is for everyone #lowcode

Datascience integration into SLI,SLO modelling , error budgets & policies

auto remediation engine??

agreeing on SLOs is really hard for disparate, large teams

@RjSriram15 interesting

Integrating with the tools used across the pertinent teams - reduces the onboarding effort

SLOs and SLIs to contextualize based on user impact

integrating - SRE tools and orchestrating it in secure & reliable way

Reliability doesn't only mean fixing the issues, but also the communication to customers as these issues are being fixed. Communication is something that a lot of service providers struggle with, which can impact how users view how "reliable" a service is.

Effectively collecting info across all systems (both social and technical) which contribute to the systemic reliability is key

@drkurta how do we add features of social engineering to #SRE platform

@bajpaigarima1A Reliability Engineering platform is about people, processes and tools and automation and how data and communication flows.

@drkurta something like gamification

So far, facilitating reflection through retrospective processes along with the good management practices that support psychological safety is the best that we have

The field of cognitive systems engineering has a lot of insight on how to reduce cognitive load and make the tools into good co-workers

(edited)