StatusPal
StatusPal.ioBlog
Documentation
Documentation
  • Introduction
  • Get Started
    • Key concepts
    • Step 1 - Configure services
    • Step 2 - Add your team
    • Step 3 - Personalize design
    • Step 4 - Enable notifications
    • Step 5 - Report an incident
  • Next Steps
  • FAQ
  • 1-Click Import
    • Atlassian Statuspage Importer
    • Status.io Importer (beta)
  • Platform
    • Services/components
      • Dependencies
    • Subscriptions & Notifications
      • Subscriptions
      • Notifications
      • Auto-maintenance notifications
      • Subscription Groups
      • Import email subscribers
      • Auto-subscribe to private status page
      • Custom email templates
        • Template examples
    • Incidents & Maintenance
      • Reporting an Incident
      • The Uptime Calendar Page
      • Custom Incident Types
      • Exporting your incidents
    • Information Notices
    • Private Status Page
      • Adding people to your status page
      • Access Groups/Audience Specific
    • Team Members
    • Status Page Settings & Design
      • Custom Domain
      • Advanced Settings
      • Design Customization
        • Design recipes
    • Multi-Language
    • Status Badge & Banner Widget
    • Integrations
      • Terraform
      • Datadog Metrics
      • Zoom Notifications
      • Google Analytics
      • Google Calendar
      • SendGrid Email Notifications
      • PagerDuty + Statuspal status page
      • Configure SSO for your status page with Okta
      • Configure SSO for your status page with Auth0
      • Configure your Mailgun Integration
      • Configure SMS Notifications (Twilio Integration)
      • Zabbix
      • Pingdom
      • Checkly
      • New Relic
      • Datadog
      • BetterUptime
  • Monitoring & automation
    • Out-of-the-box monitoring
    • Incident automation
    • Recurring maintenance
  • Security
    • Single Sign-On
      • Save your Recovery Codes
      • Configure Role provisioning from SAML attributes
      • Configure role provisioning for Okta
    • API Keys
Powered by GitBook
On this page
  1. Platform
  2. Incidents & Maintenance

Reporting an Incident

Easily manage and document incidents by providing details such as affected services, timelines, and updates, using a streamlined and user-friendly interface.

PreviousIncidents & MaintenanceNextThe Uptime Calendar Page

Last updated 3 months ago

As mentioned earlier, there are . This is how to do it via the StatusPal Admin UI.

Understanding the fields for reporting an incident

  • Title: Add a short, descriptive title summarizing the incident.

  • Incident Type: Select the type of incident (e.g., Minor incident, Major incident) to indicate its severity and impact level.

  • Starts At / Ends At: Specify when the incident began and, if applicable, when it is expected to or has already ended.

  • Affected Services: Choose the impacted services from the list. You can select one or multiple services.

  • Private Notes: Include internal notes or sensitive details, such as troubleshooting steps or resolution context. These notes are only visible to team members with Admin UI access.

  • Initial Update: Provide an update for subscribers describing the nature of the incident.

  • Type: Define the type of issue.

  • Description: Add more context or detailed information about the incident. This field supports Markdown for formatting.

  • Tweet: Check this box to send an update via Twitter.

  • Notify Subscribers: Check this box to notify subscribers via email, SMS, or other configured channels.

many ways to report an incident