Skip to main content

Transactions

Transaction means the logical unit of work (LUW) on the server side for processing a user browser request. The process for an individual web service (URL) request is a transaction. A transaction in a web application is the process from receiving an HTTP request for a web service (URL) to returning a response.

The performance of the application can be summarized as the performance of these transactions. Transaction performance includes information such as transaction start-to-end time, response time, resource usage, or attributes of the transaction caller.

Basically, the transaction performance can be analyzed through the response distribution and statistics.

The agent traces the transaction performance and provides the following configurable options.

Transaction Tracing

  • profile_http_header_enabled Boolean

    Default false

    To record HTTP headers in the trace details, set it to true.

  • profile_http_parameter_enabled Boolean

    Default false

    To record HTTP parameters in the trace details, set this to true. Parameters can be viewed by entering a separate security key.

    Note

    Set the security key to 6 digits in '%PROGRAMFILES%'\WhaTap .NET\paramkey.txt of the WAS server. If paramkey.txt does not exist, it is automatically generated as a random value.

  • profile_http_parameter_url_prefix String

    It is used to define the prefix of URL to record HTTP parameters in the trace details.

  • profile_http_host_enabled Boolean

    Default false

    The host of a transaction is output. If the value is false, only the URI is recorded in the URL of a transaction. If the value is true, output has the format of /xxx.aaa.com/URL.

  • profile_http_body_url_prefix String

    It is used to define the prefix of the target URL to record the HTTP body information in the trace history.

  • biz_exceptions String

    Default Empty

    Set a specific error or exception as business exception. It is not recorded as an error in the hitmap but collected in the statistics. It is applied the same as the error class name that is collected. Multiple items can be registered using comma (,) as the delimiter.

  • ignore_exceptions String

    Default NONE

    The errors of the registered exceptions are ignored.

    In case of an exception, if the custom exception class has not been defined, it is collected with exception by default. To exclude specific exceptions, define the custom exception class and then set the name of exception.

  • trace_normalize_enabled Boolean

    Default true

    It enables the function to parse and normalize transaction URLs.

    Note

    If the value is changed to false, it disables the path parameter parsing. In this case, it is recommended to temporarily use the setting only for debugging purposes because the statistical data is less meaningful.

  • trace_normalize_urls String

    Default NONE

    Set transaction URL patterns to normalize. It deletes the path parameter after parsing the call URL patterns.

    Note

    For example, if declared as /a/{v}/b, a/123/b is replaced by a/{v}/b. For multiple values, use comma (,) as the delimiter. A complement is required after arranging substitution patterns.

  • transaction_status_error_enable Boolean

    Default true

    If an HTTP status code that is not a normal response such as HTTP 401 or 403, is returned, set whether or not to handle it as an error.

  • status_ignore String

    You can set the HTTP status codes to ignore. For multiple values, use comma (,) as the delimiter.

    whatap.conf
    # example
    status_ignore=408,500
  • status_ignore_set String

    whatap.error.STATUS_ERROR is ignored. For multiple values, use comma (,) as the delimiter.

    whatap.conf
    # example
    status_ignore_set=/api/test/timeout/{time}:408,/api/test/timeout:200,/error:500
  • httpc_status_error_enable Boolean

    Default true

    Set whether or not to collect when the HTTP status code is an error. It includes client error responses (400 or higher) and server error responses (500 or higher).

    Note

    For more information about the HTTP status codes, see the following.

  • httpc_status_ignore String

    If the HTTP status code is an error (HTTPC_ERROR), it can be ignored. When listing multiple values, use comma (,) as the delimiter.

  • httpc_status_ignore_set String

    whatap.error.HTTPC_ERROR is ignored. For multiple values, use comma (,) as the delimiter.

    Note

    Set it as httpc_status_ignore_set=/a/b/c:400,/a/ab/c:404. In Statistics/Error Analysis, enter the value for HTTPC_URL.

  • profile_http_parameter_keys String

    Only the parameters corresponding to the set key are recorded. For multiple values, use comma (,) as the delimiter.

  • trace_active_transaction_slow_time Millisecond

    Default 3000

    In the active transaction arc equalizer graph on the dashboard that checks collected data, specify the criteria for the transaction response time that can be recorded as a slow section. If the transaction response time exceeds the set time, the number of slow active transactions is included.

  • trace_active_transaction_very_slow_time Millisecond

    Default 8000

    In the active transaction arc equalizer graph on the dashboard that checks collected data, specify the criteria for the transaction response time that can be recorded as a very slow section. If the transaction response time exceeds the set time, the number of very slow active transactions is included.

  • trace_active_transaction_lost_time Millisecond

    Default 30000

    Timeout waiting for a transaction to end. If a transaction does not end within 5 minutes, no further transaction data is collected. You can see Lost Connection in the transaction trace information.

  • prepend_app_pool_name Boolean

    Default false

    If the option value is set to true, the full name of the application appears before the URL of the transaction.