Transactions

A transaction is a server side Logical Unit of Work (LUW) that processes a request from a user’s browser. In a web application, the entire process of receiving a single HTTP request and returning a response constitutes a transaction.

Application performance can be evaluated through transaction processing performance. Transaction performance includes information such as response time from transaction start to completion, resource usage, and caller attributes.

Transaction performance can be analyzed based on response time distributions and statistical data.

Transaction tracing

These agent options allow you to trace the execution path of each transaction within an application in detail.

• trace_active_transaction_slow_time Millisecond

  Default value 3000

  Sets the response time threshold for marking a transaction as slow in the Active Transaction Arc Equalizer graph on the dashboard. If a transaction’s response time exceeds this value, it is included in the count of slow active transactions.

• trace_active_transaction_very_slow_time Millisecond

  Default value 8000

  Sets the response time threshold for marking a transaction as very slow in the Active Transaction Arc Equalizer graph on the dashboard. If a transaction’s response time exceeds this value, it is included in the count of very slow active transactions.

• trace_active_transaction_lost_time Millisecond

  Default value 300000

  Defines the timeout for waiting for a transaction to complete. If a transaction does not finish within 5 minutes, the agent stops collecting information for that transaction. In the transaction trace, this appears as “Lost Connection”.

• prepend_app_pool_name Boolean

  Default value false

  When set to true, the full application name is prefixed to the transaction URL.

• expand_transaction_level Boolean

  Default value false

  When set to true, SQL and HTTP calls that occur outside a transaction are treated as transactions and displayed on the hitmap.

• expand_transaction_basetime Int

  Default value 1000 (1 second) / Minimum value 100 (0.1 second)

  When expand_transaction_level is set to true, only requests whose response time exceeds the specified value are collected. Up to 100 requests per second can be collected.

Exceptional handling

The following options are used to manage and monitor exceptions that occur in applications. You can check the stability of applications by registering business exceptions and collecting related statistics. You can also set whether to ignore specific exceptions or treat them as errors if the HTTP status code is an error. Exception-handled items appear as normal transactions in the Hitmap or Trace analysis window.

• transaction_status_error_enable Boolean

  Default value true

  Determines whether HTTP responses with non-success status codes, such as 401 or 403, are treated as errors.

• status_ignore String

  Specifies HTTP status codes to ignore. Use a comma (,) to separate multiple values.

  whatap.conf

  # example
  status_ignore=408,500

  Tip

  Ignore status error/Hitmap display level: Excludes the INFO (blue)/error statistics.

• status_ignore_set String

  Ignores specific combinations of URL and HTTP status code so they are not treated as errors.

  whatap.conf

  # example
  status_ignore_set=/api/test/timeout/{time}:408,/error:500

  Tip

  Ignore status error set/Hitmap display level: Excludes the INFO (blue)/error statistics.

• 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.

  Tip

  Ignore HTTP status error code/Exclude error statistics

• httpc_status_ignore_set String

  Prevents specific combinations of URL and status code from being treated as errors in HTTP client external calls.

  whatap.conf

  httpc_status_ignore_set=api.example.com:404,payment.service:500
  # If your application calls api.example.com and receives a 404 response, it is not recorded as an error

  Tip

  Ignore HTTP status error code/Exclude error statistics

HTTP transaction tracing

The following agent options trace and record various data related to HTTP requests and responses. This allows you to closely monitor and analyze the HTTP transactions for applications. You can add parameter values ​​to the transaction names or exclude specific URLs or HTTP methods. You can also record transactions in detail, including HTTP headers and parameters.

• profile_http_parameter_keys String

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

• 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.txtof 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

  Outputs the Host information of a transaction. When set to false, only the URI is displayed in the transaction URL. When set to true, the URL is displayed in the /xxx.aaa.com/URL format.

• 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.

• trace_ignore_url_set String

  It sets URLs to exclude from transaction tracing. For multiple values, use comma (,) as the delimiter.

  Note

  The URLs registered through this option are excluded from the Hitmap, Trace analysis, or Transaction information window for collection.

• trace_ignore_url_prefix String

  Set the prefix of URLs to exclude from transaction collection. URLs matching the set prefix are not collected for transaction performance. To set multiple values, use comma (,) as the delimiter.

  Note

  The URLs registered through this option are excluded from the Hitmap, Trace analysis, or Transaction information window for collection.