Host Throttling
  • 25 Nov 2021
  • 2 Minutos para leer
  • Oscuro
    Ligero
  • PDF

Host Throttling

  • Oscuro
    Ligero
  • PDF

There is no Spanish content available for this article, You are viewing the fallback version (English).

In BizTalk, you might sometimes see that the performance of the server is going down or being slow. It might be that BizTalk is in a throttling situation. The purpose of BizTalk host throttling monitoring is to notify the customers if there is any throttling happening in their environment.

Setting up monitoring for Host Throttling

  1. Log in to the BizTalk360 application
  2. Click 'Monitoring' in the navigation panel
  3. Click the expand button against the 'Manage Mapping' tab and select 'BizTalk Environment'
  4. Select the Alarm name (see Manage Alarms) from the drop-down for which you would like to associate the alerts
  5. Select the 'Host Throttling' tab. This will list the hosts that are available in the BizTalk environment
  6. Let’s say, we want to monitor the BizTalkServerApplication host. Select the BizTalkServerApplication checkbox and click 'Enable monitoring'

By enabling monitoring, BizTalk360 will automatically start monitoring the host. The product will automatically collect the data and display the status (as Healthy or Error)

9. Click the 'Edit' button to open the Throttling Monitoring Rules blade window and configure the threshold alert for publishing and delivery throttling

10.Click 'Save' Configuration to monitor the host throttling

The configured host will get displayed in the host throttling tab

From the Platform Health alarm, the BizTalkServerApplication Host needs to be monitored for Throttling. In the case of Publish Throttling, a Warning should be sent in case of Rate Throttling or Process Memory Throttling. In case of Delivery Throttling, a Warning should be sent, when any throttling persists for more than 60 seconds.

An in-depth look at throttling monitoring rules configuration page

In this section, we will get deep knowledge about every configuration and functionality of publishing and delivery throttling. The first step in host throttling is to create an alarm and map the alarm with the host available in the environment. Click here to understand the process of creating an alarm.

Let's say, the administrator should get notified with a warning for publishing throttling if the rate throttling or the database session throttling persists for more than 60 seconds.
In the same way, the Administrator should get notified with error information when Thread Count or User Override for Delivery Throttling persists for more than 2 minutes.

  1. Publish throttling - This section helps you to configure the threshold alert for Publish Host Throttling. In this case, you can configure the Throttling monitoring parameters based on the scenario mentioned above. This section has the following parameters:
  • Threshold Type
  • Throttling Type
  • Duration
  1. Delivery throttling - This section helps you to configure the threshold alert for Delivery Host Throttling. In this case, you can configure the Throttling monitoring parameters based on the scenario mentioned above. This section has the following parameters:
  • Threshold Type
  • Throttling Type
  • Duration
  1. Time Units - Units to find out how long it may take before thresholds are violated
  2. Add Condition - Click this button to add another condition to your host throttling rule
  3. Save Configurations - Helps you save the configured conditions to your host throttling monitoring rule

6. Close - Close the host throttling monitoring rules screen


Editing the host throttling rule

BizTalk360 allows the user to modify the configured monitoring rules. You can change the throttling conditions associated with that host. For example, the user wants to add a sub-condition to the existing rule, in that case, follow the below steps:

  1. Click the 'Edit' button on the grid for the host which you wish to edit
  2. Throttling Monitoring Rules blade window will be opened
  3. Click the '+' icon and add the sub-condition with the help of the operators
  4. Click 'Save' configurations to save the changes


5. Click the eye icon to view the updated sub-condition result





¿Te ha sido útil este artículo?

What's Next