[[["わかりやすい","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-08-18 UTC。"],[[["\u003cp\u003eApigee and Apigee hybrid users can utilize data visualization as a powerful tool for API troubleshooting.\u003c/p\u003e\n"],["\u003cp\u003ePotential causes of slow API performance can stem from issues with a specific app, network problems affecting multiple users, or problems within Apigee itself, including newly added or updated policies.\u003c/p\u003e\n"],["\u003cp\u003eComparing average response times of different APIs can quickly identify underperforming APIs.\u003c/p\u003e\n"],["\u003cp\u003eCustom reports in Apigee allow for the visualization of specific metrics, such as maximum latency time, by app and resource to pinpoint performance bottlenecks.\u003c/p\u003e\n"],["\u003cp\u003eDrilling down on the worst performing API and adding dimensions like Developer App or Developer allows for further analysis to see which apps or developers are most impacted.\u003c/p\u003e\n"]]],[],null,["*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\nData visualization is an important **troubleshooting** tool. Apigee is always collecting and analyzing data for your APIs, and visualization is the most\npowerful way to unlock, compare, contrast, and assess that data.\n\nSo, let's say you've been hearing from customers (perhaps via support calls, social media\nsites, or user forums) that one of your APIs is slow. Visualization can help. Where do you\nbegin?\n\nConsider and test for possible\ncauses\n\nPossible causes might include:\n\n- If the slowness being seen by just one app or is it from multiple apps? If one app, then it might be a problem with the app.\n- If it being seen by multiple users across multiple apps and users seem to be in the same geo location, then it could be a network issue\n- If you're not seeing either of these issue, it could be an issue with Apigee. If you recently added or updated a policy. It could be configured incorrectly.\n- If the total response time is being reported as high, but the average endpoint response time has not changed then it might be an Apigee issue. If the average endpoint response time is also high then it could be an issue in the network between Apigee and the target server, or an internal application server.\n\nVisualize which API is slow\n\nTo discover which API is underperforming, one approach is to compare the average response\ntimes of all your APIs to see if one of them is out of line.\n\n1. Select API Proxies from the APIs menu.\n2. In the Performance section of the API Proxies page, select Average Response Time from the Performance menu.\n3. Select a range of dates to evaluate.\n4. Select which APIs you wish to evaluate.\n\nIn the plot, look for sudden spikes or gradual increases in response time.\n\nVisualize with a custom report\n\nIf you suspect which API is causing a problem, you can create a custom report that includes\ncharts and plots comparing specific metrics that you select. For example, you can visualize the\nmaximum latency time by app and resource.\n\nTo visualize with a custom report:\n\n1. Open the [Apigee UI in Cloud console](https://console.cloud.google.com/apigee).\n2. Select **Analytics \\\u003e Custom reports**.\n3. Click the **Reports** tab.\n4. Click **Create \\\u003e Custom Report**.\n5. Fill out the Custom Report basics.\n6. To add a metric, click **+** , select **Total Response Time** metric and **Max** as the aggregate function, and click **Add**.\n7. To add dimensions, click **+** , select **Proxy** and **Request Path** , and click **Add**.\n8. Click **Create**.\n\nAnalyze the resulting report\n\nThe new latency report will show you the response times by API and then by each resource\nwithin an API. By combining this information with what you know about your network architecture,\nyou can quickly find issues that may be related to your infrastructure.\n\nDrill down\n\nYou can drill down on the worst performing API (the one with the highest latency).\n\nAct\n\nNow that you know which resource is performing badly, you can examine your network to see if\nthere's a service issue, or you can add a 3rd dimension like Developer App to see which apps are\nimpacted by this slow resource, or developer to figure out which developers are impacted by the\nslow resource.\n\nAs you can see, Apigee Analytics includes multiple ways to approach a specific problem,\nand visualization plays an important role in any troubleshooting process."]]
