Viewing Event Details

Event details are only accessible for licensed software.  AVIcode Version 5.7 RTM products ship with a license file that can be located under [drive]\Program Files\AVIcode\Intercept\SEViewer\Licenses. For new installations, this license is automatically imported during the installation process. For upgrades from 5.6 or lower, please follow the upgrade and license installation instructions.

Information about how to configure what data to collect and how much data to collect may be found in the Your Monitored System and Advanced Configuration sections of this manual.

Accessing Event Details

By default, a single mouse-click on any event in the View Pane will open the event details in a new window. Be sure that any popup-blocking software is disabled.

What's in the Event Dialog

When you click on any event in the View Pane of the main SE-Viewer window, a new window will open that has all of the details about that event, and information about other events that it is related to. Each event detail window has common characteristics:

Title Bar: The title bar indicates whether the details are for an Exception, Performance or Event Log event, and displays the unique ID for that event

Event Properties Tab: The 'Event Properties' tab provides property information about the event such as what computer the event occurred on, the Event Date, etc. The Properties tab also displays event data that allows you to drill down the call stack, and view such detailed information as parameters and member variables.

Similar Events Tab: This tab displays the currently selected event along with other events which are similar to it by Problem (), Action (), Exception Class () and Failed Function or Heaviest Resource () as applicable.

Related Events Tab: This tab displays the currently selected event along with other events that may be related to it based on time. Time based correlation helps to establish cause and effect relationships by grouping Operational, Performance, System and Application events that occur over a defined period.

Distributed Chains Tab: The Distributed Chains Tab provides a graphical display of all applications, and their related Web Service and .NET Remoting calls, associated with a client-side business transaction.

Performance Counters Tab: The Performance Counters Tab provides a graphical display of Troubleshooting performance counters. Troubleshooting performance counters are collected continuously within a 15 minute window. When a .NET exception or performance event occurs, all performance counter data from the 15 minute window leading up to the event are captured and stored. To enable troubleshooting performance counters and to set the collection duration:

Each tab in the event dialog is divided into two (2) areas. The top of the window provides information about the data being displayed, or controls for selecting what data will be viewed. This will be described in more detail for each tab.

What Can I Do with Event Information?

Each event dialog comes with an 'Action' menu and a 'Tools' menu  that allow you to send information to other people, export events to be imported into another SE-Viewer,  manage licenses and manage PDB files.

Copy an event link

The 'Copy Link' button copies the link to the event or group (depending on the current view in the event detail window) to the clipboard for pasting into other applications like email or instant messaging tools.

Email events

This option opens the 'Send Wizard', which lets you manually send events to a mail recipient, and adjust event information before sending it. The wizard opens an email with the event description in the subject line. The body of the message contains: A link to the event or group (depending on the current view), UTC Event Date, Event Source, Machine Name, Event Class and description. To use this wizard:

Export Events

The 'Save as...' option allows you to export events to a '.mht' file that can be imported into any SE-Viewer of the same version through SE-Viewer's 'Import' option. If you have a question about a particular event, AVIcode Technical Support may ask you to export it and send it to them.

Export to MHTML

Manage Licenses

Once you have your Intercept Studio installed and running, you will need to add your license file. While you will be able to see events in the View Pane of SE-Viewer without a license, you will not be able to access the event details.

See the "Licenses" chapter in this manual for instructions to use the License Management Wizard.

Manage PDB Files

In order to allow SE-Viewer to display file names and line numbers, you must have your PDB files. This wizard will aid you in uploading, deleting, and browsing PDB files.

See the "PDB Management" chapter in this manual for instructions to use the PDB Management Wizard.

Symbol Key

The following symbols represent the tree navigation and event data structures in event details:

 The plus symbol allows you to expand structures such as classes, functions, arrays, and objects to view information that is more detailed. For Event Log events the plus symbol allows you to expand the Description and Data areas.

 The minus symbol allows you to collapse the information displayed under structures such as classes, functions, arrays, and objects. For Event Log events the minus symbol allows you to collapse the Description and Data areas.

 The down arrows symbol allows you to show details related to parameters and member variables.

 The up arrows symbol hides details related to parameters and member variables.

