|
|
|
|
|
|
Event Details are generated in accordance to Event Triggers. Event Details are a diagnostic tool that provide a complete audit trail and options for investigating and resolving events.
Event Details are viewed in several ways. The regular way of viewing events is from Zend Platform. Events can be configured to be sent by e-mail recipients or to a URL (in XML format). However, Event Details always include the same information regardless of the viewed output (Regular Event Details, XML or e-mail).
Event Details include five sections:
The information included in Event Details varies according to event type. For example: PHP Error Event Details include different information than a Slow Script Execution Event Details, simply because these events require different information to perform diagnostic analysis.
The general information section of the Event Details provides basic information about the event (depending on the event’s type) as follows:
Title - The top of the Event Details, displays the event that generated the Error and the Event ID (Error #). The Event ID can later be used, to locate the event in the Event List or the Console in the filter's Find section.
Severity Level - An additional notification is added to severe events.
Event Status - The Status of the event is indicated for all statuses except Opened.
Requested URL - The requested URL
Main Filename - The URL’s main file
Source Info - The path to the Source File and line in the code that triggered the event.
Note:
Especially with code related errors, this information can provide an immediate indication to the source of the error in the code.
Trigger Value The script’s trigger value (runtime,output size,memory consumption etc.)
CPU Load - The CPU load when the event occurred.
Zend Error/ Error Description - Shows the event’s error text (for code related errors) and the $type of Custom Events
Aggregate Hint - Shows the Aggregate Hint for this event
Associate Zend Error - Event Adds a link to an associated Zend error event.
To prevent an event from being continually reported for the same or similar event, PHP Intelligence enforces Aggregation Rules. These rules are based on a set of predetermined algorithms that determine which events are identical or are similar, to the extent they can be reported as a single Event. Aggregation Rules are also aware of events that occur on nodes belonging to a cluster – Groups and not just occurrences on a single server (node).
Aggregation information is displayed in event details to identify the number of times the event occurred and in case of Groups the information is expanded to include the servers on which the event occurred and the number of occurrences.
The Event Occurrence Info section shows, the total number of occurrences, the time and date of the first and last occurrence and the first server (and vhost) on which the event occurred.
In cases where an event occurred on several servers belonging to the same group, an additional expandable list is added. This list displays occurrences per server, i.e. the server’s name, and total number of times the event occurred on the server.
The Zend Studio Diagnostics section shows the advanced diagnostic options that can be performed on the event’s data.
These diagnostic options reconstruct the precise conditions that generated the event by recreating the request with the same parameters that were in the original request (Information such as: GET/POST/COOKIE/etc.).
Note:
The recreation process will not create an additional event.
The diagnostic options that can be applied to event information are as follows:
Test URL - Loads the exact same URL from the event with the exact same parameters (GET/POST/COOKIE/HTTP HEADERS/etc.) and shows the script’s output in the browser.
Note:
The Test URL option does not require the Integration with Zend Studio.
Debug URL - Initiates a Debug session of this URL in the Zend Studio.
Profile URL - Profiles the URL, using the Zend Studio Profiler with the same parameters (GET/POST/COOKIE/HTTP HEADERS/etc).
Show Source Code - Opens the file where the event occurred in Zend Studio. This option provides a means for editing files and implementing changes to multiple servers using Zend Studio.
Important: Debug URL, Profile URL and Show Source Code can be activated when the following conditions are met:
Zend Debugger is installed on the server where the event occurred.
Zend Studio (ZDE) is open.
Zend Platform preferences are configured to the correct port, the Zend Studio IP is correct, and the Debugger allows a debug session from the Zend Platform GUI.
Event context includes relevant information available at the time of the occurrence. This information varies according to the type of event generated.
There are four main Event context categories: Function Data, Variables, Backtrace, Included Files.
Function Data is only added to function related Event Details. This addition shows the function’s name and parameters at the time the event occurred.
The function always appears as a link. This link directs to the function’s description in the online PHP manual at: http://www.zend.com/manual
The information included in the Variables section, includes all variables data saved when the event occurred, such as: GET, POST, COOKIE, SERVER, etc.
The GET, POST, COOKIE and SERVER sections will always be displayed even if they are empty. This indicates that there was no available data at the time the event occurred.
Users may choose to change the type of information collected and displayed in an event.
Backtrace only appears in function related events. The listed functions are the functions that lead to the actual function (occurrence) that triggered the error.
Functions are listed in chronological order from the most recent to the first function that was called.
There are two options for viewing Backtraced functions, in a pop-up screen or in Zend Studio.
The Included Files section only appears in slow script error events. The files listed are all the files that are included in the PHP script that caused the error to occur.
Shows event data in the Event details in the form of an expandable text field. This option opens the file in the section of code where the event occurred.
To view the source code in Event Details:
Press Show Source Code to expand the text area.
The Event Administration section includes all the actions that can be applied to an event see Controlling Information Displayed in an Event, to learn how to disable these options for certain users.
The applicable actions (Buttons) are as follows:
Preserve Event - Keeps the event in the database even during database cleanups.
Delete Event - Deletes the event (i.e., removes the event entirely from the database.)
Ignore Event - Ignores future instances of this event (i.e., changes the event status to ignore). Therefore, if the same event occurs again, Platform will not open a new event.
Close Event - Closes the event (i.e., changes the event status to closed). Therefore, if this event occurs again, Platform will open a new event.
Reopen Event -Changes the event’s status from closed to open.
