amessina1

5 ms·

1. 1.▲
   by amessina1 6y ago

   I don't have deep knowledge of details of compute networks, there is a team of TSE who deal with network cases who know more than me. But the whole point of troubleshooting is not knowing what is wrong, but being able to find what
2. 2.▲
   by amessina1 6y ago

   Author of the article here. I only thought of the possibility of making a blog post after the case was closed and I started telling my colleagues about it, and realized I would have loved to read about this. The case was indeed fun to work
3. 3.▲
   by amessina1 6y ago

   For Google Cloud, 250$ per month per user: https://cloud.google.com/support
4. 4.▲
   by amessina1 6y ago

   I totally agree, but keep in mind that it is an iterative process: you have a case, you apply the runbook/playbook you have, if they are not enough you use your skill/knowledge to solve the case, then you update the playbooks.
5. 5.▲
   by amessina1 6y ago

   Follow the sun has a lot of overhead: imagine having to dump the engineers' thoughts and current hypothesis and load them in the brain of the next oncallers. Also it only really works if also the customer is active 24/7, as often
6. 6.▲
   by amessina1 6y ago

   1) you cannot have a runbook for everything, and even if you have a runbook you the best you could have found in this case is that something weird was happening in the VM. The setting had an insanely big value but it was accepted by the ker