This is the default view when you click to open the the Investigate process. It provides details of the transactions in the system, according to the filters set.
Filters
The filters screen the data that is passed at the beginning of the API execution except OAuth, Latency, Response codes and Error messages which are collected at the end of the transaction.
If the API did not finish, the OAuth, Latency, Response codes and Error message will not be collected and will not be displayed in the grid.
Transactions Grid
The following information is available for each transaction:
| Column | Description | ||
|---|---|---|---|
Service API Name | The service the running the transaction. | ||
Operation | The operation type of this transaction (may show the Request URI for Multi-Protocol Gateway services) | ||
API Name | |||
Time | The time this transaction was logged | ||
Device | The device this transaction ran on. | Domain | The domain this transaction ran in |
Catalog Name | The API Catalog Name | ||
| Space Name | The API Space Name | ||
| Operation ID | The invoked operation within the API | ||
| Client ID | The ID of the client that invoked the API | ||
| OAuth Scope | OAuth Scope | ||
Status | The status of the transaction. This may be either OK, ERROR or INPROCESS | ||
Trans IdID | This is the monitored device's transaction idID. | ||
Client IP | The client originating the transaction. This can sometimes be the IP of the load balancer. | ||
| Gl. Trans. ID | The global transaction ID | ||
Elapsed (ms) | The elapsed time of the transaction in milliseconds | ||
Payload | When WS-M recording is on, this column will contain the payload of the transaction. |
Note
IN PROCESS transactions may or may not have completed OK. INPROCESS signifies that DPOD has not found an ‘End transaction’ message in the log for this transaction.