Here you configure different aspects of events monitoring
Advanced Monitoring Settings (link on the right)
Clicking this link will lead you to the Zend Monitor directives on the Administration | Components page, for advanced configurations.
Events Aggregation
- Enable aggregation - This option allows unification of "similar" events, coming from the same URL / Route, in the events list.
- Disable aggregation - This option will separate each new event as a new instance, which will result in many event records on the same URLs / Routes. This mode is better for development, where full details of each event are needed in its own focus.
Code Tracing for Events
Periodic Cleanup Settings
- Delete events which did not occur in the last - This option configures the Monitoring Events cleanup mechanism within the Zend Server cleanup routine, basing old events cleanup on days count. Once an event has passed X days in the database, it will be permanently deleted by a periodic job, preserving disk space and DB storage. With more days to keep old events, you will get a larger storage consumption holding old events, but more time to go over old events if your admin routines are not frequent. With less days to keep old events, you will have smaller storage consumption, yet you will need to be "quicker" on your periodic checks. To make sure you do not miss out on critical events, you can always configure Event Rules with more actions, such as sending email to an admin address, or callback URL which can collect the data into other systems, such as SMS / Chat system or monitoring web service.
Triggered Actions Settings
- Monitoring rule default email address - Here you can set a default email address, or multiple email addresses separated by commas, to be selected when event rules are triggering an email action, in addition to raising an event in the system and storing in the database.
-
Monitoring rule default callback URL - Here you can set a default callback URL, to be called by Zend Server as an additional action by event rules which are defined to trigger a callback URL. Your endpoint URL script should parse the POST data from the callback information and perform further triggering / storing as your business needs / integrated systems require.
- Apply to existing monitor rules - This checkbox will re-visit existing event rules which are set to trigger Email or Callback actions, and replace the existing values with the above configuration. This can help to minimize your admin work if you already have some event rules with triggered actions defined.
General (tab)
