Use the Operational Settings page to enable and disable a proxy service and monitoring for specific proxy services. Similarly, you can specify these same service-specific operational settings on the Operations > Smart Search page, with the following exceptions: you cannot set an aggregation interval or specify an alerting or logging severity level. For more information, see Finding and Updating Operational Settings.
The run-time effects of the service-level settings depend on their corresponding global settings. You must enable both the global and service-level settings for a service to be completely enabled at run time. Additionally, the Service State must also be enabled. See Enabling Global Settings.
You can change and save monitoring configuration settings even if the service will be not be enabled at run time. For example, you can change and save the Aggregation Interval even if Service Monitoring is disabled. In this manner, you can edit settings and later enable them.
The View a Proxy Service page displays the information shown in Table 23-6.
Property
|
Description
|
---|---|
Last Modified By
|
The user who created or edited this service, or imported it into the configuration.
|
Last Modified On
|
The date and time that the user created or edited this service, or imported it into the configuration. Click the date and time link to view the change history of this resource. See
View Change History page.
|
References
|
The number of objects that this service references. If such references exist, click the numeric link to view a list of the objects. See
Viewing References to Resources.
|
Referenced By
|
The number of objects that reference this service. If such references exist, click the numeric link to view a list of the objects. See
Viewing References to Resources.
|
Description
|
A description of the service, if one exists.
|
You must be in an active session to configure proxy service operational settings shown in Table 23-7.
To...
|
Do This...
|
---|---|
Disable State
|
Clear the Enabled check box. When you activate the session, the service stops processing messages.
Disabling a service no longer causes the system to delete all monitoring statistics previously collected for the service.
|
Enable State
|
Select the Enabled check box. When you activate the session, the service resumes processing messages.
|
Disable Monitoring
|
Clear the Enabled check box. When you activate the session, the system stops collecting monitoring statistics for the service, and deletes any statistics collected previously.
|
Enable Monitoring
|
Select the Enabled check box. When you activate the session, the system starts collecting monitoring statistics for the service.
|
Set an Aggregation Interval for a service
|
Select the interval in terms of hours or minutes, then click Update. If your selection for hours exceeds 1, then the default selection for minutes is always zero. However, if your selection for hours is 0 or 1, then you can configure intervals in terms of minutes. See
Setting the Aggregation Interval for a Service.
You can change and save the Aggregation Interval setting whether or not you have enabled monitoring.
To enable monitoring at run time, make sure the Enable Monitoring check box is selected.
|
Disable SLA Alerting
|
Clear the Enabled check box. The system stops evaluating any alert rules configured for the service; therefore, you no longer receive SLA alerts associated with the service.
|
Enable SLA Alerting
|
Select the Enabled check box. From the Enable Alerting at drop-down list, select to restrict SLA alerts to the specified level or above (listed from the most inclusive to the most restrictive level): Normal (default), Warning, Minor, Major, Critical, and Fatal.
Service SLA alerting depends on both the global and service-level monitoring states-both must be enabled for SLA alerting to be enabled at run time. See
Enabling SLA Alerts Globally.
|
Disable Pipeline Alerting
|
Clear the Enabled check box. When you activate the session, the system stops executing pipeline alert actions; therefore, you no longer receive pipeline alerts associated with the service.
|
Enable Pipeline Alerting
|
Select the Enabled check box. From the Enable Alerting at drop-down list, select to restrict pipeline alerts to the specified severity level or above (listed from the most inclusive to the most restrictive level): Normal (default), Warning, Minor, Major, Critical, and Fatal.
|
Disable the report action of a proxy service
|
Clear the Enabled check box next to Message Reporting. When you activate the session, the system stops executing report actions; therefore, you no longer receive message reporting associated with the service.
|
Enable the report action of a proxy service
|
Select the Enabled check box next to Message Reporting.
|
Disable logging output for a pipeline log action
|
Clear the Enabled check box next to Logging. When you activate the session, the system stops executing log actions; therefore, you no longer receive logging output associated with the service.
|
Enable logging output for a pipeline log action
|
Select the Enabled check box next to Logging. From the Enable Logging at drop-down list, select to restrict logging output to the specified level or above (listed from the most inclusive to the most restrictive level): Debug (default), Info, Warning, and Error.
|
Enable run-time tracing for a proxy service
|
Select the Enabled check box next to Tracing. Once you enable tracing, the system logs various details culled from the Message Flow Context and the Message Context. These details include: stage name; pipeline or route node name; and the current Message Context.
|
Disable run-time tracing for a proxy service
|
Clear the Enabled check box next to Tracing.
|