Thursday, Green-House, 10:00

• Convener / Facilitator : Aaron
• Note taker : Denis

• Marco
• Gogs
• Martha
• Ben
• Aaron
• Denis
• Jeff

A lot of the people present are devs. and are looking for pointers on doing ops work. Is there more than logs to look at ? When troubleshooting start with the simple things and work to the most complex. Assume that the thing you have personally broken it and work from there (sort it from there) . Read a lot of blogs. Google is your friend. monitor the shit out of everything instrument the code please devs. Understand the stack - you cannot know everything. But make sure you know your bit. Own the thing in its runtime state. IT is a young industry (when compared to manufacturing) .

Dev can write monitoring tools for the apps they build. (Build it, Own it, Run it) Document the things, use a knowledge base, like a Wiki (use a internal wiki perhaps).

Before you automate something do the item by hand. Do not automate what you do not know Keep your shell history (save it to a file). Go remote, Rundeck are good remote tools to use. Opensource Q&A could be good if you cannot use Stack Overflow or something similar. A book “Problem Solving 101” is a good book on the subject. "Five whys" is to continuously ask questions to get to the root cause of a problem. "Lean Coffee" supports the problem solving process by allowing facilitation.

It should be OK to ask simple questions.
The only stupid question is the one you don’t ask.