Zend Server 5 Code Tracing
Root Cause Analysis is a Time-Sink for DevelopersFixing a problem is easy when you know what causes it. However, finding the root cause of problems is often challenging during testing, and incredibly difficult when the application is running in production. Trying to reproduce the exact same environment, application state and load in the development lab is both time-consuming and error-prone, and it takes developers away from their most important task – writing code. Zend Server 5 takes root cause analysis to a whole new level by featuring code tracing. |
|
A Flight Recorder for Your PHP ApplicationWhat is code tracing? Think of a black box flight recorder. When something goes wrong with an airplane, you would probably not want to “reproduce” the problem. This is why the flight recorder captures the full data that flight analysts may need in order to understand why the problem occurred.Zend Server Code Tracing is like a flight recorder for PHP. Rather than spending time on trying to set up the environment and reproducing all the steps that led up to the failure, Zend Server captures the full execution of your application in real-time – in production or in the test lab – so you can quickly find root cause. |
Zend Server Code Tracing Cuts Root Cause Analysis TimeZend Server code tracing is activated automatically, when a problem is detected, or manually by the user, e.g. during an optimization project. Data recorded by Zend Server code tracing includes:
The trace displayed in the Zend Server web console enables you to view - much like a DVD – the execution history of your application and follow the footsteps of a single problematic request to quickly pinpoint root cause. ![]() Read the white paper: "Troubleshooting PHP Issues With Code Tracing" » Watch the Code Tracing with Zend Server 5 Webinar » Watch a video demonstration of Code Tracing in action » |
Zend Server 5 code trace tree
Zend Server 5 tracing statistics |



