#59 Who handles monitoring in your team and how?

Why many copy Google’s monitoring team setup

* Google’s Influence. Google played a key role in defining the concept of software reliability.

* Success in Reliability. Few can dispute Google’s ability to ensure high levels of reliability and its ability to share useful ways to improve it in other settings

BUT there’s a problem:

* It’s not always replicable. While Google's practices are admired, they may not be a perfect fit for every team.

What is Google’s monitoring approach within teams?

Here’s the thing that Google does:

* Google assigns one or two people per team to manage monitoring.

* Even with centralized infrastructure, a dedicated person handles monitoring.

* Many organizations use a separate observability team, unlike Google's integrated approach

If your org is large enough and prioritizes reliability highly enough, you might find it feasible to follow Google’s model to the tee.

Otherwise, a centralized team with occasional “embedded x engineer” secondments might be more effective.