Action: Throttling Traffic Optimization

Note:
Dependency requirement: A policy that includes this action must also include the Identify Consumer action if the Limit Traffic for Applications option is selected.

This action limits the number of service invocations allowed during a specified time interval, and sends alerts to a specified destination when the performance conditions are violated.

Reasons for limiting the service invocation traffic include:

To avoid overloading the back-end services and their infrastructure.

To limit specific consumers in terms of resource usage (that is, you can use the Monitor Service Level Agreement (SLA) action in addition to Throttling Traffic Optimization).

To shield vulnerable servers, services, and even specific operations.

For service consumption metering (billable pay-per-use services).

To set the Throttling Traffic Optimization action parameters

1. In the CloudStreams Governance view, click the policy name.

2. In the policy editor on the right side of the page, double-click Throttling Traffic Optimization in the Applied Actions list, and set the following action parameters.

Soft Limit

Optional. Specifies the maximum number of invocations allowed per Interval before issuing an alert. Reaching the soft limit will not affect further processing of requests (until the Hard Limit is reached).

Note:
The limit is reached when the total number of invocations coming from all the consumer applications (specified in the Limit Traffic for Applications field) reaches the limit.

Hard Limit

Required. Specifies the maximum number of invocations allowed per Interval before stopping the processing of further requests and issuing an alert. Typically, this limit should be higher than the soft limit.

Note:
The limit is reached when the total number of invocations coming from all the consumer applications (specified in the Limit Traffic for Applications field) reaches the limit.

Alert Interval

Specifies the amount of time for the soft limit and hard limit to be reached.

Alert Frequency

Specifies how frequently to issue alerts.

Every Time: Issue an alert every time one of the specified conditions is violated.

Only Once: Issue an alert only the first time one of the specified conditions is violated.

Alert Message For Soft Limit

Optional. Specify a text message to include in the soft limit alert.

Alert Message For Hard Limit

Optional. Specify a text message to include in the hard limit alert.

Send Data To

By default, this action logs the alerts to the CloudStreams Analytics database.

Note:
Ensure that you select the Database Publishing option in Integration Server Administrator (go to Solutions > CloudStreams > Administration > Database), as described the section Setting the Database Options for Publishing Performance Metrics and Events in the document Administering webMethods CloudStreams.

Metrics Collection Level

The run-time performance metrics for a virtual service (which is invoked only in the inbound run-time scenario), are collected at the service level. That is, the metrics for all invocations of a single virtual services are aggregated together during your specified metrics publishing interval and then published.

In contrast, the metrics for a connector virtual service (which is invoked only in the outbound run-time scenario) can be collected at two different levels of metric collection:

Cloud Connector Service: Remember that a single connector virtual service can be used by multiple cloud connector services. Select this option if you want to collect the metrics for the connector virtual service broken down by each separate cloud connector service that uses it. For example, if a connector virtual services is used by three cloud connector services, then this option will collect the metrics of that service separately, broken down by each of the three cloud connector services that use it.

Connector Virtual Service (default): Select this option if you want to aggregate all the metrics for a single connector virtual service, even if it is used by multiple cloud connector services. For example, if a connector virtual service is used by three cloud connector services, then this option will collect the combined metrics for the connector virtual service by all three of the cloud connector services that use it.

Limit Traffic For Applications

Specifies the consumer application(s) that this action applies to. To specify multiple consumer applications, use the plus button to add rows.

Alert Email

Right-click the action name and click Add Alert Email if you want to send the monitoring alerts to an email address you specify in the Email ID field. You can select Add Alert Email multiple times to add multiple email addresses.

Note:
Ensure that you set the email options in Integration Server Administrator (go to Solutions > CloudStreams > Administration > Email), as described in Setting the Email Options for Logging Payloads and Sending Performance Monitoring Alerts in the document Administering webMethods CloudStreams.