[Gllug] Modern Fault finding techniques

[Aaron Trevena]

On 18 November 2011 12:23, James Hawtin <oolon at ankh.org> wrote:
> Aaron Trevena wrote:
>> If it's not a app dev or app support role I wouldn't expect somebody
>> to talk through troubleshooting an app aside from some basic ballpark
>> stuff, but I would expect a sysadmin to be able to help isolate the
>> problem so that the right team are (re-)assigned the trouble ticket.
>>
> And I did isolate it, it was the problem with a table on a database, it was
> running
> slow because it was very big. I however isolated it using commands I knew
> would
> be available on any Unix system, as i could not make assumptions about any
> monitoring
> tools available.

Cool, sounds reasonable to me.

Out of curiosity, was this a written question, or were you able to ask
what monitoring tools they were using?

When I've used this kind of question in interviews it's very
interactive - you don't just sit back and let the candidate give a
single answer (unless they're particularly good and can just run
through the answers without any need for you to question further or
add more context beyond the occasional acknowledgement or
confirmation)

I'm not sure I'd ever expect a sysadmin to be able to troubleshoot
queries or database design beyond suggestions of making it scalable in
the same way as any other resource (replication, etc)

> That was not my question, I know what might be the problem, what I want to
> know is what "modern/better" fault finding techniques people use.

Me too.

> What makes you think I don't? Just trying to find out what other people
> would do,  to improve myself.

Sorry, was responding to the other James's reply and removed too much
quote/context.

A.


-- 
Aaron J Trevena, BSc Hons
http://www.aarontrevena.co.uk
LAMP System Integration, Development and Consulting
--
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug