Skip to main content

Incidents and Maintenance

StatiBeat is built to make status communication easier for your team and clearer for your customers.

Incident administration​

The admin UI for incidents currently includes:

  • create incident
  • edit incident
  • add update
  • resolve incident
  • delete incident
  • edit component impacts
  • filter ongoing versus resolved incidents

These flows are implemented in application/frontend/src/pages/admin/IncidentManagement.jsx.

During incidents​

Focus on clarity first:

  • identify affected services
  • publish a short initial update quickly
  • keep follow-up messages consistent
  • close with a clear resolution message

Customers do not need every internal detail. They do need confidence that you understand the problem and are actively responding.

Maintenance administration​

The maintenance UI currently supports:

  • creating and editing maintenance windows
  • selecting affected items
  • scheduling date/time ranges
  • using preset messages
  • auto-transition messages for maintenance start and completion
  • deleting maintenance windows
  • marking maintenance complete

These flows are implemented in application/frontend/src/pages/admin/MaintenanceManagement.jsx.

During planned maintenance​

Maintenance updates should make timing and impact easy to understand:

  • what is changing
  • when it starts
  • who might be affected
  • when users should expect things to be normal again

Why this matters​

When communication fails, customers often assume the worst. StatiBeat helps you show what is happening visually so trust does not erode faster than the incident itself.