Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...


Warning
  • This feature is considered a tech preview feature, and is limited to 50 TPS at most. Do not enable this if transaction rate exceeds this limit.
  • Instead, please consider using Correlated Transactions Tab as a better alternative.


Extended Transactions, which are transactions that span more than one monitored service/domain/device, are being tracked in a non-intrusive way over HTTP protocol. This correlation is defined by means of a global transaction ID.

Examples of extended transactions include:

  • A DMZ DataPower gateway relays a request into the LAN internal DataPowergateway. The request transcends two machines and would have consists of two separate transactions.
    With the Extended Transaction, you can treat this operation as a single one.
  • An extended transaction may span domains inside a single DataPower machine gateway or across several machinesgateways.

The following information is available for each extended transaction:

ColumnDescription

Service Name

The service the extended first transaction ran on

Operation/URI

The operation’s name for this extended first transaction or URI

Time

Timestamp for the extended first transaction.

Device NameThe device this extended first transaction ran on
DomainThe domain this extended first transaction ran on

Status

The status for the extended first transaction. The possible values are

  • OK
  • ERROR

Error Message

When the extended transaction completed in an error state, this column will hold the error message

Client IP

The client IP of the machine (or load balancer) where this transaction started.

StepsIndicates the number of transactions that are part of the extended transaction
Gl. Trans. IDCorrelation ID between transactions across services/domains/devices

Elapsed (ms)

The number of milliseconds the extended transaction spanned.

...

ColumnDescription

Service Name

The service this transaction ran on.

Time

Timestamp for the transaction.

Device Name

The device this transaction ran on

DomainThe domain the transaction ran on

Status

The status for this transaction. The possible values are:

  • OK
  • ERROR

Error Message

If the transaction ended in an error state, this column will hold the error message received. If the error message is too long, it will be abbreviated,
with an ellipsis at the end. Hovering over a abbreviated message will display the full message in a pop-up

Transaction Id

The Transaction id. Click on the transaction id to open a single transaction view for this transaction

Elapsed (ms)

Total elapsed time, the number of milliseconds the transaction took.

Network
Elapsed (ms)
Network elapsed time
Device
Elapsed (ms)
DataPower processing elapsed time
Back-End
Elapsed (ms)
Back-End processing elapsed time

Feature enablement

Currently this feature is disabled for new installations by default. To enable/disable it, please execute the following script: app_logical_tran.sh