Navigate to "Management Pack
Templates""Enterprise .NET Executable"
or"Enterprise .NET Windows Service"
or"Enterprise ASP.NET Application"
or"Enterprise ASP.NET Web Service"
Select the appropriate application template from the list of
configured templates
Right-click and select 'Properties' from the menu
Go to the 'Application Monitoring' tab or the 'Transaction
Monitoring' tab
Follow the directions under "Initial Configuration" earlier in
this document
Configuration changes made to ASP.NET Applications and Web
Services will only take effect after an IIS restart/recycle.
IIS 6 and IIS 7 (by default) require an IIS restart when
configured for 'Service Activation Mode', but when configured for
'Starter Activation Mode', recycling the application pool will make
the changes take effect. Enabling monitoring requires restarting
IIS for discovered applications. Making changes to the monitoring
settings (e.g. after adding/deleting functions, resource,
entry-points, namespaces) requires an application pool recycle. A
recycle is not required after changing threshold settings.
To restart IIS:
Open the Operations Manager 2007 Console.
Go to the "Monitoring View"
Navigate to "AVIcode .NET Application
Monitoring""Monitoring
Agent State"
Select one or more of the state alerts
In the 'Actions' pane, select "Enterprise .NET Monitoring Agent
Tasks" "Restart
Internet Information Services"
Click Run
To recycle IIS:
Open the Operations Manager 2007 Console.
Go to the "Monitoring View"
Navigate to "AVIcode .NET Application
Monitoring""Monitoring
Agent State"
Select one or more of the state alerts
In the 'Actions' pane, select "Enterprise .NET Monitoring Agent
Tasks" "Recycle
Application Pools" Individual pools cannot be selected.
This action will cause all application pools to be recycled
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.
Select "Object Discoveries"
In the "Object Discoveries" window, select 'Change
Scope'
Select 'View All Targets'
In the 'Look for' field, enter 'AVIcode
Click Select All
Click OK
Under 'Discovered Type: ASP.NET Application Endpoint' (or
'Discovered Type: ASP.NET Web Service Endpoint' ), right-click the
'Discovery ASP.NET Applications' node
Select 'Overrides' 'Override the Rule' make selection for all objects, a
group, or a specific instance
Select the 'Override' checkbox next to the 'Web Extensions
List' (or 'Web Services Extensions List') field
Change the 'Override' value by adding additional extensions,
separating each with a semi-colon
Click OK
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.
Select "Object Discoveries"
In the "Object Discoveries" window, select 'Change
Scope'
Select 'View All Targets'
In the 'Look for' field, enter 'AVIcode
Click Select All
Click OK
Under 'Discovered Type: ASP.NET Application Endpoint' (or
'Discovered Type: ASP.NET Web Service Endpoint' ), right-click the
'Discovery ASP.NET Applications' node
Select 'Overrides' 'Override the Rule' make selection for all objects, a
group, or a specific instance
Select the 'Override' checkbox next to the 'Need Check
Subfolders' (or 'Web Services Extensions List') field
Change the 'Override' value to 'True' or 'False'
Click OK
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.
Select "Rules"
In the 'Rules' window, select 'Change Scope'
Select 'View All Targets'
In the 'Look for' field, enter 'Windows Computer'
Click Select All
Click OK
Under 'Type: Windows Computer', right-click the 'Enable
Enterprise Mode' node
Select 'Overrides' 'Override the Rule' make selection for all objects, a
group, or a specific instance
Select the 'Override' checkbox next to the 'SecureConnection'
field
Change the 'Override' value to 'True' or 'False'
Click OK
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.
Select "Rules"
In the 'Rules' window, select 'Change Scope'
Select 'View All Targets'
In the 'Look for' field, enter 'AVIcode'
Click Select All
Click OK
Under 'Type: Enterprise .NET Monitoring Agent, right-click the
'Set Net Framework Version' node
Select 'Overrides' 'Override the Rule' make selection for all objects, a
group, or a specific instance
Select the 'Override' checkbox next to the
'NetFrameworkVersion' field
Change the 'Override' value to the correct framework
version
Click OK
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:
'ExceptionsTotalChains' counter
'ExceptionsInteresting' counter
'ExceptionsPerDomain' counter
'ExceptionsEventGroups' counter
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).
The ExceptionsEventGroups
counter tracks the number of exceptions for each Event Group. All
events in an Event Group have encountered the same Problem, and
therefore have identical call stacks. The 'ExceptionsEventGroups'
is a logical threshold that is not directly related to resource
(CPU) usage, but prevents you from receiving an unreasonable number
of the same event repeatedly. When the threshold is reached,
Intercept Studio will stop reporting events from that group to
SE-Viewer for the configured time period, but it will continue
incrementing the internal event counter for that group. When events
are displayed in SE-Viewer grouped by 'Problem', the 'Count' column
will display the actual count of all events that occurred in the
group, even though only the first 'ExceptionsEventGroups' events
will be displayed within the group.
The ExceptionsPerDomain counter
tracks the number of exceptions raised in particular web
application (application domain). The 'ExceptionsPerDomain' is a
logical threshold that protects your system against excessive CPU
usage and from excessive network traffic from sending too much
data. In situations where SQL server is down, your disk is full,
not enough memory, etc., an unusual number of exceptions may thrown
from an application, each from a different place in the code and
each with a different exception. This threshold will stop
collecting and reporting exceptions from that application for the
configured time period. The result is that if you have multiple
application domains running under a single process (see
'ExceptionsInteresting'), and one of the application domains is
throwing excessive exceptions, that only that domain will be
throttled while the rest are being monitored normally.
The ExceptionsInteresting
counter tracks the number of 'interesting' exceptions. An exception
is 'interesting' if the system is configured to collect it. If the
system is configured to only collect 'critical' exceptions, the
only 'critical' exceptions are considered 'interesting'. If the
system has been configured to collect 'All' exceptions and 'Custom
Handlers' have been added, then all exceptions and the custom
handlers will be considered 'interesting'. 'Interesting' exceptions
are collected on a per physical Win32 process basis (ASP.NET,
.exe's, DLLs, etc). The 'ExceptionsInteresting' is a logical
threshold that protects your system against excessive CPU usage and
from excessive network traffic from sending too much data. If too
many exceptions are being reported from a particular process, then
throttling will take effect, which all exceptions from other
processes will still be reported.
The ExceptionsTotalChains
counter tracks the entire number of caught exceptions. While
'ExceptionsEventGroups', 'ExceptionsPerDomain' and
'ExceptionsInteresting' all apply to 'Interesting' events (see an
explanation of what is considered 'Interesting' under
'ExceptionsInteresting'), this threshold applies to all exceptions
thrown regardless of whether the system is configured to report
them, or not. Under normal circumstances, the system must perform
at least a cursory analysis of each exception to determine whether
or not it is 'interesting', and if detailed data should be
collected. This threshold is the last line of defense to protect
against excessive CPU usage. Should something occur that causes
your applications to throw an excessive number of exceptions,
monitored or not, this threshold will cause throttling to take
effect.
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.
Select "Rules"
In the 'Rules' window, select 'Change Scope'
Select 'View All Targets'
In the 'Look for' field, enter 'AVIcode'
Click Select All
Click OK
Under 'Type: Enterprise .NET Monitoring Agent, right-click the
'Set Event Throttling Parameters' node
Select 'Overrides' 'Override the Rule' make selection for all objects, a
group, or a specific instance
Select the 'Override' checkbox next to the field you want to
change
Change the 'Override' value
Click OK
Last update: Thursday, December 09, 2010
02:01:58 PM
"Authoring View"
"Management Pack
Templates"
"Enterprise .NET Executable"
or 
"Enterprise .NET Windows Service"
or 
"Enterprise ASP.NET Application"
or 
"Monitoring View"
"AVIcode .NET Application
Monitoring"
"Monitoring
Agent State"
Individual pools cannot be selected.
This action will cause all application pools to be recycled
'Management Pack Objects' node
"Object Discoveries"
"Rules"
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.