Once, when I picked up a book from the local library, the librarian asked to tell her what I thought about the book when I would bring it back. Well, why not write a few lines about all the books I read so everybody could see what I thought about it? I'm often also happy to have friends recommend a certain book or tell me this and that is not really worth reading. I won't comment about the tons of books I have read so far, but about books I read from now on.
| highly recommended | sehr empfohlen | |
| good reading | gutes lesematerial | |
| average | durchschnittlich | |
| not too interesting | nicht allzu interessant | |
| recommended not to read it | empfehlung das buch nicht zu lesen |
 |
|
|---|---|
| title | Monitoring Distributed Systems |
| author | Rob Ewaschuk |
| ISBN-10 | |
| ISBN-13 | |
| ASIN | |
| rating | |
| date | 2016-Sep-29 |
This is a short writeup of what considerations Site Reliability Engineering at Google take into account when building infrastructure monitoring systems. What they monitor, what they alert or do not alert, what to correlate or not and why. It definitely is not a 'how to monitor your infrastructure' but it does give some insight into the experience some people responsible for large and dynamic environments have made with monitoring and alerting and gives some of their reasoning why they do some things this way. So spending the one hour or less to go over this report might well save you many hours of preliminary trial-and-error and offer you a head start.
