Specifications

Alternate Rulesets
176 BTStudio Administration Guide
Failure Code Code Message
410 HTTP_STATUS_GONE
411 HTTP_STATUS_LENGTH_REQUIRED
412 HTTP_STATUS_PRECOND_FAILED
413 HTTP_STATUS_REQUEST_TOO_LARGE
414 HTTP_STATUS_URL_TOO_LONG
415 HTTP_STATUS_UNSUPPORTED_MEDIA
500 HTTP_STATUS_RETRY_WITH
501 HTTP_STATUS_NOT_SUPPORTED
502 HTTP_STATUS_BAD_GATEWAY
503 HTTP_STATUS_SERVICE_UNAVAIL
504 HTTP_STATUS_GATEWAY_TIMEOUT
505 HTTP_STATUS_VERSION_NOT_SUP
Alternate Rulesets
Alternate rule sets allow you to monitor an application using two or more
different rule sets (a primary rule set and one or more alternate rule sets)
simultaneously. The primary rule set provides the transaction definitions to
monitor application response time from one point of view, and the alternate
rule sets provide transaction definitions to monitor response time from other
perspectives.
Application Response independently analyzes an application’s activity for
transactions using each alternate rule set defined. However, the transactions
recognized under each alternate definition (and their corresponding response
information) are recorded under the same overall application definition. In
effect, this allows you to "double-count" activity, including response time for a
particular transaction in multiple response time calculations.
Note: You cannot nest alternate ruleset constructs. All transaction definitions
that occur outside the scope of an alternate ruleset construct belong to the
primary rule set.
Syntax
alternate ruleset
{
transaction transaction- name1