Support and Documentation

Introduction to Ops Desk

Many cloud technicians perform maintenance on servers or other network elements. Those elements issue messages of varying severity, from informational to critical. Depending on an event's severity, the technician needs to take corrective action.

Some premises use multiple systems to monitor their network elements. For example, a server may be running one interface that deploys Travis CI builds and another interface that detects server restarts or low disk space. All too often these systems are running independently, so a technician must monitor multiple sources of messages and prioritize the corresponding incidents. Ops Desk addresses multiple message sources by consolidating them into a single listing.

The following diagram illustrates a typical Ops Desk topology.

Typical Ops Desk topology
Figure 178. Typical Ops Desk topology

Referring to the previous diagram, a facility is running three servers, and each of them are running interfaces for PagerDuty, Travis CI, and local log monitoring. This topology results in nine messaging feeds—a number that explodes geometrically as the number of servers and daemons increases. Ops Desk consolidates all this incoming information into a single feed sorted by timestamp.

Ops Desk maps events into incidents that require attention. Administrators can configure the mapping so that incidents are automatically ranked by severity and assigned to the appropriate technician. The end result is the technician has one clean, prioritized listing of tasks.