When an incident occurs, our tool provides a comprehensive set of details to help diagnose and resolve the issue. Here are the key components typically included in an incident report:
1. Root Cause:
The underlying issue that caused the incident. This could be a server crash, network failure, configuration error, or other specific driver of the problem.
2. Status:
The current state of the incident, such as "Resolved" or "Ongoing."
3. Duration:
The length of time the incident lasted, from detection to resolution.
4. Request:
The initial action or query sent by the monitoring system to check the availability, performance, or correctness of the service. This request aims to check the availability, performance, or correctness of the service. When something goes wrong, the response to this request will often include detailed error messages that help in diagnosing the issue.
5. Response:
In the context of an incident refers to the detailed feedback or error message that is generated when an incident occurs. This information is crucial for diagnosing and resolving the issue. For example, an incident response might include specific error messages, stack traces, or exception details that pinpoint the root cause of the problem.
6. Traceroute:
It is a network diagnostic tool used by UptimeRobot to trace the path that data packets take from the monitoring server to the target server. This can help identify where breakdowns or slowdowns are occurring along the route, providing valuable information for troubleshooting network-related incidents.
7. Activity Log:
A chronological record of actions taken during the incident, including updates, troubleshooting steps, and resolution efforts.
8. Comments (Available in TEAM and Enterprise Plans):
The ability for users to add comments to the incident report for further clarification or additional information. This feature provides room for further clarification or additional context concerning the incident. Importantly, comments related to ongoing incidents can be published on the status page. This enhances transparency and keeps your team and users informed about the status and details of the issue.