ZenOSS Sample Clauses

ZenOSS. ‌ Infrastructure monitoring in each island is supported by ZenOSS7. ZenOSS is a tool capable of managing a set of IT resources of an organization. It monitors the network, servers (physical or virtual), power consumption, and even applications. ZenOSS is organized in 4 layers as shown in Figure 8-3. Figure 8-3 – ZenOSS Functional Structure The user layer is a web portal that gives access to the managed devices, to the dashboard, generated events, user’s management, and to reports. This layer interacts with the data layer that is responsible for information visualization. The data layer stores the information in three different databases: ZenModel and ZenEvents stores devices, monitoring, and events information in a MySQL database. ZenRRD stores measurement data in a Round Xxxxx database (RRD). Each collector owns its specific measurement object, as an example, the CPU measurement generates its own RRDs archives. The process layer has the responsibility to intermediate the communication between the data and collect layer. This communication occurs through remote procedure calls (RPCs) between the diversity of services that run to support all ZenOSS functionalities. The Collect layer is responsible to manage the services that collect and feeds the data layer. Data Collection process can be done through a variety of protocols, such as: SNMP, ICMP, SSH, and WMI (for specific Windows process). This layer has a variety of plug-ins that “translates” the raw data to “understandable” data to the data layer. ZenOSS monitoring process model follows the workflow presented in Figure 8-4. Figure 8-4 – ZenOSS Monitoring Process Workflow The first step is to discover the resources/devices over the network, either manually or automatically. It is followed by the definition of the configuration model, through a range of available templates or using extensions called ZenPacks. Once it is applied, the monitoring starts. If it is necessary to make adjustments, they should be done in the configuration step to make it reflect in monitoring. ZenOSS has a concept of class devices that is an organizer of used metrics, by default, accordingly to the device classification. For example, for a Linux server, it has a specific class with a variety of items that are common monitored in Linux servers. Naturally, this class of devices can be adjusted regarding the objective of monitoring. This process is done at the configuration step, just after the resource Discovery, as it can be seen in...