Incidents are used to track issues such as network outages, security events, app slowdowns or anything else that may negatively affect your users. The incident process is simple: Create the incident Post incident updates Resolve the incident Let’s take a closer look at each step in the process. Creating an incident Creating an […]
The affected infrastructure can be modified for existing incidents. Click the edit icon next to Affected Infrastructure. 2. Add or remove any infrastructure. Notes: At least 1 component must be selected. The status level will not be changed automatically.
Historic incidents and maintenances can be imported manually via the Dashboard or automatically with the Developer API. Web Dashboard Access the backfill function in the dashboard from the Incidents or Maintenance tab. Developer API The API is especially useful for bulk importing historic events. Use the /incident/history/create and /maintenance/history/create methods to add historic events automatically. Learn […]
Create reusable templates to make status updates more efficient. Manage your templates from either the Incidents or Maintenance tab in the dashboard. Give your template a descriptive name. The name is only used internally to identify the template. Optionally, specify a title that will be used when creating a new incident or maintenance. The […]
Enhance an incident by adding a link to an external post-mortem. Since post-mortems are usually detailed reports that may contain media content or external resources, we recommend creating the post-mortem on your blog and then linking to it from the incident on your status page. Adding a post-mortem link to an incident Click the Add […]