30.07.2012 Views

Reference Guide

Reference Guide

Reference Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Zend Server <strong>Reference</strong> Manual<br />

Workflow - The trace displayed in the Zend Server web console functions like a DVD player, showing the<br />

recorded execution history of the application. Users can follow the footsteps of a single problematic<br />

request in order to quickly pinpoint the root cause of the problem.<br />

202<br />

1. Manual Workflow - The code tracing of a single request can be generated manually through the<br />

code tracing page in Zend Server (Monitor | Code Tracing) (Figure 1). By executing a request, the<br />

full application execution is captured and stored in a trace file. The captured trace data can<br />

undergo collaborative reviewed leaving no need for developers and test engineers to pore over<br />

the symptoms of the defect and no room for misinterpretation of the events leading up to the<br />

error.<br />

2. Event Monitoring Workflow - Code tracing in Zend Server has very low performance overhead.<br />

This therefore enables its use either while running a load test in the lab or while running in<br />

production.<br />

By leveraging the Zend Server event monitoring mechanism, code tracing can save trace data only when<br />

a problem occurs. For example, when the performance of a checkout process in a web application drops<br />

below a predefined threshold, Zend Server can send an alert and capture the entire execution of the<br />

poorly performing request. The combination of knowing that a problem has occurred, while recording the<br />

entire execution flow, allows for quick identification and correction even before other users may notice.<br />

Summary<br />

One of the most appealing characteristics of this application is that the performance and memory<br />

characteristics have been designed to be suitable for production environments and excellent in-depth<br />

trace of execution.<br />

Other advantages:<br />

In-depth root-cause analysis when event happens. Trace of “exact” request which had the failure<br />

(a view back in time)<br />

No need for risky reproduction<br />

Insight into additional PHP subsystems beyond the script itself such as Web Server interface<br />

Technology suitable for development, testing, staging and production

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!