Working with Events

The following procedures explain how to handle events.

See Editing Rules to learn how to define which events you want Zend Server to generate and under which conditions.

Zend Server event filtering reduces the number of events in the Events list on the Monitoring | Events page by displaying events according to your personal preferences, thus facilitating a more precise monitoring process.

Instructions on how to complete a procedure

To filter events:

  1. In the UI, go to Monitoring | Events.

  2. To filter the events list, select a filter from the Stored filter menu. By default, All is selected.
  3. To filter the jobs list by time range, click the Time range menu, and select a filter. To manually configure the time range, select Custom and click on the current date that appears next to the menu. You can enter the start and stop dates and time.
  4. To see the advanced filtering options and to create and save custom filters, click Advanced filter. You now have access to the advanced filtering options. For a complete list of your filtering options, see Event Filtering.
  1. To create and save a custom filter, select the filtering options from the various menus and click Save as. You are prompted to name the new filter and save it. Your custom filter now appears in the Stored filters menu.
  2. To delete a custom filter, select the filter from the Stored filters menu and click Delete.

To clear all selected filters, click Reset.

Tip:

The URL for this page uses URI fragment identifiers - pasting the URL in another tab/browser will load the page with current filters activated.

This procedure explains how to delete events from your server. You can either filter down, and delete, a specific selection of events, or manually select which events to delete.

Instructions on how to complete a procedure

To delete an event:

  1. In the UI, go to Monitoring | Events.

  2. Filter the events in the Events list.
  3. Delete all filtered events by clicking , and clicking OK when prompted.
    All filtered events are deleted from your server and the Events list.

Note:

Zend Server will remove all events on your server answering to the selected filters, even those that are not currently displayed in the Events List.

  1. Delete a selection of events by manually selecting events in the list, and clicking , and clicking OK when prompted.
    All selected events are deleted from your server and the Events list.

Issues contain different types of information and actions that allow you to detect the source and drill down to investigate what caused a problem. In some cases (and depending on the type of event that was triggered), the information also indicates the solution. For example, issue information includes the exact line of code that has a problem and the nature of the problem.

The following procedure describes how to view an event's details. Event Details are the actual context of the event. Use these event details to locate information for root cause analysis of the issue.

Instructions on how to complete a procedure

To view an event:

  1. In the UI, go to Monitoring | Events to display the Events list.

  2. Locate an event that interests you (The filter option can be used to decrease the number of events listed in the table, see Filtering Events above).

  3. Click on the Event ID link
    -OR-
    click on the Expand View arrow on the right side of the event line, to view an expanded view of the event, and click More Details.
    The Event Details page is displayed.

  4. Clicking on an Event Group changes the contents of tabbed display to show the details collected for that specific group of events.
  5. Clicking on the Event Details tabs changes the displayed details collected for that specific group of events.

See Events and Event Details for more information on viewing event details.

This procedure explains how to integrate with your IDE to quickly identify event root cause analysis. These actions can be applied to each event group to investigate what caused the event. By default, the settings are set to run diagnostic actions on the originating server (the server on which the event was created). You can change the settings to run on a different server.

Important:

These action items are only available if the IDE is installed on your machine, and Zend Server is configured to communicate with it.

Instructions on how to complete a procedure

To diagnose with your IDE:

  1. In the UI, go to Monitoring | Events.
  2. Hover over the relevant event, and click the menu button in the Actions column on the right.
  3. Select one of the following options:
    • Debug in IDE - Initiates a debug session for the event URL in your IDE.
    • Profile in IDE - Profiles the event URL, using your IDE Profiler with the same parameters (GET, POST, COOKIE, HTTP headers, etc.).
    • Show in IDE - Opens the file where the event occurred in your IDE. This option makes it possible to use your IDE to edit files and implement changes for multiple servers.
    • Export to IDE - Generates a .zsf file containing the selected event's information that can be imported into your IDE.

-OR-

  1. In the UI, go to Monitoring | Events.
  2. In the Events List, click an event ID.
    The Event Details page is displayed.
  3. In the IDE Diagnostics area, click an action button:
  • - Initiates a debug session for the event URL in your IDE
  • - Profiles the event URL, using your IDE Profiler with the same parameters (GET, POST, COOKIE, HTTP headers, etc.).
  • - Opens the file where the event occurred in your IDE. This option makes it possible to use your IDE to edit files and implement changes for multiple servers.
  • - Generates a .zsf file containing the selected event's information that can be imported into your IDE.
  • - Allows you to select the server upon which you would like to perform the IDE diagnostics. See Diagnosing Using an Alternative Server below for more details.

Note:

When you use these actions, make sure that you have Zend Studio on the remote machine, access to the remote server and that the remote server is an allowed host. For more details, see Error: Failed to Communicate with Zend Studio.