Skip to Content

Request threshold for interesting transactions

The request threshold is a global threshold for the performance of transactions. Requests that take longer than this value are considered for capture. Requests that take less time than this value are not captured, unless the requests are tagged.

Warning

Note

For Diagnostics Agents version 2.6, set global thresholds and custom endpoint thresholds in the BMC Application Management Console. For information, see Configuring-SLA-rules-for-business-transactions.

For a small proof-of-concept environment with the Diagnostics Agent for Java, you can override the global and custom settings in the GUI and maximize the number of "interesting" transactions. If the agent policy parameter mark.all.transactions.interesting is set to true, then all transactions are considered for capture. The Max policy is set this way by default. Do not enable this parameter for medium or large environments because system performance can be adversely affected.

For Diagnostics Agents that are version 2.5.01 or earlier, request thresholds are defined using the recording.regulator parameters in the BMC Application Diagnostics Agent policy file.

recording.regulator.filters parameter

The recording.regulator.filters parameter determines which algorithm is used to determine the threshold for persisting requests. The following values are valid:

  • staticThreshold, the default value, sets the recording filter to use a static threshold.
  • lastSampleWeight sets the recording filter to use a dynamic threshold.

recording.regulator.staticThreshold parameter

This parameter is only used for BMC Application Diagnostics versions 2.5.01 or earlier.

The recording.regulator.staticThreshold parameter sets the global value of a static threshold to determine when an SLA is breached. The value is used for all entry points.

The default value is 2000 ms (2 seconds).

recording.regulator.lastSampleWeight parameters

The recording.regulator.lastSampleWeight parameters are used to calculate the thresholds dynamically and to determine the when to send events. Dynamic thresholds are continuously calculated per entry point. Calculations are based on an approximated average duration of requests made in the specific entry point.

The dynamic threshold is determined by the following algorithms:

new_average = (old_average * (ratio - 1) + sample_duration)/ratio
threshold = average * (1 + excess/100)

You can adjust the ratio and excess  parameters:

  • recording.regulator.lastSampleWeight.ratio
    The weight ratio between the previous average and duration of the last sample.
    A lower ratio gives more weight to the current sample, and causes the average to change faster.
    The default ratio is 1000.
  • recording.regulator.lastSampleWeight.excess
    Excess determines how much higher than the average a request’s duration has to be, in order to record the request. Excess is expressed as a percentage. For example, if the current average is 1000 ms, and the excess is 20 percent, then only requests with a duration of over 1200 ms are recorded.
    The default value is 20 percent.

Related topics

Modifying-an-Agent-policy-file

Persistence-of-tagged-transactions

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC TrueSight App Visibility Manager 2.7