The Incidents Page

The Incidents Page is the centralized log for viewing all service disruptions detected by your monitors and heartbeats. It provides the necessary context, history, and status updates needed to manage failures and communicate effectively with your users.

Overview and Structure

Each entry on the Incidents Page provides critical details about the disruption. Understanding these elements is key to quick diagnosis and root cause analysis.

Key Incident Details

• Status: The current state of the issue. Statuses include Ongoing (currently active), Unknown (status hasn't been confirmed), and Resolved (the issue has been fixed).
• Monitor/Heartbeat: The name of the resource (website, server, or script) that triggered the incident. This is a linked item that takes you directly to the specific monitor's configuration and performance data.
• Root Cause: The technical reason for the failure (e.g., HTTP 500 Error, Connection Timeout).
• Date and Time: The precise time the incident was first detected by Pulsetic.

Viewing and Managing Incidents

The Incidents Page includes powerful tools for navigating and managing your event history.

Step 1: Access the Incidents Page

1. Log in to your Pulsetic account.
2. On the left-hand navigation menu, click the Incidents link.

Step 2: Filtering and Sorting

To efficiently manage and review service disruptions, use the controls near the top of the list:

• Search: Use the Search bar to quickly find specific incidents by name or keyword.
• Filter (View options): Use the Show filter menu to isolate incident types:
  • Everything: Display all historical and ongoing incidents.
  • Ongoing: Display only active incidents that have not yet been resolved.
  • Resolved: Display only incidents that have been fixed and closed.
• Sort By: Use the Sort by menu to arrange the list chronologically:
  • Newest First: Displays the most recent incidents at the top (often the default view).
  • Oldest First: Displays the earliest incidents at the top.

Step 3: Reviewing Details

1. Locate the specific incident you need to investigate.
2. Review the Status and Root Cause for initial context.
3. Click the Monitor/Heartbeat name to be directed to the detailed performance page of the affected resource for immediate diagnosis.