Reference Guide

Zend Server Reference Manual
Advanced Tasks
Issues contain different types of information and actions that allow you to detect the source and drill down
to investigate what caused a problem. In some cases (and depending on the type of event that
happened), the information also indicates the solution. For example, issue information includes the exact
line of code that has a problem and the nature of the problem.
Basic Details
The first layer of issue details are the basic details. These details are used to identify an issue with highlevel
characteristics. Every issue includes the following basic details:
124
ID and Rule Name - The ID number is a unique identifier for a specific issue. The Rule Name
states the rule (defined in Rule Management | Monitoring) that triggered the event. The ID
number can be used to locate a specific issue using in Monitor |
Events. The Rule Name indicates the rule that triggered the event: Several issues can be
triggered by the same rule. Knowing the rule name makes it easy to find the rule if you want to
modify the rule settings (Rule Management | Monitoring | Edit).
Occurrence Info - An issue is a collection of aggregated events: This detail specifies how many
times this event occurred since the first time.
Status - The Status indicates the state of the issue. In some cases, the Status changes
automatically. The Status can be used to locate events in the Events page: Use a filter to display
the specific status.
Severity - Currently there are two severity levels, Critical and Warning. These levels reflect your
preferences, in terms of the importance of the event.
General Details
Each issue is an aggregation of one or more events with common, predefined characteristics. These
common characteristics are displayed in the General Details section. Therefore, you can assume that
each event that occurred for this issue has at least these details in common. This is the first step in
identifying the source of the event and understanding the circumstances surrounding the event.