SRE

coming together for a shared goal as a team as well

I think it can be helpful to think of SRE in maturity stages, but we shouldn't get overwhelmed or intimidated by an idealized SRE... there's lots of small practical changes that orgs new to SRE can implement today

Practice of practice

I'm not a big fan of discussing "maturity" vs. "immaturity", because there are many paths toward achieving the right level of reliability. See https://cloud.google.com/blog/products/devops-sre/...

IMO it's only Reliability Engineering and not reliability engineer

Best reference I can provide is someone who works to move the organization up stages of Hollnagel's resilience practices: https://erikhollnagel.com/ideas/resilience-enginee...

An SRE's full scope can be huge - everything from writing code, to building infrastructure, to championing cultural changes!

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

Our @blamelesshq platform automates at least as far as triggering incidents. But by policy we don't poke into your systems directly. We leave that to you or your other tools - but shoreline.io is really interesting.

interesting .. blameless + keptn + (SREs ) :-)

@bajpaigarima1 @drkurta yes! In Keptn we have many integration services (aka plugins), and also generic integrations through webhooks and scripts/CLIs. Should be possible to integrate with @blamelesshq for incident management: https://artifacthub.io/packages/search?org=keptn

common vocabulary building starts with education & awareness and not leaving anyone behind

Do incident post mortems help non engineers understand incidents? @bajpaigarima1

the business leaders should also talk in the same vocabulary as engineers.. ;)

Postmortems are great for eng + devops teams to learn but how do you elevate to others?

connecting the business, users and technology with a common language is a typical task of a business analyst

@WSzepesi the in-between 'glue' is helpful but it doesn't bring the teams closer together. it's a translation agent

Sales, marketing, CS, and product teams could really leverage reliability as a distinct advantage over their closest competitors. The next step is simply to get business and SRE teams on that same page by focusing on user experiences.

But when developers are shipping hundreds of changes every day, can the biz analysts really keep up? It's important to practice empathy across all biz functions - which requires people to understand each other's values and language

I think by crafting retrospectives to include a breakdown of user impact, other teams can use them to understand how users are feeling and what solutions they can bring to help them

Yes, the whole requirement for Business Analysts is caused by different cultures needing a translator!

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)