...
Transaction Analysis Widget
The widget atthe at the top right provides analysis of the transaction in three aspects:
...
(For transactions in Error status only).
These The errors displayed are either network or SSL errors. Transactions that are erroneous as a result of the output policy are not reported here.
If the error is common, DPOD will provide provides a description of alongside the error here. This is especially useful in situations where the raw logs are
hidden on account of security policies, and cannot be viewed by the user.
...
The memory graph is designed to display the differential differences in memory consumption between processing policy actions in a processing rule.
The purpose of this graph is to assist the user in troubleshooting high memory consumption by one or more processing actions (for example when using an inefficient XSLT).
The graph is build based on built using the DataPower “memory-report” records.
In some cases the memory used value reported at the beginning of a transaction is higher than the values following memory report , leading to a negative value in the report.
To investigate the service’s total memory usage please navigate to Dashboards -> Resources -> Service → Resources → Service Memory.
The memory graph display the differential differences in memory value usage values in KB.
Raw Messages Tab
This widget lists the raw messages that make up the single transaction viewed.
Tracking the raw messages for making up transactions in error may provide insights into the causes of failures.
Tracking the raw messages for making up successful transactions may provide insights into slow components or unnecessary steps.
...
| Column | Description |
|---|---|
Category | The message’s category |
Severity | The message’s severity |
Time | The message’s timestamp |
Direction | The message’s direction. This may be:
|
Object Type | The object type associated with this message |
Object Name | The object name associated with this message |
Client IP | The Client IP this message originated from. This may be the actual client, or a load balancer. |
Message Code | The message’s code |
Message | The actual message logged. |
Payload Payload Tab
When WS-M recording is switched on, the Payload pane of the table will contain payload information for the messages displayed.
The payload is shown for both the front end and the back end, for both the request and response phases.
...
| Column | Description |
|---|---|
| Type | The call 's type - such as SQL, LDAP, etc. |
| Direction | request or response |
| Time | When the call was made |
| Elapsed (ms.) | Elapsed time of the call in milliseconds |
| Status | Whether the call was successful or not |
| Details | Extra details about the call, such as the SQL statement, HTTP request URL, etc |
...