Reference Guide

Configuring for Production or Development
Zend Server Best Practices
In general, the best practice is the same: tune monitoring rules and thresholds to provide the information
you need, without creating an overflow of events that you are not able to handle. This means that in
development you may want focus on a specific rule type each time or set high thresholds and gradually
modify them. In production, it is preferred that you already come with an estimate of the thresholds that
are necessary.
The difference between development and production is that usually in development environments you
have to work very hard in order to have such an "overflow" - development environments are low traffic,
low load systems. Additionally, the performance impact is negligible in development environment. In
production, as a contrast, tuning is very important because of two reasons:
1. High traffic systems tend to generate hundreds and thousands of events per day if not properly
tuned - even with aggregation, this tends to be more than what a development team can handle.
2. The more events you have, and the broader your thresholds are (for example the more functions
you watch for Slow Function Execution events) the bigger the performance impact on your
system is going to be. While under normal circumstances this impact is usually negligible, under
high stress circumstances it could have an effect.
Given this, the best practice for tuning Zend Monitor thresholds is to start from relatively high thresholds,
and lower them over time as old issues are fixed and the capacity for handling fine-grained errors grows.
This is mostly true in production environments.
397