IBM DataPower Operations Dashboard v1.0.9.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

When you click a transaction’s ID in the transactions list, DPOD loads the full details of the transaction into the information window.

This view provides a plethora of information about the single transaction in the following widgets.

Transaction Widget

The widget at the top of the window displays various details about the transaction, sc time, status, device, domain, service, operation and Client IP.

This information is identical to the information displayed for the transaction in the Transactions table.

Transaction Analysis Widget

Error analysis

(For transactions in Error status only). 

These are 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 a description of 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.
 

DPOD Administrators can also add error analysis descriptions.

Elapsed Time 

A breakdown of the transaction’s elapsed time between network, monitored device and Service Provider.
This analysis lets you view latency data pertaining to the transaction, and potentially identify network congestion or issues.

This data is only available for successful transactions.

Payload Size

Displays the request and response size.

Memory

Memory consumption graphs for the request and response parts of the transaction, across the transaction lifetime and state changes.

The memory graph is designed to display the differential memory consumption between processing policy actions in a processing rule.

The purpose is to assist the user in troubleshooting high memory consumption by one or more processing actions (for example when using inefficient XSLT).

The graph is built based on the DataPower “memory-report” records.

In some cases the memory value reported at the beginning of a transaction is higher than the following memory report leading to a negative value.

To investigate the service’s total memory usage please navigate to Dashboards -> Resources -> Service Memory.

The memory graph display the differential memory value in KB.

Policy Latency Graph

Green nodes represent the policies and their latency, hover over the latency node to view the policy type.
Blue nodes represent the API Framework latency.

Raw Messages Tab

The raw messages tab is identical to the raw messages tab in the DataPower transaction page

Payload Tab

The payload tab is identical to the payload tab in the DataPower transaction page

Extended Latency Tab

The extended latency tab is identical to the extended latency tab in the DataPower transaction page

Side Calls

The side calls tab shows both API-C internal side calls (such as calls to API-C Analytics) and side calls that were made by user policies.


  • No labels