Zend Monitor

The Zend Monitor component is integrated into the runtime environment and serves as an alerting and collection mechanism for early detection of PHP script problems.

The Zend Monitor is a Zend Server for IBM i component that integrates into the PHP runtime environment and watches for various events Events are a result of the monitoring component checking your system and collecting information about a specific occurrence that indicates that your environment is displaying uncharacteristic behavior. such as errors, failing functions, slow scripts, database errors, etc. When an event occurs, the Zend Monitor collects and reports all the relevant debugging information. This information can then be used to perform root cause analysis.

What is an Event?

Events are governed by rules created in Rule Management | Monitor. Rules define the nature of an event and the parameters for capturing event related information in an application. Events are only created when the monitor component is running (Server Setup | Components).

By definition, an event is a collection of information that can be used to investigate what caused the rule to trigger an event. The information collected varies according to the rule type.

Aggregation

If events are triggered by the same rule and have similar characteristics – i.e., filename, URL, line etc – they are aggregated into a single issue. If they do not have similar characteristics, a separate (new) issue is created.

Inside a single issue, events are divided into groups according to when they occurred. A new group is created only if there is no activity for at least five minutes. If a new event occurs after five minutes pass, a new group is added to the issue. The new group includes all the events that occurred, as long as five minutes without activity has passed.

Changing Statuses

This section describes what happens to issues when they are created and what happens when a new event must be added to an issue after the issue's status has changed.

• New events are created with the New status.
• If an event is closed and a new issue occurs, the event is changed to the Reopened status.
• If an event is ignored and a new issue occurs, the event does not change its status. However, the system continues to collect information for the event.