|
|
|
|
|
|
Event triggers can be customized to suit your working environment. Zend Platform comes ready with default configurations. However, a person with an understanding of the environment’s settings and performance standards should construct the Event Triggers to suit each unique environment. Event Triggers define the conditions under which an event, will be captured by the monitoring system (PHP Intelligence).
Users are prompted to select a node before entering the Event configuration screen as all configurations are made to a selected node. The top bars of screens display the name of the node, no name means the user is working directly on the Central Server.
The possible actions on this screen are:
Configure Event Triggers for a specific server.
View Event Triggers currently defined for the node.
Filter the view of events displayed in the “Define Event Triggers” table.
Clone Events
To configure Event Triggers:
Click “Event Triggers” in the “Configuration and Management Tools” list of shortcuts. The Select Server to Configure screen opens.
Select a server from the “Server Tree.”
Note:
To configure multiple servers or a server group with the same Event Triggers: (1) configure a selected server and (2) then use the Quick Clone button to propagate settings from that server to other server nodes.
Click Select to open the “Event Triggers” screen for the selected server.
Note:
Event Types are the specific events configured by administrators for monitoring a server/node. The Define Event Triggers procedure is used to define the conditions under which a server will generate an Event of a specific severity when an event (of the type) occurs. The Event Types supported in the current version of Zend Platform are described below.
Zend Platform is equipped with 12 types of Events for monitoring performance and script execution. The default Event Trigger display is a non-filtered view that shows all the available Alerts. A filter is provided to allow displaying a selection of events by type.
To filter events:
Press (Filter By) to expand the filter list.
Use the two drop-down fields to select the Events to display by:
Events From – The area where the event originated (script, database, web server, etc.)
Event Types – Filter view to display Events according to their Event Type (The selection changes according to the area chosen in the “Events From” field).
Press (Go) to filter the view.
The fields that make up the Define Event Triggers table can be understood as follows:
Event Type - The type of event that, under the rules defined, will produce an alert in the monitoring system.
Active- When enabled for a specific event, Zend Monitor (node) will report alerts when they occur.
Note:
This gives the user the right to disable an event for a particular server.
Rules - Defines the conditions under which an event will produce a report. For example, (Red) Script Runtime Exceeds 500 Seconds means that the system will generate a critical (red) event—for Slow Script Execution (Absolute) type events—if the condition (> 500 sec.) is met.
Note:
The user defines the thresholds for both the moderate and severe events. Some events have only one level of severity (like function error).
To define whether or not Zend Monitor will report a specific event, enable/disable the event in the Active column of the Define Event Triggers table.
To save the changes to Event Trigger definitions, click Save Rules.
The changes will then be updated in the database.
Each event type has its own advantages and characteristics. Press the link to view all the different Alert Types, their descriptions and recommended usage. Choosing and Defining Event Triggers
Note:
Events marked as “Performance Monitoring Events” have a special role in optimizing web application performance. This topic is addressed in the Zend Platform User Guide in Chapter 5, Implementing the Performance Lifecycle.
