I wanted to cover some termiology to make clear each component, AVIcode is a product and currently still is that can run as a standalone product, although Microsoft want you to use it as an ‘Add-In’ to Operations Manager. Operations Manager does tidy the deployment up and I think really enhances the AVIcode Solution making it a joy to deploy and configure via the Ops Mgr console with the additional tool set that is offers the operator.
Terms (with Short Descriptions)
- 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.
- CSM Client Side Monitoring also know as uX
- 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.
- 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.
- 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.
- 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. Authors Note. “ We do not need PDB files for AVIcode to work just to break in to the complied dll files.
AVIcode Intercept Agent provides the following monitors:
- Intercept Operations Monitor – collects performance and exception information from .NET applications.
- Intercept Event Log Monitor (part of the Intercept service) – collects events from the Windows Event Log
- Intercept Performance Counter Monitor (part of the Intercept service) – collects both State performance counters (for current application health state) and Troubleshooting performance counters (for historical application health state)
The Intercept monitors attach to any .NET application on the fly, without any code modifications or recompilation of the monitored application. The Intercept Agent uses standard common language runtime (CLR) mechanisms, so that it will have no behavioral effect on the monitored application.
Intercept Operations Monitor collects exception events and measures application performance so that you can quickly identify and quantify performance problems in a production environment and effectively prioritize your problem resolution efforts. Intercept Operations Monitor allows you to capture exceptions and monitor the performance of your application at runtime without modifying your code, and to capture resource specific performance data.
Intercept Operations Monitor captures exception events, but by default it does not collect parameters for all functions, but does collect them for resources, entry-points and special functions that have been added for exception tracking.
Intercept Operations Monitor collects performance information about the communications of monitored components with external systems, such as SQL servers, Web Services, TCP/IP servers, OLE DB providers and others. It tracks request times for external resource calls, and raises an event if request times exceed predefined thresholds. The performance event information appears in a tree structure, where the root of the tree is the top-level function of a monitored component, and the leaves of the tree are calls to external systems. If the monitored component is a web application, the tree Root node is a page-process request call. If the monitored component is a web service, the tree Root node is a web-service function call. Intercept Operations Monitor also collects the runtime information about external system calls (i.e., query strings and query parameters for SQL calls, function names and function parameter values for web service calls).
Intercept Operations Monitor collects and feeds the performance data into Intercept’s event viewer (Intercept SE-Viewer).
The Intercept Service is responsible for activating monitoring for Applications, Web Services, Executables, Windows Services, COM+ Applications, Event Logs, Performance Counters and instrumentation. It also controls the Intercept Event Log Monitor and the Intercept Performance Counter Monitor.
The Intercept Event Log Monitor provides the ability to merge windows event log information into SE-Viewer for integrated visualization and reporting. This means that even custom event log events can be correlated to events gathered by Intercept’s other monitors.
Intercept Performance Counter Monitor
The Intercept Performance Counter Monitor collects key system and framework performance counters and automatically correlates that data with application events, providing a better understanding of how application problems and system performance relate. With insight into system and process level information, Intercept Studio enables advanced root cause diagnostics. Intercept Studio delivers a comprehensive view of application health by providing a “per process” and “system-level” view of key performance counters, as well a providing a view of counter trends.
The Agent Connector routes events from the Intercept Agent to event consumers. It consists of an event dispatcher and multiple adapters. When the Intercept Operations Monitor catches an event, it reports the event to the event dispatcher. The event dispatcher routes the event to the appropriate consumer via connector adapters, which are responsible for communications between the event dispatcher and event consumers.
The Intercept Management Console provides a convenient way to configure monitored applications in Intercept Studio. It allows system administrators to add applications, to select either performance or event monitoring, and to set thresholds and other options.
The SE-Viewer Configuration Utility provides a convenient way to configure SE-Viewer to use a Microsoft SQL Server database and to manage the Advisor database.
Next in the series: Deployment of the SEViewer:
Simon Skinner MVP