StatusGator Support

Custom monitor and Incident overview

Open navigation

Custom monitor and Incident overview

StatusGator supports Custom Monitors, which are items displayed on your board and status page which you control the status of via incidents you create in StatusGator. 

Custom Monitors have many uses:

  • Internal status pages: Display the status of your network, wifi, or other systems and services that are not actively monitored by StatusGator.
  • Customer-facing, public status pages: Manually communicate the status of your software and systems with your customers or end-users. In most circumstances, you would not want automated monitoring alerts going to your customers. Instead, you use Custom Monitors and Incidents to communicate outages to your customers via your status page.
  • Integrate with a third-party monitoring tool to send status updates to StatusGator via the API. (Coming soon!)

Let's review some terms that will be helpful:

Subscriber An end-user that could be a team member, employee, or customer who has visited your status page and entered their email address in order to receive notifications of outages and incidents affecting the monitors on the status page.

You can manage your subscribers on the Status page under the Subscribers tab.

Incident - An outage or downgraded performance of some service/feature/site. You can create incidents affecting any of the Custom Monitors on your board. Use this to manually change the status and communicate outages to subscribers on your status page.

Incident Update - A timeline entry you create as part of the investigate or resolution of the incident. The first Incident Update is created automatically for you when you create the incident. For each incident update, you can decide whether or not to notify subscribers.

Phase - An attribute of your incident describing the current step in your process of resolving the incident. Each time you create an Incident Update you can choose a new phase for your incident or keep the phase the same. You can choose from the following phases:

  • Investigating - An issue has been discovered or reported and the incident is acknowledged. 
  • Identified - Cause of the issue identified and work to resolve is in progress.
  • Monitoring - monitoring of the incident to ensure the situation has stabilized. 
  • Resolved - Issue has been fixed, the service is up and running.

Severity - An attribute of your incident describing its impact on your infrastructure, customers, or other end-users Each time you create an Incident Update you can choose a new severity for your incident or keep the severity the same. You can choose from the following severities:

  • Major - The entire service or product is down, severely impacted, or is experiencing a widespread issue.
  • Minor - A slight degradation of the service performance or one feature is not functioning, but the main service components/features still work.
  • Maintenance - The service is under maintenance within a planned or pre-scheduled downtime.

Status -The current status of each monitor you choose to be included in your incident. Each time you create an Incident Update you can add additional monitors to your incident and change the status of monitors you have already added to your incident.

  • Up - No impact, service is back running and operational.
  • Down - Major impact or widespread unavailability.
  • Warn - Minor impact or isolated issue or degradation.
  • Maint - Maintenance as part of a planned outage.

If you have any questions or problems, please email us or submit a ticket.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.