Specifications

How Transaction Limits Work
[
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
# ServerName != "No-Server"
]
When an application rule set includes any transaction limit or constraint,
Application Response ignores the default constraints and applies the defined
limit or constraint when monitoring transactions. If the application does not
have associated server activity, the response path name on reports shows
"No-Server" instead of a server name, similar to the following:
Client Module An application
name name path
yellow- Outlook- Read-No-Server- AP
Application No server
name activity
Other Transaction Limits and Constraints
In addition to ElapsedTime and ReportedTime limits for applications and
transactions, you can set other types of limits. Use these constraints in the
same manner as ElapsedTime and ReportTime limits. Constraints defined for
BT Language Reference 211