Please note
that these terms are used across a variety of AVIcode products Please note
that these terms are used across a variety of AVIcode products
| .NET Remoting | .NET Remoting is an enabler for different applications to use to communicate with one another. The applications can be located on the same computer, different computers on the same network, or even computers across separate networks. |
| Action |  Action
based consolidation categorizes events based on entry points such
as page calls, button clicks, web service calls or some other
atomic action representing a particular business process. This
grouping is valuable for determining under what circumstances a
failure occurs. |
| Alerting Threshold | Alerting thresholds are used by the Operations Monitor to determine if an event needs to be reported. The monitor measures the execution time of an Entrypoint (a top-level function), and reports an event if the Alerting threshold is exceeded. If the threshold is not exceeded, then the operations monitor disposes of the data. Alerting thresholds are measured in milliseconds. |
| application | In the development environment, an application typically corresponds to a Visual Studio Project for ASP.NET, a Web Service, or a Windows Service. It's typically a standalone unit of deployment. |
| 'Applications' node | The 'Applications' node allows you to access and modify properties which apply to the monitoring system as a whole, such as choosing the desired storage type, testing connectivity to SE-Viewer, setting event throttling, etc. |
| Aspect | Aspects are a way to group events into incidents. Incidents allow IT personnel to recognize events that have the greatest impact on the business and to react quickly and appropriately to restore normal operations, either by implementing a known fix. Aspects include: Application Failures, Connectivity, Performance, Security, Operational Info and System Failures |
| Assembly Inspector | The AVIcode Assembly Inspector supports browsing managed assemblies when adding functions. It displays all namespaces, classes, functions, exception handlers and resource calls related to a selected application and allows users to select items to be added for monitoring. It displays the full name of selected function in the status bar at the bottom of the window. It also allows user to find functions, classes or namespaces in an assembly by searching for all nodes that have a name which includes a user input string as substring |
| Average Duration | The 'Average Duration' value is the average event time for all performance events in the group. Clicking on the 'Avg. Duration' column header will cause the event list to sort in either ascending or descending numeric order by Average Duration. |
| Build | The version from the main assembly of the application, which is automatically incremented when the assembly is built, and which is stored in Assemblyinfo.cs |
| Callee | A child function that is called by the current function |
| Caller | A parent function that calls the current function |
| 'Category' | The 'Category' field is included for compatibility with the Microsoft Event Log. For exception events, it displays the exception class, but it unused for performance events |
| Chain | The relationship between applications and related Web Service and .NET Remoting calls associated with a client-side business transaction. |
| 'Code' Column | The 'Code' column will display the relevant exception class for Exception Events. Performance events do not use this column. |
| Component | Win32, COM or .NET DLL. In development environment library typically corresponds to Visual Studio Project. It's typically deployed as part of an application. |
| 'Computer' | The 'Computer' field displays the name address of the monitored computer (from which the Intercept Agent generated an event). Clicking on the 'Computer' column header will cause the event list to sort in either ascending or descending alphabetical order by computer. |
| 'Count' | For consolidated events, the 'Count' indicates how many events are in the group (i.e., related to the same problem). Clicking on the 'Number of Events' column header will cause the event list to sort in either ascending or descending numeric order by Number of Events. |
| Critical Exception | 
Intercept defines Critical Exceptions as being those that lead to a
monitored component's failure. For ASP.NET applications, a critical
exception results in the user seeing either the standard or a
custom error page. For web services, critical exceptions are those
that ASP.NET serializes into valid SOAP messages on the
server-side, and deserializes to SoapExceptions on the ASP.NET
client. |
| CSM | Client Side Monitoring |
| Defragmentation Self Maintenance | As of Version 5.0, the Configuration Utility supports defragmentation for the SEViewer and Reporting MS SQL databases. Over a period of time, because of the inserts, updates and deletes, the data and the index pages can get fragmented. The more fragmented a database is, the more slowly the data can be accessed. Defragmentation is a process that physically reorganizes the contents of the disk to store the pieces of each file close together and contiguously. It also attempts to create larger regions of free space using compaction to impede the return of fragmentation. |
| 'Description' Column | By clicking on any 'Description' value for an event, SE-Viewer will automatically populate and display the 'Event' (for single events) or 'Event Group' (for consolidated events) view dialog for that event. The tabs on the dialog, as well as the contents of each tab, vary depending on the type of event that you choose. The table below indicates which tabs and fields will appear in the dialog based on the selected event. Clicking on the 'Description' column header will cause the event list to sort in either ascending or descending alphabetical order by description. |
| Developer Workstation | Allows users to access SE-Viewer events and to the associated lines of source code. Where source code and Visual Studio reside. |
| Display Name | The 'Display Name' serves as an alias for the application name that uniquely identifies an application in all phases of monitoring, from configuration to monitoring, viewing and reporting in SEViewer. The default display name is the process name for executables, and the IIS property 'Application name' for web applications. |
| 'Duration' Column | The 'Duration' field allows you to see how long (in milliseconds) an event lasted. |
| Edge | A relationship between two functions where one (caller) is calling the other (callee) |
| Edge Time | Time contributed to the total time of a callee function when called from a specific caller function. The sum of the edge time of all the incoming edges to a function equals to this function's total time |
| Edge Total Time | The execution time of a particular function when called from a specific parent function |
| Entrypoints | Entrypoints, or top-level functions, are the point from which Intercept Studio begins timing execution for slow performing business transactions. A separate performance event is generated for each entrypoint whose execution time exceeds the alerting threshold set for it. |
| Event Class | The Event Class indicates whether an event is a '.NET Performance Event' or a '.NET Exception Event', 'Client Side Exception Event', 'Client Side Performance Event', 'Client Side Action Performance Event', 'Client Side Action Performance Event' |
| 'Event Code' | The 'Event Code' field is included for compatibility with the Microsoft Event Log. For exception events, it displays the exception class, but it unused for performance events. |
| 'Event Date' | For Single events, the 'Event Date' field allows you to see the date/time stamp for when an event occurred. |
| Event Log events | Events pulled from the Windows Event Log |
| Event Throttling | The main goal of Event Throttling is to keep CPU Utilization low by constraining the rate at which events are sent to SE-Viewer. The 'Enable Event Throttling' checkbox on the General tab allows you to constrain the rate at which events are collected to improve system performance. Events are constrained by the number of events collected in an event group over time. |
| Event Type | The event type for a performance event is 'information', and the Event Type for an exception event is 'error'. |
| Exception Events | Exception Events are critical application and system errors. Intercept defines critical errors as being those that lead to a monitored component's failure. For ASP.NET applications, a critical exception results in the user seeing either the standard or a custom error page. For web services, critical exceptions are those that ASP.NET serializes into valid SOAP messages on the server-side, and deserializes to SoapExceptions on the ASP.NET client. |
| Exception Handlers | Exception handlers are application functions that are called in exception catch blocks to report errors and perform some error handling. |
| Failed Function | A failed function is the function call from the call stack that actually caused an exception,, e.g. the last method called from the user code or a call to a web service or .NET Remoting call |
| First Event Date | The 'First Event Date' field allows you to see the date/time stamp for when the first event in the group occurred. |
| Function Offsets | Function Offsets appear in the event detail stack area (at the end of each stack frame), and permit using Ildasm.exe to locate the actual line of source code corresponding to the particular stack frame. |
| Heaviest Resource | The resource call that exceeded it's threshold more than other resources |
| ID | A unique numerical identifier for the event. |
| Intercept Agent | Resides on a Monitored System. It gathers exception and performance information from a monitored application and reports it to Intercept SE-Viewer. |
| Intercept Service | Collects events from the Windows Event Log. |
| Interesting Functions | Also known as well-known functions, an exception is 'interesting' if the system is configured to collect it. |
| Key Metrics | The Key Metrics tab in SE-Viewer provides an at-a-glance view of a selected application. The graph displays 1) the average performance based on the Monitored Requests counter, and 2) the number of requests. By looking at the graph, you can easily determine the traffic load, and make inferences about problems that may be occurring. |
| KPI Dashboard | A dashboard provided in the AVIcode OpsMgr 2007 Management Pack as of Version 5.1. This dashboard provides a set of standard rules and monitors that will collect KPI (Key Performance Indicator) data using performance counters. The Application Health state is represented to Operation personnel as monitoring of performance counters. |
| Last Event Date | When SE-Viewer consolidates events, the 'Last Event' field allows you to see the date/time stamp for when the last (most recent) event in the group occurred. Clicking on the 'Last Event' column header will cause the event list to sort in either ascending or descending date/time order by last event. |
| Light/Heavy Optimization | The 'Enable Data Collection Optimization for Light Requests' checkbox, when checked/enabled, ensures that optimal performance is achieved by the agent. There are times however that you may be interested in bypassing this optimization in order to collect resource call data for all events. Intercept Management Console > 'Applications' node > 'Properties' > General tab |
| 'Local Date' | The 'Local Date' field displays the date/time that an event occurred in local browser time. |
| Management Data Storage | Data storage for Intercept events. Intercept SE-Viewer supports: Microsoft SQL 2005 Microsoft SQL 2008 and SQL Express. We recommend Microsoft SQL 2005 or 2008 for a production configuration, but Microsoft SQL Express may also be used for smaller deployments. |
| Management System | The system where your event management software is installed (e.g. Intercept SE-Viewer, MOM) for monitoring your network or intranet. |
| Max Duration | The 'Max Duration' value is the longest event time for any performance event in the group |
| Metrics | The statistics which help analyze both an application’s load and it’s ability to respond to it are referred to as metrics. |
| module | A module is an executable file or a dynamic link library (DLL). |
| Monitored System | The system where a monitored ASP.NET, Web Service, Executable application, Windows Service or COM+ application runs and where the Intercept Agent resides. |
| Number of Events | For consolidated events, the 'Number of Events' indicates how many events are in the group (i.e., related to the same root problem). |
| Operations Mode | Operations Mode provides concurrent monitoring of exceptions and performance. |
| PDB File | A program database (PDB) file holds debugging and project state information that allows incremental linking of a Debug configuration of your program. |
| Performance Counters | In addition to the information contained in the Intercept performance events, additional performance metrics may be collected with counters. Metrics of particular interest tend to be response time, throughput, and resource utilization (how much CPU, memory, disk I/O, and network bandwidth your application consumes while performing its tasks). Developers can also instrument their code with custom performance counters. Counter information is displayed in SE-Viewer. |
| Performance Events |  An event
raised if request times between monitored components and external
systems (such as SQL servers, Web Services, TCP/IP servers, OLE DB
providers and others) exceed predefined thresholds. |
| Problem | Grouping by 'Problem' means that all events have the identical call stack. Consolidating events by problem, meaning that the events all have the same call stack, allows IT personnel to prioritize their efforts to correct an issue based on the number of events in the group |
| Related events | Other events that may be related to the selected event based on time.. Time based correlation helps to establish causality by grouping Operational, Performance, System and Application events that occur over a defined period |
| Request Method | GET or POST |
| Resource Utilization | AVIcode shows statistics for resource utilization, so that users can see how their computers are doing under pressure. We will show, for example, how many users are logged into an application at a given time, how many errors they are encountering, and how quickly the application is performing for them. |
| 'Root node' | The location where the exception was raised, which provides information about entry points (external call) for application: Asp page, Webservice method, Remoting methods and etc. |
| Self Time | Time spent inside a function, including time spent waiting between execution activities. It does not include time spent in calls to other instrumented functions |
| Sensitivity Threshold | Sensitivity thresholds apply to resource calls, and are less than or equal to the alerting threshold (generally being set to approximately 100 ms). The sensitivity threshold causes the Intercept Agent to collect information about specific resource calls that take longer than the preset threshold. |
| 'Severity' Icon | Each event has an icon that indicates its severity level, which
may be Information (for Performance Events), Critical Error
for Critical
Exception Events from the Operations Monitor or Non-critical Error
 for
