Specifications

How Transaction Limits Work
transaction "Forward"
module "Forward"
{
# Sending a message
event "ComposeForward" Outlook ComposeForwardMessage { }
event "SubmitComplete" Outlook SubmitMessageComplete { }
}
transaction "Read"
module "Read"
{
# Reading a message
event "Selection" Outlook ReadMessage { }
event "ReadComplete" Outlook ReadMessageComplete { }
}
Eliminating Transactions with No Server Activity
A typical transaction involves an action performed at the client, which sends a
request over the network to an application server. If Application Response
does not observe any network activity, it assumes that the application is local
to the client, and so the transaction has no server activity to measure. Many
Application Response customers prefer to omit such information from their
reports, choosing to focus instead on the response time of applications and
transactions that involve measurable amounts of server and network time.
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:
210 BTStudio Administration Guide