Code Tracing in Zend Server can be run manually for a URL, or automatically for triggered events.
Important:
To work with Code Tracing you first have to have the Code Tracing component installed and activated. To verify, go to Configurations | Components.
 Video
Video
                                To better understand the procedures described in this topic, watch this video:
 Enabling/Disabling Code Tracing for Events
Enabling/Disabling Code Tracing for Events  
                                This procedure describes how to enable or disable Code Tracing for events.
| 
 | 
 | 
| 
                                                     | To enable/disable event-triggered code tracing: 
 
 
 | 
| Important! If enabled, you will also need to activate Code Tracing for the specific event rule from the New/Edit Event Rules page. For more information, see Activating Code Tracing for an Event Rule below, and Working with Event Rules. | |
 Manually 
 Triggering a URL Trace
Manually 
 Triggering a URL Trace
                                This procedure describes how to manually run a code tracing on a specific URL. Running a code trace on a specific URL will capture the current activity at the time the trace was triggered.
| 
 | 
 | 
| 
                                                     
 | To manually trigger code tracing on a specific URL: 
 | 
| The trace information will be collected and added to the list in the Code Tracing page. | |
 Running Code Tracing on Another Machine
Running Code Tracing on Another Machine
                                You can run Code Tracing on another machine as long as the Zend Code Trace component is installed and running on it. However, when running a trace on a remote machine the trace information is collected on that machine therefore, instead of running the trace from a remote machine always run a trace on the specific machine you need. If you do want to run a trace on a remote server after all, make sure that the server's IP is an allowed host in Debugging | Debugger.
 
                            
                         
                                                 .
.  .
.


