Chapter 3 of 8
Alerts and incidents
Alert contacts are set up by the account owner; operators can see incidents too
Setting up an alert contact
- In More tools → Alert contacts, choose Add alert contact and select a delivery method.
- Fill in the details following the help for the chosen channel and save the alert contact.
- For email, complete the required verification. While an alert contact is waiting for verification, it receives neither alerts nor tests.
- Use Test and check delivery in the target inbox or app.
- In each website’s settings, select the recipients. An empty selection means all enabled alert contacts on the account.
When an outage alert arrives
A single failed check doesn’t necessarily become an incident. digiWatcher confirms an outage with repeated checks; you set on the website how many must fail in a row. If the digiWatcher provider has enabled additional monitoring locations, a majority of them must confirm the outage, always at least two. A result that no one else has confirmed stays unconfirmed; follow its explanation.
- Open Incidents or the details of the affected website. Read the time, cause, and current status.
- Check the site and contact whoever manages it or the hosting provider, depending on the cause found. digiWatcher tracks the outage; monitoring alone doesn’t fix it.
- Write a note on the resolution. Use a public note only for text meant for clients on the status page.
- After recovery, check the end of the incident and any follow-up alert.
Quiet hours and scheduled maintenance
The account owner sets quiet hours in Settings → Alerts and delivery. They postpone alerts; checks and event logging continue. You can allow an exception for important websites.
Before planned work, set up a window in More tools → Maintenance and choose the right websites and time. When it ends, check their actual status.