Open topic with navigation

You are currently viewing Zend Server 5.x documentation. Click here to view the latest Zend Server online documentation.

Rule Types

The eventsEvents 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. listed in Monitor | Events are based on rules defined in Rule Management | Monitoring, If a rule is enabled, it is displayed in the Events page when it is triggered. When more than one event with a high percentage of similarity is triggered, it is aggregated into a single report. These reports are called issues.

The following list displays the possible rule types that can generate issues in the Events page:

• Function Error - A Function Error rule provides specific information about the root cause of an error that may not be related to a PHP error. QA and production teams can use this event rule type to identify run-time events, as opposed to PHP errors, which identify code-related/syntactical events. Severity: Warning.
• Database Error -A Database Error rule provides specific information about the root cause of an error that may not be related to a PHP error. QA and production teams can use this event rule type to identify database connectivity and query events, as opposed to PHP errors, which identify code-related/syntactical events. Severity: Warning.
• Slow Function Execution - Slow Function Execution rules identify bottlenecks within functions, providing a more granular approach than finding bottlenecks in pages. This type of event rule is particularly useful in the production process, because it can pinpoint performance bottlenecks for user-specific functions, as well as the predefined list of functions that are considered prone to slow execution. Severity: Warning and Critical.
• Slow Query Execution - Slow Query Execution rules generate an event when database related function execution rises above the given threshold. Slow Query Execution events identify slow queries that are related to database performance that can directly influence Web server performance.
• Slow Request Execution - Slow Request Execution rules generate an event when script execution time exceeds defined limits. These event rules are used to maintain script runtime performance standards. The settings can be relative to a specified percentage or set to an absolute value. Severity: Warning and Critical.
• High Memory Usage - Memory Usage event rules identify when scripts use excess memory resources that can, in turn, reduce the application's performance. This type of rule is primarily used in production environments, but QA teams can also benefit from monitoring by kilobyte (KB) or by the percentage of memory used by a script to execute. The settings can be relative to a specified percentage or set to an absolute value. Severity: Warning and Critical.
• Inconsistent Output Size - Inconsistent Output Size event rules verify that pages render the same output to the client each time. If pages do not render the same output each time, this indicates that some clients may be seeing different output. This is an error situation. Production environments use these rules to indicate possible usability issues. Severity: Warning.
• Uncaught Java Exception - Java exception event rules increase the visibility of issues originating in the Java side, by indicating when uncaught Java exceptions occur in Java code invoked from PHP via the Java Bridge.
  This event identifies uncaught Java exceptions and provides Java-related backtrace information, including which part of the PHP code triggered the error. Severity: Critical.
• Custom Event - This unique event rule is used to initiate events from a PHP script. Custom events control event generation, in contrast to other events, which are triggered by specific occurrences. Custom events are used to generate an event whenever the API function monitor_custom_event() is called from the PHP script. Severity: Warning.
• PHP Error - PHP Error rules identify all types of PHP errors, including hard errors that cause stops in page execution, warnings that interrupt the end user experience, and notices that could lead to larger problems.
  This type of event rule is useful in QA processes, to identify problems that may have gone unnoticed during production. Production environments can benefit from using this PHP intelligence feature to alert administrators to application runtime errors  that could seriously impact the end user's experience. Severity: Warning and Critical.
• Job Execution Error - This event is generated when a job could not run.
• Job Logical Failure - This event is generated when a job reports a logical failure.
• Job Execution Delay - This event is generated when job execution is delayed by x seconds from the planned start time that was defined in the job. The delay time is defined in the Job queueA simple and manageable system for off-loading tasks from the synchronous user request, to an external, parallel PHP process. settings page: Server Setup | Job Queue.
• Job Queue High Concurrency Level - This event is generates when the job queue daemon is at or close to its maximal concurrent job limit.
• Tracer - Failed to Write Dump File - This event is generated when the Code Tracer could not create a dump file.
• Skew Time - when the job is executed later than scheduled

Important:

Caught Java exceptions are considered part of the normal exception flow, therefore only uncaught exceptions are reported.

Some rule types can be configured twice - once with absolute value settings and again with relative value settings.

An absolute setting is used to configure a specific value and a relative setting is used to configure a percentage of a selected value.

© 1999-2013 Zend Technologies, Ltd. All rights reserved.