Devices - Traverse monitors the performance of your network, application systems, and their underlying components. These systems and components, referred to as "devices", can be routers, switches, servers, databases, networks, or applications.
Tests - Tests monitor and measure the performance and health of devices. The Test Status (displayed on the Device Details page) displays the current status for a test (for example, "OK", "Warning", or "Critical"). The Device Status (displayed on the Status Summary page) is the worst current test status for a device.
Thresholds - Traverse uses boundaries called thresholds to determine a test's status. A threshold is the outer limit of acceptable performance on a variable such as utilization, and packet loss. An event occurs whenever a test result crosses a threshold. These events form the basis for reporting through Traverse logs and graphs.
Status/State/Severity - These terms are used interchangebly to indicate the current status of a test, device or container. Typical states include OK, WARNING, and CRITICAL. The status of a lower-level object, such as test can set the status of higher level object, such as a device or container. Status display changes and notifications are based on transitions between states.
Events - Events automatically trigger actions. You can configure actions to execute as soon as a single event occurs, or after the same event occurs repeatedly. For example, you can configure Traverse to send an email notification to a Traverse user whenever a test crosses the warning threshold, or after a test crosses the warning threshold five consecutive times. Certain action types are included in Traverse, such as email, pager, and external scripts. Also, the plugin framework allows you to add new types of actions as required. See the Traverse Developer Guide & API Reference for more information.
Service Containers - A service container provides a user-selected view of containers, devices or tests. Service containers are nested. The status of each container in each level in the hierarchy is determined by the containers, devices or tests they contain. Service containers enable users to construct a logical, business-oriented view of a service being delivered to customers.
Monitor Types - A monitor type is a process used to run tests. Typically a monitor type is associated with a unique management protocol, such as SNMP or WMI. Each test type/subtype is identified by the monitor type used to run the test.
Departments - Each device, test and action must belong to a department. End users can only view and access devices, tests and actions in their own department. You typically create a department for each organization you deliver services to. You may find it convenient to create multiple departments for larger organizations.
End Users - End users can only view devices and other types of data for a single department. End users have either read-only or read-write permission to create and modify devices, tests, or actions within their own department.
Administrator - An administrator is a special type of user with the ability to create and modify departments and the devices, tests, and actions owned by those departments. The administrator can also configure default test thresholds, and establish service level permissions and limits for departments.
User-Classes and Admin-Classes - Users are associated with user-classes. Similarly, all administrative users are associated with admin-classes. The superuser creates permissions associating the admin-class with one or more user-classes. These permissions define the relationship between the admin-class and the user-class.
