Incidents

All errors detected during uptime, SSL, and domain checks are collected in this area and presented to the user through a single panel.

This allows all issues in the system to be:

• tracked from one place
• filtered
• analyzed
• documented by adding notes

Incident Creation

When WebPixie detects a problem during checks, it automatically creates an incident.

Example situations:

• website is inaccessible
• HTTP status code returns an error (e.g., 500)
• SSL certificate is about to expire
• domain expiration is approaching

When a problem occurs, the incident:

👉 starts as Ongoing

When the problem is resolved:

👉 it automatically transitions to Resolved

This process is fully managed by the system and does not require manual intervention.

Incidents Page

The Incidents page is the main screen where all incidents are listed.

From this screen, you can:

• list all incidents
• filter them
• review their details
• add notes or descriptions

Filtering

The Incidents page offers various filters to make analyzing incidents easier:

• Status filter: All / Resolved / Ongoing
• Category filter: Domain / SSL / Uptime
• Type filter: Status Code, Timeout, SSL Expiration, Request, etc.
• Severity filter: Critical, High, Medium, Low, Info
• Site filter: Used to view incidents for a specific site

These filters help users quickly perform meaningful analysis within large datasets.

Incident List

Each incident is displayed as a row in the list and includes the following information:

• Status: Indicates whether the incident is active (ongoing) or resolved
• Site: The website associated with the incident
• Details: Shows the type and reason for the incident (e.g., Status Code 500, Timeout, SSL Expiration)
• Incident Start: The start time and duration of the incident
• Retry Count: Shows how many times the problem has recurred
• Description: A note field that can be added by the user

Incident Types

Incidents can be generated from different types of checks.

Example incident types:

• Status Code
• Timeout
• SSL Expiration
• Domain Expiration
• Connection
• Keyword Match
• Too many redirects
• Unexpected

This structure allows WebPixie to consolidate various problem types within a single system.

Incident Severity Levels

Each incident is classified by its level of importance:

• Critical → Critical issue, requires immediate action
• High → High-priority problem
• Medium → Moderate impact
• Low → Low priority
• Info → Informational only

This classification makes it easier for teams to prioritize their response.

Incident Descriptions

A description can be added and updated for each incident.

This field allows you to:

• document the cause of the problem
• note the actions taken
• facilitate team communication

It plays an important role, especially when analyzing past incidents.