Traverse is built on a powerful, fully-distributed architecture featuring three primary components, Data Gathering Engines (DGE), Business Visibility Engine (BVE) Object Store, and the BVE Web Application. Traverse has distributed collection capability AND a distributed database architecture, which allows the system to scale to extremely large environments with standard hardware.
1. Data Gathering Engines (DGEs)
DGEs are independent elements that locally collect, process, analyze, and store performance data from IT components. DGEs polls devices, receives SNMP traps, and process logs. They generate alarms based on threshold violations, and do the data aggregation in real time. Each DGE has its own distributed relational database. Traverse also includes DGE Extensions (DGEx) which enable capturing data from within closed / secure networks. The DGEx eliminates the need for inbound connections from the primary data aggregation point. They function as store-and-forward components that interact with an upstream DGE.
2. Business Visibility Engine (BVE) Object Store
The BVE Object Store is an intelligent configuration repository that keeps track of users, permissions, devices, connections, and the correlation between services and underlying infrastructure tests. The object store allows IT personnel to set up business services and containers. It also maintains application user permissions, definitions of what infrastructure elements are in which business container views, which data gathering elements monitor which infrastructure components, and at what frequency and with which specific queries/tests.
3. BVE Web Application
The BVE Web Application is a reporting and graph generation engine that consolidates system and application performance data to provide real-time status views, dashboards and historical/trend reports. The BVE Web Application is responsible for coordinating information collection from all the DGEs and presenting it to the user on-demand. The BVE is Web-based, and IT personnel can log on and view data through any conventional browser.
Overall System Operation
Each component of Traverse operates independently to provide a high level of scalability and fault tolerance. User, DGE and other configuration data is defined in the BVE Object Store. When a DGE is started, it searches the dge.xml file for its unique name, connects to the BVE Object Store, and downloads the entire configuration associated with that unique name, including tests, thresholds and actions.
After this process completes, the DGE performs tests, generates events when thresholds are crossed, and triggers the corresponding notifications. The data collected by each DGE is stored in a local SQL database on the DGE itself. Any configuration change made in the BVE Object Store through the BVE API or the BVE Web Application is instantly transmitted to the appropriate DGE.
When a user logs into the BVE Web Application, the system searches the BVE configuration database for the list of devices that the user has permission to view. The web application then connects directly to the distributed DGEs and gets the real-time status of the services or devices. When the user needs a report, the Web application fetches the data using parallel queries from the distributed DGEs.
|The BVE Web Application then summarizes the multiple results into a consolidated view and presents it to the user. This unique interaction between the BVE and the multiple DGEs is highly efficient. Zyrion has three patents on this distributed processing capability.