Reference Guide

Zend Server Reference Manual
Working with Code Tracing
Code Tracing records execution activity in real-time. This provides an in-depth diagnostic tool that will
allow you to drill-down to the function level to view actual performance related information and statistics.
In order to work with Code Tracing you first have to have the Code Tracing component installed and
activated (see the Installation Guide for information on adding components and to see Working with
Components for information on the components in your system).
Setting a Monitor Rule to Run a Code Trace
This procedure describes how to define monitor rule settings to in addition to the event related information
also collect trace information when the event is generated.
128
To set a monitor rule to save trace data:
1. Go to Rule Management | Monitoring.
2. Select a rule from the list.
3. Click Edit to open the rule for editing.
4. Scroll down the page to "Step 2: Event Action"
5. Select the one of the options and click .
The Tracing options are:
Save Trace Data - Generate a trace file each time the event is triggered.
Activate Trace Data Collection for... -Generate a trace file for a given time frame each
time an event is triggered.
6. Scroll to the bottom (or the top) of the page and click Save to save changes.
The next time the event is triggered trace information for that specific occurrence will be collected. The
trace information can be viewed in Monitor | Code Tracing or directly from the event (see important note
below).
Important Note:
A single issue can contain aggregated information about more than one instance of an occurrence. This
information is also grouped according to when the event occurred. When Code Trace information is
collected it is collected for a specific time and therefore will be associated to a specific group inside the
event for more information see "Viewing Trace information Inside an Event".