News for hackers. Stuff that matters.

A comment on Finding a problem at the bottom of the Google stack. Parent comment

Re:Finding a problem at the bottom of the Google stack by mjw1007 on Sunday March 15, 2020 @12:41PM (#22584429)
Right. High temperature and thermal throttling are things that can and should be monitored directly.

Spotting it by digging down from service-level monitoring instead isn't terrible, but it isn't something to be proud of either.

[ Parent | on HN ]
Re:Finding a problem at the bottom of the Google stack by thedance on Sunday March 15, 2020 @02:04PM (#22585249)
It’s just the org chart being reflected in their stack architecture. There is a group responsible for machine health. That group doesn’t run any services. There is a group that operates GFEs. They don’t own any machines.
[ Parent | on HN ]
Re:Finding a problem at the bottom of the Google stack by fragmede on Monday March 16, 2020 @03:56AM (#22590868)
Does that imply a SaaS-based revision to Conway's law?

(GFEs are a reverse proxy that terminates TCP for Google. https://landing.google.com/sre/sre-book/chapters/production-... )

[ Parent | on HN ]
Re:Finding a problem at the bottom of the Google stack by bryanrasmussen on Sunday March 15, 2020 @01:55PM (#22585171)
maybe something to be proud of by the person who actually did the digging down.
[ Parent | on HN ]