Handled or non-Critical Exception Events from the Operations
Monitor. |
| SE-Viewer | Intercept SE-Viewer is a centralized event Management System for enterprise monitoring. With inputs from the Intercept Operations Monitor, Intercept SE-Viewer allows data center personnel to monitor deployed .NET applications for slowdowns, faults and failures, and immediately pinpoints the source of the problem. It provides problem diagnosis down to the source-code level without developers having to alter the code. Intercept SE-Viewer supports a rich event notification infrastructure that allows integration with operations Management Systems such as Microsoft Operating Manager, Tivoli, BMC and HP OpenView. |
| SE-Viewer Navigation Pane | The resizable 'Navigation Pane' allows you to access the filtering and reporting capabilities of SE-Viewer. |
| SE-Viewer Preview Pane | Displays the Event Properties Tab of the Event Dialog. |
| SE-Viewer Server | installs on Your Management System and receives events gathered by the Intercept Agent. It also allows you to route events to other event Management Systems (such as MOM) or to defect tracking systems. |
| SE-Viewer Toolbar Area | The Toolbar options provide all of the tools that you will need to control the quantity and type of information to display in SE-Viewer. For your convenience, SE-Viewer includes a shortcut toolbar below the Main Menu for quick option access. |
| SE-Viewer View Pane | The View Pane provides a list of selected events. |
| Similar events | Events that are like one another - criteria similarity depends on the type of event |
| Source | The Source is the name of the web application from which Intercept Studio received the event. Clicking on the Source column header will cause the event list to sort in either ascending or descending alphabetical order by source. |
| State Performance Counters | State performance counters are used to monitor the immediate health state of an application by collecting a snapshot of configured performance counters at 5 minute intervals. This data is available for viewing trends SE-Viewer. |
| Store and Forward | For business scenarios when a centralized management system (like SE-Viewer) is not available or has limited access, AVIcode's Incident Utilities provide a method to store data locally for subsequent forwarding. This feature allows users to address disconnected desktop installations, network traffic optimization and troubleshooting processes. |
| subscriber | Any application that consumes events. AVIcode Intercept Studio subscribers include email, WMI and the Windows Event Log |
| system | A set of applications working together on a common task. In development environment a system would typically correspond to a Visual Studio Solution |
| Tenant information | A string included in the HTTP context that identifies the business context for each web application request. Configuration options allow retrieving this business context identifier from any point of the web request context |
| 'Time-only' Entrypoints | Only the execution time will be captured, without any runtime variables |
| Total Time | Time elapsed between the time a function starts execution until the time it terminates execution. This is the sum of this function's Self Time and all its callees Total Time |
| 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. |
| TTFB | Time To First Byte |
| TTLB | Time To Last Byte |
| uX | user eXperience |
| uX Collector | The uX Collector is part of the Intercept uX product, and is the component that receives client events and statistics from end users. |
| Visual Studio Plug-in | Resides on a developer system, and allows you to access the actual line of defective source code via Microsoft Visual Studio .NET |
| 'Web Applications' node | The 'Web Applications' node allows you to configure the default settings for all applications running under IIS. There is no need to add an individual application under this node unless you want the application to have settings which differ from the default. |
| WMI | Windows® Management Instrumentation (WMI) provides management information and control for objects in a managed enterprise environment. |
Last update: Thursday, December 02, 2010 12:26:56 PM