7. Basic Concepts of Wanguard Console¶
Please read this chapter to understand the basic premises required to operate the user interface correctly. The next few chapters cover the software’s configuration, while the last chapters cover the reporting features.
7.1. User Interface Structure¶
To understand how to operate the Console web interface, you should be aware of how it’s structured:
7.1.1. Side Region¶
According to the user’s preference, it is located at the east and/or west edge of the browser’s window. If it is not visible, an administrator has been either collapsed it or hidden it. Clicking the border of regions expands or collapses them.
Side Region contains two sections – Reports and Configuration – that can be collapsed or expanded by clicking the title bars or by pressing Ctrl+R. Both sections contain multiple panels that can also collapse or expand, with such state being maintained between sessions. These panels are constantly updated; you can add objects to most of them by clicking the [+] button from their title bar.
7.1.2. Central Region¶
Each report, dashboard or tool you select in the Side Region opens a tab (page) in the Central Region. You can switch between (sub-) tabs with a mouse or with the keyboard shortcut (Alt+) Ctrl+ → and (Alt+)Ctrl+ ← . You can close all tabs except for the Landing Tab (initially set as the Configuration Wizard). To change the Landing Tab, edit your user profile in General Settings » User Management. Tabs can be rearranged with drag-and-drop.
7.1.3. South Region¶
South Region provides a quick way to view the Latest Events tab, a live traffic graph, or a list with active anomalies. It is located at the bottom of the browser’s window. By default, it is collapsed; to expand it, click the thin line near the lower edge or press Ctrl+E.
Events are short text messages that describe errors, warnings, or the change of an operational status. Every Wanguard software component generates events; these are centralized and logged in the Console database. On one side, the Latest Events tab displays the latest 50 events, while on the other side, it shows a list of components that can generate events and the number of events generated in the last 24 hours by each component. The number’s color indicates the maximum severity of the events:
● CRITICAL – Critical events are generated when significant software errors occur, such as a memory exhaustion situation● ERROR – Error events are usually caused by misconfigurations, communication errors between components, or even bugs. Sensors auto-recover from some errors by restarting themselves● WARNING – Warning events are generated when authentication errors occur, on I/O bottlenecks or when there are time synchronization issues● INFO – Informational events are generated when configurations are changed or when users log in● DEBUG – Debug events are generated only to help with troubleshooting or the development process
You can also list the events generated by each software component by going to Reports » Devices » [Component Name] » [Component Type] Event sub-tab. To search, sort, or filter event messages, click the small down arrow that appears when hovering over the Event column header. To see additional details about an event, click the [+] button from the first column.