Product Architecture

The Zenoss technical architecture breaks down into 3 layers as illustrated below.

Zenoss Architecture Highlights

• Integrated Package - complete monitoring solution in an integrated software package with consistent design and code base
• Configuration Model (CMDB) - detailed, object-based data representation of IT environment including relationships between components and layers
• Class-based Configuration - manage configuration settings at the class (i.e. template), sub-class or instance-level with support for inheritance
• Hierarchical Navigation - file system metaphor for navigation of IT model and configuration
• Logical and Physical Groupings - group resources into arbitrarily complex groupings based on location, responsibility, business systems, etc., manage settings and view reports at group, sub-group or node level
• Agnostic Collection - support for various collection protocols, works with existing agents or agentless
• Scalable Collection - asynchronous, multi-threaded, distributable collection services
• Tiered Customization - substantial functionality "out of the box", various levels of customization depending on needs and expertise including GUI configuration, skins, plug-ins, interfaces and core programming.
• Extensive Automation - automation of routine tasks, including maintenance of an up-to-date model of your IT environment and automotic monitoring templates
• Modern Web App Architecture - leverage of Zope to provide a productive, secure and mature web application and publishing framework
• Python Programming Language - makes the core code easy to read, understand and extend. Experience the joy of programming in python. Plugins and extensions can be written in the language of your choice.

Zenoss User Layer

The user layer consists of a browser-based GUI that has been tested to run in Firefox and Internet Explorer. The front end is written in the Zope web application framework using Zope page templates. AJAX techniques are used to provide to enhance navigation and usability.

Zenoss Data Layer

Zenoss data layer provides a unified data store of configuration, availability, performance and event information.

Zenoss Configuration Database (CMDB)

• Unified object model of IT environment and management settings
• Stored in the Zope Object Database (ZODB)

ZenRRD

• Used to store time series history information and generate trend graphs
• Automatic data reduction
• Persistence using RRDtool

ZenEvents

• Database of active events and event history
• Persistence using MySQL

Zenoss Process Layer (Collection Tier)

The process layer of Zenoss Core includes a series of long-running collection and control services (Linux daemons). These processes provide many services including: node discovery, configuration modeling, availability monitoring, performance monitoring, event collection, and automated response.

While each of the services performs a different function, they have similar modes of operation. Each service:

• Interacts with Zenoss Configuration Database for model and configuration information
• Can run as a single local instance or distributed to improve scalability and availability
• Has its own command-line init script or can be managed by the global "zenoss" init script
• Can be run in daemon/service mode or from the command-line for debugging