If we look back at Chapter 1, Troubleshooting Best Practices, the first step in the troubleshooting process is to understand the problem statement. In this section, we are going to explore how the problem was reported and will try to collect any data that we can to find the root cause of the issue.
For this example, we were notified of the issue via a phone call. This is actually lucky as we have an end user on the phone and can ask questions to get more information from him/her.
Before asking the person reporting the issue for more information, let's first take a look at what was already answered. All of a sudden, our blog is showing an installation page and not our posts!
At first, you may feel that this problem statement is vague; this is because it is vague. However, there is still quite a bit of useful information in this single sentence. If we dissect the reported issue, we can gain a better understanding of the problem.
"Our blog is showing an installation page"
"All of...