This action
requires a service restart.Enable [Disable] Orchestrations [Pipelines | Adapters | Maps] Performance Tracing
This task enables/disables orchestrations performance tracing and sets Alerting Threshold for their monitoring. Alerting Thresholds are used by the 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 monitor disposes of the data. Alerting Thresholds are measured in milliseconds, and are set to 15000 ms by default. This action does not require a service restart.
Set Sensitivity Threshold for all Hosts
This task sets a new override value for the sensitivity threshold for all BizTalk hosts (windows services) added for monitoring. This action does not require a service restart.
Pause/Resume Monitoring All Hosts
This action
requires a service restart.
Check BizTalk Server Discovery Account Rights
This task attempts to combine the connection string to the SQL database with the BizTalk metadata, and will fail if there are insufficient rights. If the task fails, the following message will be reported: Action Account Used for BizTalk Discovery does not have sufficient rights to access BizTalk management database. To resolve, please add OpsMgr Health service account to "BizTalk Server Operators Group" or configure Operations Manager Action Account for "BizTalk Server Discovery Account" run as profile and add it to "BizTalk Server Operators Group". This action does not require a service restart.
Enable [Disable] Orchestrations [Pipelines | Adapters | Maps] Performance Tracing
Enable All Exceptions Monitoring
This task enables collecting both critical and handled exceptions in the monitored application.
This action
requires a service restart.
Enable Only Critical Exceptions Monitoring
This task enables collecting only critical exceptions in the monitored application. Intercept defines critical errors as being those that lead to a monitored component's failure.
This action
requires a service restart.
Enable [Disable] Exception Diagnostic Data
This task enables/disables collecting exception diagnostic data in the monitored application. It adds All Namespaces into the list of monitored namespaces in order to collect functional parameters and member variables for custom namespaces in the exception event.
This action
requires a service restart.
Enable [Disable] Performance Diagnostic Data
This task adds All Namespaces to collected information in the monitored application (or disables collecting performance diagnostic data in the monitored application). This option will cause the agent to start monitoring all functions except namespaces, classes and functions that are explicitly excluded from monitoring.
The '[All
Namespaces]' item should be used judiciously as it will increase
the amount of data collected.
This action
requires a service restart.
Pause/Resume Application Monitoring
This option disables [enables] monitoring.
This action
requires a service restart.
Set Alerting Threshold
An SLA threshold is used by the operations monitoring agent to define if an event needs to be reported. The operations monitor detects all requests that exceed this threshold and reports them. If the execution time exceeds the alerting threshold, then the agent collects information about the request and reports it, otherwise the agent disposes the event data. This action does not require a service restart.
Set Sensitivity Threshold
The threshold for the execution time of a call to external resources is called the 'Sensitivity Threshold'. The sensitivity threshold for a resource call should never exceed the alerting threshold of the page or function it was called from. In a staging or test environment, setting the sensitivity threshold to zero will allow Intercept to report performance information on all resource calls, including those that took no time. In a production environment however, you should reduce overhead by eliminating the reporting of resource calls that took a negligible amount of time. This will help to eliminate extraneous information, which is of no interest in the alert.. This action does not require a service restart.
Start/Stop NT Service
This task is used to start or stop monitored BizTalk hosts.
Enable [Disable] Orchestrations Performance Tracing
This task enables/disables orchestrations performance tracing and sets Alerting Threshold for their monitoring. Alerting Thresholds are used by the 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 monitor disposes of the data. Alerting Thresholds are measured in milliseconds, and are set to 15000 ms by default. This action does not require a service restart.
Enable [Disable] Pipelines Performance Tracing
This task enables/disables pipelines performance tracing and sets Alerting Threshold for their monitoring. Alerting Thresholds are used by the 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 monitor disposes of the data. Alerting Thresholds are measured in milliseconds, and are set to 15000 ms by default. This action does not require a service restart.
Enable [Disable] Adapters Performance Tracing
This task enables/disables adapters performance tracing and sets Alerting Threshold for their monitoring. Alerting Thresholds are used by the 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 monitor disposes of the data. Alerting Thresholds are measured in milliseconds, and are set to 15000 ms by default. This action does not require a service restart.
Enable [Disable] Maps Performance Tracing
This task enables/disables maps performance tracing and sets Alerting Threshold for their monitoring. Alerting Thresholds are used by the 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 monitor disposes of the data. Alerting Thresholds are measured in milliseconds, and are set to 15000 ms by default. This action does not require a service restart.
Enable Only Critical Exceptions Monitoring
This task enables collecting only critical exceptions in the monitored application.
This action
requires a service restart.
Enable All Exceptions Monitoring
This task enables collecting both critical and handled exceptions in the monitored application.
This action
requires a service restart.
Enable [Disable] Exception Diagnostic Data
This task enables/disables collecting exception diagnostic data in the monitored application.
This action
requires a service restart.
Enable [Disable] Performance Diagnostic Data
This task adds All Namespaces to collected information in the monitored application (to enable) or disables collecting performance diagnostic data in the monitored application.
This action
requires a service restart.
Additional
configuration options are available through the Intercept
Management Console and through the agent configuration files.
Details are available in the "Intercept
Studio User Manual" .
Last update: Thursday, December 09, 2010 02:06:03 PM