Incidents

An incident is opened whenever a region sees a failure, and it follows the steps in How Mage Watcher decides a site is down.

The Incidents list

Incidents lists every incident, newest first, 25 to a page. Each row shows the monitor, its group, when the incident started, how many comments it has, and its state.

False alarms are hidden by default. A line says how many are hidden and explains that a false alarm is a failure seen from one region that the other regions did not confirm. Show false alarms brings them into the list; Hide false alarms removes them again.

The incident page

• Header. The group and monitor, and the incident's state.
• Started, Confirmed, Resolved and Duration. Times are in UTC.
• Help desk ticket. When a GVenta Help Desk ticket was opened for the outage, its number links to your help desk, marked open or resolved.
• Timeline. Every step, in order, with the time and a short explanation: the first failure, each region's verification result, confirmation, notifications, recovery and resolution.
• Notifications. For a confirmed incident, every alert sent about it: the type, the channel it went to, and whether it was Sent, Failed, Skipped or Waiting, with the reason where there is one. If nobody was emailed, the page says so and links to your notification rules.
• Comments. See Comments on incidents.
• Visual evidence. Web images captured around the incident, with their reason, region and time.

A false alarm's page carries a note explaining that one region saw a failure, the others did not, no alert was sent, and it does not count against your uptime.

Removing false alarms

False alarms were never outages, so you can tidy them away:

• Remove false alarm on a false alarm's page removes that one.
• Remove all false alarms on the Incidents page removes every false alarm, or only those for one monitor when the list is filtered to it.

Both ask you to confirm. Removed false alarms no longer appear anywhere, and your uptime and reports are unaffected. A real outage cannot be removed: it is part of your uptime history.