Is it a plane, is it a bird, is it a UFO?
Before you can delve into any kind of troubleshooting of an issue you need to thoroughly define it. If you don't you'll probably end up spending a lot of time randomly gathering and looking at data that is probably not even relevant to the issue at hand. More importantly, how do you even know that your problem is fixed if you don't have a good definition of the problem?
This might sound like common sense, but having worked with troubleshooting the better part of the last 10 years I can tell you that it is extremely common that people start looking at data before really understanding the problem. More often than not this is because people are stressed and want to fix the problem fast, or maybe because the problem space is unknown to them so they have difficulties defining what information or details are important. Sometimes symptoms are even contradictory which makes it even more difficult to troublesho ...
Go to the complete details ...