IDG 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.
...
Click the 
 icon to the left of an extended transaction to open a panel with the extended transaction’s correlation Id at the top, and extra information relating the single transactions comprising it:
| Column | Description |
|---|---|
Service Name | The service this transaction ran on. |
Time | Timestamp for the transaction. |
Device Name | The device this transaction ran on |
| Domain | The domain the transaction ran on |
Status | The status for this transaction. The possible values are:
|
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, |
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 |
...