Editing the Configuration

Modifying the Template Properties

Restarting/Recycling IIS

Configuration changes made to ASP.NET Applications and Web Services will only take effect after an IIS restart/recycle.

To restart IIS:

To recycle IIS:

Advanced Agent Configuration

Accessing the Rules

Changing Rules

Adding extensions other than ASPX and ASMX

This functionality allows you to add file extensions other that ASPX and ASMX to be recognized as Enterprise ASP.NET Application or Enterprise ASP.NET Web Services during the discovery process.

Searching IIS subfolders during discovery

By default, only the IIS root folders are checked for files with ASPX or ASMX extensions (unless modified as described in the section above, Adding extensions other than ASPX and ASMX', or for the presence of a global.asax file.  This parameter allows you to specify that subfolders also be checked for these same file.

Extend Rules for SSL

ASP.NET monitored events can contain sensitive data (such as in SQL calls) and as result must be protected. The Management Pack supports event delivery from a Monitored System to SE-Viewer using the HTTPS protocol. As result, it protects the data during the delivery phase.

Change the Framework Version

The Management Pack automatically tests that AVIcode has tested your installed version of the .NET Framework with the monitoring agents to verify compatibility. If your framework version has not been tested, an alert will appear that says application monitoring has been disabled because the framework version has not been verified, and to notify AVIcode about the problem. Once AVIcode has been notified, framework support can be enabled via the rule overrides.

Change Event Throttling

The main goal of Event Throttling is to keep CPU Utilization Low.

AVIcode exception monitoring compares the count of monitored events with limits, and will provide those events to SE-Viewer only if the limits are not exceeded. For the exception monitoring, there are four counters, named as follows:

For each counter three attributes can be set: 'per minute', 'per hour' and 'per day' limit values.

Each of them defines the maximum number of events in corresponding time periods (minute, hour or day), which will be provided to SE-Viewer. Part of the sample configuration above shows all operable limits for each type of counter (if you set, for example, perHour='60' for 'ExceptionsTotalChains' counter, it will be ignored).

Setting a small value for the perMinute attribute for this counter could cause you to not receive any events. This value should only be changed if there is a significant reason to do so.

The first time any limit is exceeded an alert will notify you that some events have been lost.

Last update: Thursday, December 09, 2010 02:01:58 PM