Zend Server User Guide > Getting Started > Step 6: Troubleshoot your Application

Step 6: Troubleshoot your Application

So - you've deployed your app, set up your monitoring thresholds, and an event is triggered. Now what? Zend Server helps you quickly find where in your code the error occurred.

Note:

This step can only be performed if the Demo application was deployed in Step 3: Configure your PHP.

 

 

Instructions on how to complete a procedure

To troubleshoot your application:

  1. Open the Event Details page for the same PHP Error event from Step 5:
    1. In the Zend Server Ui, go to the Overview | Events page.
    2. In the Filters area, click Show Filters.
    3. In the Event Type category, select the PHP Error filter.
    4. From the list of filtered events, click event ID 9.

  1. The Backtrace tab displays the exact line in the code triggering the error (line 350 in the 'mtrig.php' file).
  2. To help you quickly diagnose the error and find the root cause, you can debug the event using the integration with Zend Studio.
    In the Zend Studio Diagnostics area at the bottom of the page, click .
    Zend Server initiates a debug session for the event URL in Zend Studio.

    Important:

    These action items are only available if Zend Studio is installed on your machine, and Zend Server is configured to communicate with it. For more information, see Integrating with Zend Studio.

  3. In the Zend Server UI, go the Overview | Code Tracing page.
    The Code Tracing page is displayed.

The Code Tracing page is central display and management area for all traced information triggered by a monitoring rule or manually.

  1. In the Code Tracing column, click the trace ID belonging to the demo application you installed in Step 4.
    The Code Tracing Details page is displayed.

  1. In the Tracing Tree tab, select the Highlight most time consuming path check-box.
    The path that took the most time to run is highlighted.

 

For more information on working with Code Tracing, see Working with Code Tracing.

 

Read Also

 

Code Tracing

   
  Monitoring    
  Events