Using the Investigate view

The API Monitoring Investigate view displays pivot tables of metrics and attributes for all API traffic, to help you compare activity for different metrics.

To access the Investigate view, follow the steps in Accessing API Monitoring and select Investigate.

Select investigate view.

The figure below shows the UI with Investigate selected.

API Monitoring investigate view

The options in the Investigate view are the same as in the Timeline view, but the graphs displayed are different. You can select any combination of the graphs in the Graphs drop-down menu, as shown below.

Select investigate graphs.

When you select graphs, they are displayed according to the order you selected them, starting with the most recent.

The first graph displayed above, Fault Code by Time, shows the numbers of responses with a given fault code over time. For example, in the portion of the graph shown below,

Fault code by time graph.

there are two rows. The first row shows the numbers of responses with fault code steps.json2xml.SourceUnavailable in each time interval. The second row shows the numbers of responses in which the fault code is not set for some reason.

For example, in the interval from 18:18 - 18:24, there were 444 responses with fault code steps.json2xml.SourceUnavailable.

To learn about this particular fault code, see JSON to XML policy runtime error troubleshooting

For more information about fault codes in general, see Introduction to Policy Playbooks.

Using the Investigate view to diagnose an issue

You can use the Investigate view to diagnose API issues For example, suppose you receive an alert that indicates that the 5xx error rate exceeds the specified threshold. To investigate this issue, you might perform the following tasks in the Investigate view:

  1. View the FAULT CODE BY TIME table to view the fault code activity over the last hour.
  2. View the FAULT CODE BY STATUS CODE table to identify specific HTTP status codes associated with the fault codes whose counts have increased over the last hour, as identified in the previous step.
  3. View the FAULT CODE BY PROXY matrix to identify the API proxies that are triggering the fault codes identified in the previous step.
  4. Set up an alert to further assist with diagnosing the issue.