The 'Expand all' symbol allows you to open the data in the stack area completely. It is the equivalent of clicking on all of the

symbols in the stack area.

 This symbol indicates that runtime information (parameters, member variables) are available.

 This symbol indicates that the PDB files are accessible and that source code access is available.

 This symbol represents a class.

 This symbol represents a class that refers to another class or entity that is already open and appears before it in the tree.  This symbol indicates that you will not be able to drill down any further, since it will cause a circular reference.

 This symbol represents a function.

 This symbol represents the first (from the top of the stack) user function, the red function in the exception event (Exception Events)

 This symbol represents a resource node in the  'Resource group view'

 This symbol represents an array.

This symbol represents an object.

This symbol links to details about the next connected event node in the execution (performance)

This symbol links to details about the event node that preceded this one in the chain (performance)

This symbol links to details about the event node that will receive this exception as a result of the call. (exceptions)

This symbol links to details about the event node that an exception was received from (exceptions)

This symbol identifies the Target, or subject, of an operation. For example, if the operation attempts to open a registry key, then the target is the registry key being opened. If it is a SQL query, then SQL is the target. For file I/O operations, the filename is the target. (exceptions)

Security Context - The Security context provides the connection string (for database connections) and the user that the ASP.NET process is running under for Security and Connectivity errors in the Aspect area.  (exceptions)

Actions - Actions are the actual methods executed as the result of a user requested action such as File.Open or the text of a SQL query that results in a Security or Connectivity failure. (exceptions)

This symbol identifies assembly and code information related to an event (exceptions)

This symbol links to the Microsoft Developer Network (MSDN) to quickly get information about syntax and usage for the specific methods, parameters, etc. that appear in your events (exceptions)

Special Elements

SEViewer displays special elements when data has not been collected. The table below provides additional details for some of these elements:

 

Value Description
No member variables are collected due to the detail level setting.  
The object has no member variables.  
The object members can not be retrieved.  
Remoting members are not collected. Transparent proxies are not collected (see MSDN System.Runtime.Remoting.RemotingServices. IsTransparentProxy). For example, sometimes the ‘this’ object in Remoting calls is a transparent proxy. In that call the ‘this’ object would not be collected.
Could not retrieve member because of NullReferenceException 'Member' refers to a variable (for example, parameter ) or member variable. This usually occurs when the object was disposed by the Garbage Collector .
Cycle reference (one level up). An object may have a special member variable that is reference to itself:

Class MyClass

{

Private MyClass _cycleReference = this;

}

This is a 1 level cycle reference. This type of  cycle reference could be within a member variable of a member variable of the current object (which would make it a 2 level cycle reference).
Cycle reference (2 levels up).  
Cycle reference (3 levels up).  
Cycle reference (4 levels up).  
Cycle reference (5 levels up).  
Empty Collection  
Cycle was detected This message is due to an error in the monitor. For parameters data collection, the monitor saves all collected objects to a hash table. This error occurs when the monitor detects a cycle in this collection. In the collected data this means that this object has already been collected and the user can locate it somewhere the data collected for this function.
Other object members are not collected due to class limit settings  
Other object members are not collected due to root limit settings  
Other object members are not collected due to function limit settings  
All collection elements are not collected due to the detail level.  
Collection was changed. Other elements are not collected.  
All class members are not collected due to the detail level.  

How do I control how much data I collect?

Data collection is controlled via the configuration file. The files can be most easily modified via the Intercept MMC, but the files can also be modified manually and redeployed out to your monitored servers. Please refer to both the Your Monitored System and the Advanced Configuration sections of this manual for more information.

 

Last update: Friday, December 03, 2010 01:05:31 PM