Versions Compared

Key

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

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

...

If you navigate to this page from a transactions list that contains more than one transaction, previous/next buttons will appear to quickly move to the next or previous transaction on that list.

The size of next/previous transactions results can be defined in the System Parameters list.

...

Green nodes represent user policies and their latency, hover over the latency node to view more details.
Blue nodes represent the API Framework latency.
Pre/Post processing polices (DataPower API Gateway only) will appear with a Blue border.
The user can switch between “Primary Policies” and “All Policies”.
For primary policies - all pre policies and post policies are grouped into 2 boxes (pre and post) with the aggregated latency and the number of policies. If the pre or post contains user policies, it will appear with a green border, otherwise blue.

Image Added

Click on a user policy or on a pre/post policy to open the Policy Details Window.Image Removed


Policy Details Window

The top part of the window shows the policy graph, you can focus on any user policy by clicking it.
The middle part shows general details about the policy, such as the policy name, type and the execution time in ms.
The lower part shows a list of side calls made by this policy. and a list of context variables and their values (if a policy variables capture was active during the execution of this transaction)
If a policy variables capture was active, but no data is showing in the "Context variables" table - wait a few seconds and refresh the page, it may take up to 2 minutes for the data to appear.

Keyboard shortcuts - 
Left or Right arrows - Previous / Next policy
Space - Wrap the policy variables values text.
Escape - Close the window.

Raw Messages Tab

This widget lists the raw messages that make up the single transaction viewed (up to 2000 messages). 

Tracking the raw messages making up transactions in error may provide insights into the causes of failures.

Tracking the raw messages making up successful transactions may provide insights into slow components or unnecessary steps.

The information is displayed in a table.

...

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:

  • Request
  • Response
  • Error (if message is an error)
  • Empty (if it is a system message)

...

Object Type

...

The object type associated with this message

...

Object Name

...

...

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 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 the front end, for both the request and response phases. 

Extended Latency Tab

Detailed latency information for both the request and response phases.

Side Calls

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

Image Removed

Correlated Transactions Tab

...

Clicking on the Raw Errors links (appears only if the transaction did have any errors, and only if the user has appropriate permissions) will open a window with the all the transactions' error messages, note that the existence of error messages doesn't necessarily mean that the transaction failed. 

Side Calls Tab

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

Image Added

Payload Tab

When WS-M recording is switched on or Analytics Offload exists, the Payload pane of the table will contain payload information for the messages displayed.
The payload is shown for the front end, for both the request and response phases. 

Headers Tab

When Analytics offloading is enabledheader information is displayed for both the request and response phases.

Extended Latency Tab

Detailed latency information for both the request and response phases.

Raw Messages Tab

This widget lists the raw messages that make up the single transaction viewed (up to 2000 messages). 

Tracking the raw messages making up transactions in error may provide insights into the causes of failures.

Tracking the raw messages making up successful transactions may provide insights into slow components or unnecessary steps.

The information is displayed in a table.


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:

  • Request
  • Response
  • Error (if message is an error)
  • Empty (if it is a system message)

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.

Analytics Offload Tab

When Analytics offloading is enabledboth Analytics data and raw data is displayed.