Checking systems…
Queue
Everything that needs someone, from every system
Checking systems…
·
Loading alerts…
Alert emails from our systems, grouped by problem and client. Repeats are merged, things that fix themselves close on their own, and only what still needs someone goes to Problems. What each kind of alert does: Admin settings > Alert sources.
Needs someone
Also under Problems, where you can say you're on it or make a ticket. Urgent ones send a phone alert.
Waiting to fix itself
Offline things get a few minutes to come back before they reach anyone.
Handled without anyone
Kept for the record. The morning digest lists what's good to know.
Emails per day
Every email that reached the alert address. A red mark is a day with an emergency.
By client
Worst first. Names in grey aren't linked to a client yet.
| Client | Emails | Problems | Emergencies | Open |
|---|
Noisiest devices
"Keeps dropping" means it went down and came back 3 or more times.
| Device | Emails | Problems | Note |
|---|
By kind of alert
Time to fix runs from the first email to "back" or Done.
| Source | Kind | Emails | Problems | Emergencies | Time to fix |
|---|
Senders
Every address writing to the alert address. "Not read yet" means a new system or layout to add.
| Sender | Emails | Read as |
|---|
Names to link
Client or device names the alerts used that aren't matched to a client. Open one and pick the client once; later alerts follow.
Checking backups…
| Client | Last 14 nights | Oldest good backup | Status | Who's on it |
|---|
One square per night: green = good, amber = finished with warnings, red = failed, dashed = no result came in, gray = nothing that night.
Checking locations…
Client locations where every network device is offline. Areas are approximate.
Locations down longest first
We couldn't tell where these are from the device or the client's site address. Type the ZIP code they're in (only the ZIP area is ever shown), or leave them off the map.
