Table of Contents
4 Áú»¢¶Ä²© overview
Architecture
Áú»¢¶Ä²© consists of several major software components, the responsibilities of which are outlined below.
Server
Áú»¢¶Ä²© server is the central component to which agents report availability and integrity information and statistics. The server is the central repository in which all configuration, statistical and operational data are stored.
Database storage
All configuration information as well as the data gathered by Áú»¢¶Ä²© is stored in a database.
Web interface
For an easy access to Áú»¢¶Ä²© from anywhere and from any platform, the web-based interface is provided. The interface is part of Áú»¢¶Ä²© server, and usually (but not necessarily) runs on the same physical machine as the one running the server.
Áú»¢¶Ä²© web interface must run on the same physical machine if SQLite is used.
Proxy
Áú»¢¶Ä²© proxy can collect performance and availability data on behalf of Áú»¢¶Ä²© server. A proxy is an optional part of Áú»¢¶Ä²© deployment; however, it may be very beneficial to distribute the load of a single Áú»¢¶Ä²© server.
Agent
Áú»¢¶Ä²© agents are deployed on monitoring targets to actively monitor local resources and applications and report the gathered data to Áú»¢¶Ä²© server.
Data flow
In addition it is important to take a step back and have a look at the overall data flow within Áú»¢¶Ä²©. In order to create an item that gathers data you must first create a host. Moving to the other end of the Áú»¢¶Ä²© spectrum you must first have an item to create a trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed by an action which sends you an email. While that may seem like a lot of steps, with the use of templating it really isn't. However, due to this design it is possible to create a very flexible setup.