Inspecting failed runtime requests

Edit online

Procedure

  1. In the Runtime events section, click the client request for which you want to inspect the trace details.
    The Trace API page refreshes and populates data in the Policies applied and Event tracer details sections. By default, the Event tracer details section displays the General Information, API request and response, and Server logs sections. Under the API request and response section, you have the following subsections.
    • Request sent by client. This subsection displays the request headers and request body that is sent by the client to webMethods API Gateway.
    • Response sent to client. This subsection displays the response headers and response body that is sent to the client from webMethods API Gateway.
    • Request sent to native service. This subsection displays the request headers and request body that is sent to the native API from webMethods API Gateway.
    • Response sent by native service. This subsection displays the response headers and response body that is sent by the native API to webMethods API Gateway.
    Note: If the request and response body has streaming content, the tracer does not capture the streaming content even if you enable the tracer.
  2. In the Policies applied section, click the stage name that is highlighted in red for which you want to inspect the trace details.
    The Trace API page refreshes the Event tracer details section with the stage_ name stage execution status section. The Trace API page also displays the status and response time of the stage and policies that failed during API invocation.
    Note: In the Policies applied section, if no policies in a stage are enforced during the invocation then that stage is disabled. In this use case, the Response Processing stage is disabled and it is not enforced as the API invocation fails in the Routing stage. The Error Handling stage was enforced to handle the Routing stage failure.
  3. In the Policies applied section, click the policy name request that is highlighted in red for which you want to inspect the trace details.
    The Trace API page refreshes the Event tracer details sections with the policy_name policy config/input/output section that displays the configuration details. The Trace API page also displays values that are passed during the enforcement of that policy, transformation conditions, and payloads. It also highlights the exact location where the policy invocation failed along with the failure reason.
    Note: The template of the policy_name policy config/input/output section varies based on the policy.