3. Log investigation
If you have had problems of some infrastructural kind, be it networking problems, application mishaps or (let's hope not) had an intrusion of some kind you would be at this level. This implies that you know where your logs are being created, at which level they are logging, how to tweak log configuration settings, and actually know how to interpret what's in the logs to human understandable technical speech, and since there has been problems someone probably knows how to translate that techno-lingo to upper level language since management most likely have been reported to at some stage. What it boils down to is that you don't really care about your logs unless there is something worth to investigate, and only then you dive into your sea of logs and dredge for the line that eventually will lead you in the direction in finding out what really went wrong in the first place.
Comments
Post a Comment