[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[[["\u003cp\u003eThe API Monitoring Investigate view in Apigee and Apigee hybrid provides pivot tables of metrics and attributes for all API traffic, allowing users to compare activity across different metrics.\u003c/p\u003e\n"],["\u003cp\u003eBy default, the Investigate view displays three tables: Fault Code by Time, Fault Code by Status Code, and Fault Source by Proxy, but users can select other tables from the Graphs menu.\u003c/p\u003e\n"],["\u003cp\u003eEach cell in a table represents the number of responses for a specific data subset, such as the number of responses with a particular fault code within a specific time frame.\u003c/p\u003e\n"],["\u003cp\u003eUsers can filter the data to exclude successful requests (2xx status codes) to focus on unsuccessful requests, by toggling the "Show 2xx Status Code" button.\u003c/p\u003e\n"],["\u003cp\u003eClicking on a cell in the Investigate view reveals the distribution of data within that cell, broken down by various attributes like fault code or status code, which helps diagnose API issues.\u003c/p\u003e\n"]]],[],null,["# Using the Investigate view\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n\u003cbr /\u003e\n\nThe API Monitoring Investigate view displays\npivot tables of metrics and\nattributes for all API traffic, to help you compare activity for different metrics.\n\nTo access the Investigate view, follow the steps in\n[Accessing API Monitoring](/apigee/docs/api-monitoring#accessing_api_monitoring) and\nselect **Investigate**. \n\nThe figure below shows the UI with **Investigate** selected. \n\nBy default, the Investigate view displays three tables:\n\n- Fault Code by Time\n- Fault Code by Status Code\n- Fault Source by Proxy\n\nAs in the [Timeline view](/apigee/docs/api-monitoring/timeline#timeline),\nyou can select any combination\nof tables from the **Graphs** menu to display. All other\n[graph options](/apigee/docs/api-monitoring/timeline#graph_options_for_all_views)\nare the same as in the Timeline view.\n\nEach cell in a table shows the number of responses\nfor a subset of the data. As an example, take a look at\nthe first three columns of the **Fault Code by Time** table.\n\nThe first cell in row 1 shows the number of responses (`444`) with fault code\n`steps.json2xml.SourceUnavailable` that were returned from\n`18:18 - 18:24`, on the selected date.\n\nThe first cell in row 2 shows the numbers of responses (`64`)\nduring the same time\ninterval for which the fault code was not set for some reason.\n\nTo learn about this particular fault code, see\n[JSON to XML policy runtime error troubleshooting](/apigee/docs/api-platform/troubleshoot/policies/runtime/jsontoxml-runtime-errors).\n\n### 2xx status codes\n\nRequests that return a 2xx status code were\nsuccessfully received and understood. Normally, most requests will return a 2xx\nstatus code. If you\nare primarily interested in viewing data for unsuccessful requests,\nyou might want to restrict the displayed data to requests with\nstatus codes other than 2xx, to make the data easier to interpret.\nTo do so, toggle the **Show 2xx Status Code**\nbutton, at the top-right of the Investigate view, to the left (off) position.\n\nWith this setting, the Investigate view only displays data from\nrequests with response codes different from 2xx.\n\n### Viewing the distribution of cell data\n\nYou can get a more granular view of the data for an individual table cell\nby clicking the\ncell. This displays the distribution of the cell data by several\ndifferent attributes.\n\nTo see an example of this,\nfirst select **Region** in the **Graphs** menu to display\nthe table shown below.\n\nIn the data for this example, there is just one region, `us-central1`.\nIf there were data for other regions, you would see additional rows in the table.\n\nNow, click the first cell in the table.\n\nThis displays several tables in the right-hand pane of the Investigate\nview. The first table is shown below.\n\nThe top of the pane displays the conditions that specify the cell data, in this\ncase the region and time interval.\n\nBelow that, the table \"Distribution by Fault Code\" displays the number of responses\nfor each fault code in the data. In this example, there are just two fault code\nvalues:\n\nThe counts for the fault codes add up to `496`, the total count in the\ncell.\n| **Note:** If you select a table cell in the main section whose attribute is `not set`, the right-hand pane displays data for all cells in the column (or row if the table is pivoted) for the selected cell. In that case, the sum of the values in a distribution table does not necessarily equal the value in the selected cell.\n\nAs another example, scroll down in the right-hand pane until you\nreach the table labeled \"Distribution by Status Code,\" as shown below.\n\nIn this case, there are two status codes in the data:\n\n- `500`: `432`\n- `200`: `64`\n\nAgain, the counts add up to `496`.\n\nUsing the Investigate view to diagnose an issue\n-----------------------------------------------\n\nYou can use the Investigate view to diagnose API issues\nFor example, suppose you receive an alert that indicates that the 5xx error\nrate exceeds the specified threshold. To investigate this issue, you might\nperform the following tasks in the Investigate view:\n\n- View the **FAULT CODE BY TIME** table to view the fault code activity over the last hour.\n- 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.\n- View the **FAULT CODE BY PROXY** matrix to identify the API proxies that are triggering the fault codes identified in the previous step.\n- [Set up an alert](/apigee/docs/api-monitoring/alerts-notifications) to further assist you with diagnosing the issue."]]
