Versions Compared

Key

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


IDG DataPower allows correlation between transactions across domains/ devices. This correlation is defined by means of a global transaction ID.
Examples of extended transactions include:

  • A DMZ DataPower relays a request into the LAN internal DataPower. 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 or across several machines.

...

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

...