The Investigate view of the API Monitoring User Interface (UI) enables you to view pivot tables of metrics and attributes for all API traffic, and compare activity for different metrics to investigate and diagnose issues.
To acess the Investigate view, follow the steps in Accessing the API Monitoring UI and select Investigate.
The figure below shows the UI with Investigate selected.
The options in the Investigate view are the same as in the Timeline view, but the graphs displayed are different. You can choose the graphs in the Graphs drop-down menu as shown below.
In the example above, the following graphs are displayed:
- Fault Code
- Fault Code by Status Code
- Fault Source by Proxy
Note: In the picture of the Graphs menu above, Fault Code by Status Code and Fault Code by Proxy don't appear because they are too far down the list.
You can select any combination of the graphs in the list. When you select graphs, they are displayed according to the order you selected them, starting with the most recent.
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:
- View the FAULT CODE BY TIME table to view the fault code activity over the last hour.
- 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.
- View the FAULT CODE BY PROXY matrix to identify the API proxies that are triggering the fault codes identified in the previous step.
- Set up an alert to further assist with diagnosing the issue.