[[["容易理解","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 Proxy Performance dashboard in Apigee and Apigee hybrid allows users to visualize API traffic patterns and the time it takes for API calls to be processed, from receipt to response.\u003c/p\u003e\n"],["\u003cp\u003eThe dashboard includes charts for Average Transactions Per Second (TPS), Total Traffic, Traffic Success/Errors, Average Response Time, Traffic by Proxy, and Average Response Time by Proxy.\u003c/p\u003e\n"],["\u003cp\u003eThe dashboard's metrics, such as Average Response Time, consider the total time it takes for an API call to return, including the time spent within Apigee and at the target system.\u003c/p\u003e\n"],["\u003cp\u003eData displayed on the dashboard may have a delay of up to 10 minutes after API calls are made.\u003c/p\u003e\n"],["\u003cp\u003eThe most relevant average response times are gathered by observing a higher number of requests over a larger period of time.\u003c/p\u003e\n"]]],[],null,["# API Proxy Performance\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\nWhat does this dashboard tell me?\n---------------------------------\n\nThe Proxy Performance dashboard helps you see API proxy traffic patterns and processing times.\nUse is to visualize how much traffic your APIs generate and how long it takes for API calls\nto be processed, from the time they are received by Apigee until they are returned to the\nclient app.\n\n\n| **Note:** **Data delay interval** \n| After API calls are made to proxies, it may take up to **10 minutes** for the data to appear in dashboards, custom reports, and management API calls.\n\n\u003cbr /\u003e\n\nThe API Proxy Performance dashboard\n-----------------------------------\n\nTo access the Proxy Performance dashboard:\n\n1. In the Google Cloud console, go to the **Analytics \\\u003e API metrics \\\u003e API Proxy Performance** page.\n\n [Go to API Proxy Performance](https://console.cloud.google.com/apigee/analytics/proxy-performance)\n2. Select an **Environment or Hostname** and one or **All** proxies in the **Proxy** list. Selecting **All** shows charts for all proxies including aggregated data for proxies. Selecting a single proxy shows charts with data for that proxy only.\n3. If desired, change the default time range. For example, you can view data for the last day or the last 14 days.\n\nThe **API Proxy Performance** view is shown. Aggregate metrics for each chart, such as the\naverage transactions per second (**Average TPS**) are shown to the right of the chart\n\nWhat does this dashboard measure?\n---------------------------------\n\nThis dashboard includes these charts:\n\n- [Average transactions per second (TPS)](#averagetraffic)\n- [Traffic](#traffic)\n- [Average Response Time](#averageresponsetime)\n- [Traffic by Proxy](#trafficbyproxy)\n- [Average Response Time by Proxy](#averagebyproxy)\n\n| **Note:** This `client.received.start.timestamp` time value is used to calculate traffic metrics for API proxies in the analytics dashboards. For more information, see the [client](/apigee/docs/api-platform/reference/variables-reference#client) flow variable reference.\n\n### Average transactions per second (TPS)\n\n### Traffic\n\n### Average Response Time\n\nSee also this interesting article on the Apigee Community site:\n[When can the Average Total Response Time be less than the Average Target Response Time?](https://community.apigee.com/articles/2695/when-can-the-average-total-response-time-be-less-t.html)\n\nAverage proxy response time is calculated as the difference between the averages of total response time and target response time. The expectation is that total response time is always greater than the target response time. However, there are also calls which are handled by the proxy itself - preflight requests, cached responses, Oauth tokens etc which do not reach the backend system. These \"faster\" calls by the proxy reduce the average Total Response time without reducing the Target response time. Hence the average total response time may not always be greater than the average target response time which could result in negative values being seen for proxy response time. When you look at larger TPS without zooming in the time scale too much, these exceptions will not hold much weight and hence give you more accurate and actionable data.\n\nYou obtain the most meaningful average response data when a large number of requests are collected over a long period of time, rather than from just a few requests collected over a short period of time. If you only observe a small number of requests that come in over a short time period, there's a chance that even one call that does not go to the target will result in a negative average proxy response time. When evaluating average response times, it's best to view longer time frames that have high traffic.\n\n### Traffic by Proxy\n\n### Average Response Time by Proxy"]]
