|
3
|
- Enter a friendly name and description
- Name: Enter a friendly name for
the application. This is the name that will appear in the Intercept
MMC.
- Description: Enter a
description for the application
- Discover on all computers included in
.NET Agent Deployment Group: If this checkbox is enabled,
then agent deployment and monitoring will be done for
computers in the .NET Agent Deployment Group. If the checkbox is
disabled, then deployment of agents and monitoring agent
deployment and monitoring will be done for computers included both
in the .NET Agent Deployment Group and in the group selected from
the dropdown list.
- number minutes: Enter the time, in minutes, for the
system to check for discovery of the application running in the
deployment group. This same value will be used for the
discovery interval for transaction monitoring list. See
'Transactions' in section 5 below for more information. [default =
240 minutes, minimum value = 10 minutes
The Management Pack you create or select will be used to store
application monitoring settings.
To create using the default management
pack: Leave the 'Use existing management pack or create new'
checkbox disabled. This will create a new MP based on the friendly
name entered above, as reflected in the destination MP display name
field.
 In general,
it is best to use the default option. Creating a management pack
based on the default management requires manually cleaning the MP
in order to uninstall.
To use an existing management
pack: Select the 'Use existing management pack or create
new' checkbox . Choose an existing MP from the dropdown list
combo-box. This will create a new MP based on the existing MP, as
reflected in the destination MP display name field. The selected MP
will be used to store application monitoring settings.
To create a new management pack:
Select the 'Use existing management pack or create new' checkbox .
Click New....
|
General Properties
|
|
a
|
Management Pack General Properties
- ID: A read-only field that
displays the name of the new management pack.
- Name: The user-defined name for
the management pack.
- Version: The user-defined
version for the management pack. The version number must be of the
format: Number.number.number.number, where each number may not exceed 10 digits.
- Description: The name of the
unique instance of the performance counter.
|
|
Knowledge Article
|
|
b
|
Knowledge
Visual
Studio 2005 Tools for Microsoft Office is a Systems Center
requirement for being able to add/modify management pack knowledge
articles.
- the knowledge text area: Create
a Knowledge base for the new MP
- Edit...: This will launch a
Microsoft Word template for creating your Knowledge article
|
- Create destination management
pack: The name of the MP automatically generated from
the Application Display Name. This MP will be used to store
application monitoring settings.
- Use existing management pack or
create new: Create a custom MP or select an existing one to
store application monitoring settings. If not checked, the MP will
automatically generate a new MP.
|
|
4
|
Application
Thresholds
The Management Pack monitors for performance at two levels: 1)
the execution time of a web page or entry points of an executable
application (top level functions), and 2) the execution time of
calls to resources from within those top level functions. The
threshold set for the execution time of a page or executable's
entry point is called the 'Alerting Threshold', and by default is
set to 15000 ms. The threshold for the execution time of a
resource call is called the 'Sensitivity Threshold', and by default
is set to 100 ms. How are entrypoints and performance events
related? Performance event timing begins when the monitor
encounters a known entrypoint and completes when the processing of
the entrypoint finishes. If that time exceeds the alerting
threshold, then a performance event will be reported.
- Alerting Threshold : set the
'Alerting Threshold' milliseconds: 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 [default = 15000 ms].
- Sensitivity Threshold: set the
'Sensitivity Threshold' milliseconds: 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 [default = 100 ms].
Performance Counters
Collection
This section is for selecting the performance counters that are
exposed at the application level. Performance counters are used to
monitor the immediate health state of an application by collecting
a snapshot of configured performance counters at regular intervals.
By default, the 'Avg. Request Time' , 'Monitored Requests/sec' , '%
Exception Events/sec' and '% Performance
Events/sec' performance counters are all exposed by default.
These counters are unique to the monitoring agent, and allow
monitoring of metrics for .NET Remoting applications or WinForm
applications, which otherwise would have no standard counters.
- Avg. Request Time: The average
time (in milliseconds) that it takes for a request to be processed
by .NET applications configured for operations monitoring. The
timing of each request begins from when it triggers an entrypoint
configured for the process, and is stopped when the request
completes successfully or fails somewhere in the code. The sum of
these times is averaged across the total number of requests being
monitored. If this time consistently the alerting threshold, it
indicates a bottleneck that should be investigated. This counter is
only available when AVIcode Operations Monitoring is enabled.
[default = 10000 ms]
- Monitored Requests/sec: The
total number of requests each second that are being processed by
.NET applications configured for operations monitoring. This
counter is incremented when the request triggers an entrypoint
configured for the process. [default = 15 requests/sec]
- % Exception Events/sec: This
counter is a value calculated by dividing the number of exception
events/sec by the total number of events. The total number of
exception events is based on the agent configuration, critical vs.
all exceptions, customized exception handlers, etc. This number may
be larger than the number of exception events reported to
SE-Viewer, because it also includes events that are suppressed by
Event Throttling. [default = 15%]
- % Performance Events/sec: This
counter is a value calculated by dividing the number of performance
events/sec by the total number of events. The number of total
number of performance events is based on the agent configuration,
threshold levels, enabled namespaces, etc. This number may be
larger than the number of performance events reported to SE-Viewer,
because it also includes events that are suppressed by Event
Throttling. [default = 20%]
- Interval: number Seconds/Minutes/Hours/Days. State
performance counters are used to monitor the immediate health state
of an application by collecting a snapshot of configured
performance counters at number
minute intervals [default = 5 minutes].
- Custom Counter List...: This
option allows you to add your own performance counters in addition
to those already exposed by default by the management pack. So, if
your application has your own custom performance counters, or you
would like to use the MP to continue monitoring a particular set of
performance counters that you typically use, add them via the
Custom Counter List... option.
To Add or Edit Custom Performance
Counters: Select either Add
or Edit to open, add to or
modify the list of custom performance counters.
|
Specify the performance counter
|
|
a
|
Either enter the display name, object, counter, and instance
into the text field, or use Browse... to select the appropriate counter,
which will automatically fill in the text fields.
- Display name: The rule name for
collecting the custom performance counter (without aggregation) for
displaying in the Operations Console
- Object: The Object (category)
name for the performance counter.
- Counter: The name of the
performance aspect to be measured within the object category.
- Instance: The name of the
unique instance of the performance counter.
- Include all instances for the selected
counter: Although some objects (such as Memory and Server)
have only a single performance object instance, some performance
objects can have multiple instances. If an object has multiple
instances, you can add counters to track statistics for all
instances at once. Enable this checkbox to aggregate values for
this counter from across all discovered computers into a single
reported value. Disable this checkbox to only collect the selected
instance.
If
the counters category does not support instances such as Memory or
Server, leave the instance text box empty.
To Browse and Select a Performance
Counter: Click Browse... to
look through all system counters.
|
Browse or enter computer name
- Computer: Enter the name of the
computer, or click ... to make a
selection
Performance Counter
- Object: Select the object
(category) from the dropdown list
- Select counter from list:
Select the counter
- Select instance from list:
Select the instance of the counter, or check the 'All Instances'
checkbox below
- Explain...: Display the
description for the counter in a popup window.
- All Instances: This checkbox is
always unchecked and disabled. Use Include
all instances for the selected counter from the parent
screen.
|
|
|
Aggregation settings
|
|
b
|
This section allows users to configure how data that is
aggregated from across multiple computer sources will be displayed
in the KPI dashboard.
- Aggregation Counter name: The
default name of the aggregation counter as it will appear on the
KPI dashboard. The name created by combining the name of the
selected counter and selected aggregation function. This name
may be changed by the user.
- Aggregation Function: This
dropdown allows users to select the function to use when
calculating the aggregation counter. Functions include calculating
the aggregated value based on the Sum, Average, Minimum or Maximum
values.
- Show trend in the dashboard:
When this checkbox is enabled, trends for the aggregated
performance counter will be shown in the KPI dashboard.
|
To Delete Custom Performance
Counters: Select a counter from the list and click
Delete
To Change the Order that Custom
Performance Counters will appear in the Trend Reports:
Select a counter from the list and click Move Up or Move
Down
Collect Alerts by Event
Type
The management pack reports problems in two ways: via problem
based alerts and via the application state. For each unique
problem signature, the MP generates a unique alert inside of
Operations Manager. This section allows user to decide
whether or not to generate problem based alerts, and which type of
problems based alerts should be generated.
- Application Failure: Select
this checkbox to enable rules to collect Application Failure
alerts, or deselect to disable the collection rules. This is
disabled at the Application level.
- Performance: Select this
checkbox to enable rules to collect Performance alerts, or
deselect to disable the collection rules. [default = not
selected]
- Connectivity: Select this
checkbox to enable rules to collect Connectivity alerts, or
deselect to disable the collection rules [default = selected].
- Security: Select this checkbox
to enable rules to collect Security alerts, or deselect to disable
the collection rules [default = selected].
Monitors
The Management Pack monitors at both the overall application
health level and at the business transaction level. The overall
application health state can be monitored with respect to the
number of exception and performance events and application
load.
- The % Exception Events/sec
exceeds number [default =
15 percent]
- The Average Request Time
exceeds number [default =
10000 milliseconds]
To Add or Edit Application Load
Monitors: Select either Add
or Edit.
Several
monitors of the same type can be added, but the thresholds for
these monitors must be different.
|
Select the monitor type from the list
(available for 'Add' only)
|
|
a
|
Select from the following list of available monitor types which
can be added for applications or transactions:
- The Average Request Time exceeds
threshold: The instance state becomes unhealthy if the
average request execution time per predefined escalation time
period exceeds an escalation threshold. Application performance
alerts are generated when the execution time exceeds the configured
Alerting Threshold. The alert details break down the execution time
by percentage spent in various types of resource calls and in the
internal code execution. Excessively long SQL, Oracle, ODBC, DB2 or
OLEDB calls may be due to either a problem with the database server
or with the structure and complexity of the database query. Long
file I/O times may be due to problems with the file server. Web
Services performance issues may occur because the web service or
the server it resides on is down or there is a problem in the Web
Service code. Long internal execution times for applications may
result from a complex or inefficient code. Application performance
alerts are generated when the average execution time exceeds the
configured threshold. Typical application performance degradation
could be due to a long database call, long web service call, slow
.NET Remoting call or COM+ call, or inefficient application
code.
- The Number of Monitored Requests/sec
exceeds threshold: The instance state becomes unhealthy if
the total number of monitored requests per predefined escalation
time period exceeds an escalation threshold. The total number of
requests each second that are being processed by .NET applications
configured for operations monitoring. This counter is incremented
when the request triggers an entrypoint configured for the process.
This counter shows number of requests (for example to web pages)
that have a duration greater than the Application Alerting
Threshold. The alert details break down the execution time by
percentage spent in various types of resource calls and in the
internal code execution. Excessively long SQL, Oracle, ODBC, DB2 or
OLEDB calls may be due to either a problem with the database server
or with the structure and complexity of the database query. Long
file I/O times may be due to problems with the file server. Web
Services performance issues may occur because the web service or
the server it resides on is down or there is a problem in the Web
Service code. Long internal execution times for applications may
result from a complex or inefficient code. Application performance
alerts are generated when the number of monitored requests that
exceed the configured Alerting Threshold more than configured
monitor Threshold. I don't understand what the part in yellow means
- Typical application performance degradation could be due to a
long database call, long web service call, slow .NET Remoting call
or COM+ call, or inefficient application code.
- The % Performance Events/sec exceeds
threshold: The instance state becomes unhealthy if the total
number of performance events per predefined escalation time period
exceeds an escalation threshold. Application performance alerts are
generated when the number of performance events exceeds the
configured monitor threshold. The alert details break down the
execution time by percentage spent in various types of resource
calls and in the internal code execution. Excessively long SQL,
Oracle, ODBC, DB2 or OLEDB calls may be due to either a problem
with the database server or with the structure and complexity of
the database query. Long file I/O times may be due to problems with
the file server. Web Services performance issues may occur because
the web service or the server it resides on is down or there is a
problem in the Web Service code. Long internal execution times for
applications may result from a complex or inefficient code.
Application performance alerts are generated when the number of
performance events exceeds the configured monitor threshold.
Typical application performance degradation could be due to a long
database call, long web service call, slow .NET Remoting call or
COM+ call, or inefficient application code.
- The % Exception Events/sec exceeds
threshold: The instance state becomes unhealthy if the total
number of exception events per predefined escalation time period
exceeds an escalation threshold. Application availability alerts
are generated when the number of exception events exceeds the
configured monitor threshold. The alert details break down the
execution time by percentage spent in various types of resource
calls and in the internal code execution. Excessively long SQL,
Oracle, ODBC, DB2 or OLEDB calls may be due to either a problem
with the database server or with the structure and complexity of
the database query. Long file I/O times may be due to problems with
the file server. Web Services performance issues may occur because
the web service or the server it resides on is down or there is a
problem in the Web Service code. Long internal execution times for
applications may result from a complex or inefficient code.
Application availability alerts are generated when the number of
exception events exceeds the configured monitor threshold. Typical
application performance degradation could be due to a long database
call, long web service call, slow .NET Remoting call or COM+ call,
or inefficient application code.
|
|
Monitor properties (for both Add and Edit)
|
|
b
|
- Monitor Settings: The read-only
name of the selected monitor
- Specify threshold value to
match:
- Threshold: Number percent. This number indicates how many performance or
exception events (as a percentage of all monitored requests) can
occur per interval before affecting the health state. Available
only for '% Performance Event' [default = 20 percent] and '%
Exception Event' [default = 15 percent] monitors.
- Threshold: Number milliseconds. This number indicates the most number of
milliseconds the average request time can last per interval before
affecting the health state. Available only for 'The Average
Request Time' monitor [default = 10000 ms].
- Threshold: Number requests/sec. This number indicates the maximum monitored
requests that can be made per interval before affecting the health
state. Available only for 'The Number of Monitored
Requests/sec' monitor [default = 15 requests/sec.
- Specify Health State:
Health State: Select whether the
monitor will go to a Warning or Error health state when the
specified threshold is met for the specified interval [default =
Error].
- Specify the interval: Interval
number Seconds/Minutes/Hours/Days.
This number indicates the
frequency with which the Warning and Error thresholds will be
checked. For example, if the Warning threshold is 5, then a
state change will take place if 5 events occur within the
interval. It also indicates the frequency of the Monitor Rule check
[default = 5 minutes].
- Alert Properties: The alert
properties are displayed when an alert is generated in response to
the monitor changing state. The properties include: Alert Name (Provide a unique, descriptive name
for the alert to be generated), and Alert
Description (Provide a description of the possible causes
of, and resolutions to, this alert). The alert description can
contain any number of parameters formatted as %ParameterName%, that
will be replaced with actual values when alert is generated.
Possible parameters include: %Threshold%, %InstanceName%, %Value%.
The alert name can not contain parameters.
- Automatically resolve the alert when
the monitor returns to a healthy state: Select this checkbox
to have the MP automatically change alert resolution state to
'Closed' when the monitor returns to a healthy state [default
= selected].
|
To Delete Monitors: select a
monitor from the list and click Delete
|
|
5
|
The Management Pack not only monitors overall application
health, but also monitors at the business transaction level. So, in
addition to monitoring things like the overall volume of activity
on an applications, you may have, for example, 5 or 10 top
business transactions that you would like to monitor. In this
case you would define your own monitoring rules to see the volume
of traffic on those transactions or the average overall application
response time, and you want to have the ability to define monitors
and health rules for those 5 or 10 critical transactions. For each
transaction, we can expose the same performance counters as were
exposed for the overall application, like average response time or
number of events.
The discovery interval for transactions is defined in section 3
above.
Transactions: This list displays
the current list of monitored transactions. New Web Pages, Web
Services and Custom Functions can be added to the list (depending
on the application type being monitored).
To Add a Web Page: Click
Add web page. This option is
available for Enterprise ASP.NET Applications and Enterprise
ASP.NET Web Services
|
ASP.NET Page Settings
|
|
a
|
- Transaction Name: A user
defined string to describe a transaction to a web page, web service
or custom function
- ASP.NET Page: The virtual path
to the selected ASPX page, for example "/Virtual
Dir/mypage.aspx"
To Browse and Select an ASP.NET
Page: Click Browse...
|
Specify Account for Remote
Access
- Use current user checkbox
[default = selected]
- Account Name [default =
disabled]
- Password [default =
disabled]
Select Computer:
- Enter the name of the computer you want to browse assemblies on
or choose from a computer list. Leave this field empty for using
local computer ('...')
Select ASP.NET File (opens
automatically after selecting the computer)
- Choose an *.ASPX file with an entrypoint for Web Pages by
browsing for the file via Choose
file...
|
|
To Add a Web Service: Click
Add web service. This option is
available for Enterprise ASP.NET Applications and Enterprise
ASP.NET Web Services.
|
Web Service Settings
|
|
a
|
- Transaction Name: A user
defined string to describe a transaction to a web page, web service
or custom function
- Web Service File: The virtual
path to the selected ASMX page, for example "/Virtual
Dir/mypage.asmx"
To Browse and Select a Web Service
File: Click Browse...
|
Specify Account for Remote
Access: Enter the account information that will be needed to
access the remote file system so that the files and assemblies can
be browsed.
- Use current user: Select this
checkbox to use the current user, or disable in order to
enter a new user account name and password. The 'current user' is
the account used to log into the local machine [default =
selected].
- Account Name [default =
disabled]
- Password [default =
disabled]
Select Computer:
- Enter the name of the computer you want to browse assemblies on
or choose from a computer list. Leave this field empty for using
the local computer ('...')
Select ASP.NET File (opens
automatically after selecting the computer)
- Choose an *.asmx file with an entrypoint for Web Services by
browsing for the file via Choose
file...
|
- Method Name: The URL to a web
service method. Some usage examples:
1) A [SoapDocumentMethod] attribute is included in
the web service
Action
field=http://www.AVIcode.com/webservices/HelloWorld .
Method Name =
"http://www.avicode.com/webservices/HelloWorld
2) No defined namespace
[ActionName]=HelloWorld
Method Name =
http://tempuri.org/HelloWorld
3) [NameSpace] =
http://www.avicode.com/webservices
[ActionName]=HelloWorld.
Method Name =
http://www.avicode.com/webservices/HelloWorld
To Browse and Select a Method
Name: Click Browse...
Select a DLL File with an Entrypoint for Web Services
- Choose an DLL file with an entrypoint for Web Services by
browsing for the file via Choose
file...
- Drill down to the method:
- Drill down into the tree to select the method to act as the
entrypoint for the method
|
|
To Add a Function: Click
Add function. This option is
available for Enterprise ASP.NET Applications, Enterprise
ASP.NET Web Services, executables and Windows Services.
|
Custom Function Settings
|
|
a
|
- Transaction Name: By default,
this field will be filled in with ApplicationName_YourTransactionName,
ApplicationName is the name of the
executable, Windows Service, ASP.NET Application or web service the
monitor is being created for. 'YourTransactionName' will
automatically be replaced by the name of the selected
function.
- Function Name: Enter the name
of the function, or use the 'Browse...' to browse functions available from a
selected assembly.
To Browse and Select a Function
Name: Click Browse...
Specify Account for Remote Access
- Use current user checkbox
[default = selected]
- Account Name [default =
disabled]
- Password [default =
disabled]
Select Computer:
- Enter the name of the computer you want to browse assemblies on
or choose from a computer list. Leave this field empty for using
local computer ('...')
Select Managed Assembly (opens automatically after selecting the
computer)
- Use the file browser to find the assembly
Assembly Inspector
- Select the namespace or class from the Assembly Inspector. To
learn more about the Assembly Inspector, please refer to
About the Intercept MMC at the end
of this document.
|
- Function Module: The name of
the assembly the selected function resides in. When using the
Assembly Inspector (via Browse...),
this will automatically be filled in.
|
Performance Counters Collection
- Calls / sec: The total number
of calls of the monitored method each second that are being
executed.
- Avg. execution time: The
average time (in milliseconds) that the monitored method has been
executed. This counter is only available when AVIcode Operations
Monitoring is enabled.
- % of Exceptions/sec: This
counter records the percentage of exceptions raised in the
monitored method. This counter is only available when AVIcode
Operations Monitoring is enabled.
- % of Performance
violations/sec: This counter records the percentage of entry
points that have exceeded their threshold. You can set the
threshold for the concrete entry point, otherwise the default
settings for domain will be used.
- Interval: number Seconds/Minutes/Hours/Days. State
performance counters are used to monitor the immediate health state
of an application by collecting a snapshot of configured
performance counters at number
minute intervals [default = 5 minutes].
Collect Alerts by Event Type
The management pack reports problems in two ways: via problem
based alerts and via the application state. For each unique problem
signature, the MP generates a unique alert inside of Operations
Manager. This section allows user to decide whether or not to
generate problem based alerts, and which type of problems based
alerts should be generated.
- Application Failure: This field
tells the Management Pack whether or not you want Operations
Manager to report the health of your .NET application by the
frequency of exception problems. Select this checkbox to enable
rules to collect Application Failure, Connectivity and
Security alerts, or deselect to disable the collection rules
[default = selected].
- Performance: This field tells
the Management Pack whether or not you want Operations Manager to
report the health of your .NET application by the frequency of
performance problems. Select this checkbox to enable rules
to collect Performance alerts, or deselect to disable the
collection rules [default = not selected].
- Connectivity: Select this
checkbox to enable rules to collect Connectivity alerts, or
deselect to disable the collection rules [default = selected].
- Security: Select this checkbox
to enable rules to collect Security alerts, or deselect to disable
the collection rules [default = selected].
Monitors
To Add or Edit Transaction Usage
Monitors: Select either Add
or Edit.
The
Transaction Usage Monitors are available when adding monitoring for
web page, web service or custom function transactions.
| Select the monitor type from the list
Select from the following list of available monitor types:
- The Average Execution Time exceeds
threshold: The instance state becomes unhealthy if the
average request time per predefined escalation time period exceeds
an escalation threshold. The alert details break down the execution
time by percentage spent in various types of resource calls and in
the internal code execution. Excessively long SQL, Oracle, ODBC,
DB2 or OLEDB calls may be due to either a problem with the database
server or with the structure and complexity of the database query.
Long file I/O times may be due to problems with the file server.
Web Services performance issues may occur because the web service
or the server it resides on is down or there is a problem in the
Web Service code. Long internal execution times for applications
may result from a complex or inefficient code. [default = 5000
ms]
- The Number of Calls/sec exceeds
threshold: The instance state becomes unhealthy if the total
number of calls per predefined escalation time period exceeds an
escalation threshold. The total number of calls each second that
are being processed by .NET applications configured for operations
monitoring. This counter is incremented when the call triggers an
entrypoint configured for the process. This counter shows number of
requests (for example to web pages) that have a duration greater
than the Application Alerting Threshold. The alert details break
down the execution time by percentage spent in various types of
resource calls and in the internal code execution. Excessively long
SQL, Oracle, ODBC, DB2 or OLEDB calls may be due to either a
problem with the database server or with the structure and
complexity of the database query. Long file I/O times may be due to
problems with the file server. Web Services performance issues may
occur because the web service or the server it resides on is down
or there is a problem in the Web Service code. Long internal
execution times for applications may result from a complex or
inefficient code. Application performance alerts are generated when
the number of monitored requests that exceed the configured
Alerting Threshold more than configured monitor Threshold. I don't
understand what the part in yellow means - Typical application
performance degradation could be due to a long database call, long
web service call, slow .NET Remoting call or COM+ call, or
inefficient application code. [default = 15 requests/sec]
- The % Exception Events/sec exceeds
threshold: The instance state becomes unhealthy if the total
number of exception events per predefined escalation time period
exceeds an escalation threshold. Application availability alerts
are generated when the number of exception events exceeds the
configured monitor threshold. The alert details break down the
execution time by percentage spent in various types of resource
calls and in the internal code execution. Excessively long SQL,
Oracle, ODBC, DB2 or OLEDB calls may be due to either a problem
with the database server or with the structure and complexity of
the database query. Long file I/O times may be due to problems with
the file server. Web Services performance issues may occur because
the web service or the server it resides on is down or there is a
problem in the Web Service code. Long internal execution times for
applications may result from a complex or inefficient code.
Application availability alerts are generated when the number of
exception events exceeds the configured monitor threshold. Typical
application performance degradation could be due to a long database
call, long web service call, slow .NET Remoting call or COM+ call,
or inefficient application code. [default = 5 percent]
- The % Performance Events/sec exceeds
threshold: The instance state becomes unhealthy if the total
number of performance events per predefined escalation time period
exceeds an escalation threshold. Application performance alerts are
generated when the number of performance events exceeds the
configured monitor threshold. The alert details break down the
execution time by percentage spent in various types of resource
calls and in the internal code execution. Excessively long SQL,
Oracle, ODBC, DB2 or OLEDB calls may be due to either a problem
with the database server or with the structure and complexity of
the database query. Long file I/O times may be due to problems with
the file server. Web Services performance issues may occur because
the web service or the server it resides on is down or there is a
problem in the Web Service code. Long internal execution times for
applications may result from a complex or inefficient code.
Application performance alerts are generated when the number of
performance events exceeds the configured monitor threshold.
Typical application performance degradation could be due to a long
database call, long web service call, slow .NET Remoting call or
COM+ call, or inefficient application code.
The
"% Performance Events/sec Exceeds Threshold" monitor is not
available when adding a custom function transaction for monitoring.
This is because these are resource calls, and therefore do not have
entrypoints from which execution time can be measured.
[default = 10 percent]
Monitor properties (for both Add and Edit)
- Monitor Settings: The read-only
name of the selected monitor
- Specify threshold value to
match:
- Threshold: Number percent. This number indicates how many performance or
exception events (as a percentage of all monitored requests) can
occur per interval before affecting the health state. Available
only for '% Performance Event' [default = 10 percent] and '%
Exception Event' monitors [default = 5 percent].
- Threshold: Number milliseconds. This number indicates the most number of
milliseconds the average request time can last per interval before
affecting the health state. Available only for 'The Average
Execution Time' monitor. [default = 5000 ms]
- Threshold: Number calls/sec. This number indicates the maximum monitored calls
that can be made per interval before affecting the health
state. Available only for 'The Number of Calls/sec'
monitor. [default = 15 calls/sec]
- Specify Health State:
Health State: Select whether the
monitor will go to a Warning or Error health state when the
specified threshold is met for the specified interval [default =
Error].
- Specify the interval:
Interval number Seconds/Minutes/Hours/Days. This number indicates the frequency with which the
Warning and Error thresholds will be checked. For example, if
the Warning threshold is 5, then a state change will take place
if 5 events occur within the interval. It also indicates the
frequency of the Monitor Rule check [default = 5 minutes].
- Alert Properties: The alert
properties are displayed when an alert is generated in response to
the monitor changing state. The properties include: Alert Name (Provide a unique, descriptive name
for the alert to be generated), and Alert
Description (Provide a description of the possible causes
of, and resolutions to, this alert). The alert description can
contain any number of parameters formatted as %ParameterName%, that
will be replaced with actual values when alert is generated.
Possible parameters include: %Threshold%, %InstanceName%, %Value%.
The alert name can not contain parameters.
- Automatically resolve the alert when
the monitor returns to a healthy state: Select this checkbox
to have the MP automatically change alert resolution state to
'Closed' when the monitor returns to a healthy state
[default = selected].
|
|
"Authoring View"
"Groups"
"AVIcode .NET Application
Monitoring"
"Monitoring
Agent State" notifying that IIS must be restarted in order to
monitoring to actually begin. 
"Monitoring View"
"Authoring View"', right click
the 
"Management Pack Templates" folder
and select 'Add Monitoring Wizard.' This action will open an
installation wizard which will guide you through the activation
process.
Enterprise .NET Executable
Application
Enterprise .NET Windows
Service
Enterprise ASP.NET Application:
This tells the wizard that you will be selecting your Enterprise
ASP.NET Application from a list of all Enterprise ASP.NET
Applications installed within the Operations Manager management
group.