Specifications

How Transaction Limits Work
To eliminate these no-server transactions from reports, each default
application rule set begins with the following constraints. In addition, when
you define a new application, these constraints appear at the top of the rule
set.
[
BytesSent > 0
ServerName != "No-Server"
]
The BytesSent constraint instructs Application Response to ignore any
transaction for which no data is sent over the network. In effect, this
eliminates response time information for all transactions that do not involve
significant server time. The ServerName constraint instructs Application
Response to ignore any transaction where the server cannot be identified
(resulting in the server name of No-Server). This constraint ensures that all
No-Server transactions are omitted from eHealth reports.
Including Transactions with No Server Activity
If you want to include information about these transactions (that do not
involve sending data over the network) in eHealth reports, change the
constraints to the following:
[
BytesSent >= 0
# ServerName != "No-Server"
]
This will ensure that Application Response includes response time information
about transactions in eHealth reports, regardless of whether they involve
sending data over the network.
If a Rule Set Does Not Define BytesSent
If an application rule set does not include the [ BytesSent > 0 ] constraint or
any other constraints, Application Response still applies the constraints and
ignores any transaction for which no data is sent over the network. For
example, any application defined prior to eHealth Release 5.6.5 does not
include this constraint.
If you want to include information about these transactions (that do not
involve sending data over the network) in eHealth reports, do either of the
following:

Define any transaction limit for the application rule set.

Edit the default constraints as follows:
[
BytesSent >= 0
BT Language Reference 205