API Monitoring 的目標是提供 API 效能的即時深入分析，協助您快速診斷及修正問題，確保 API 正常運作。API Monitoring 會顯示最新的 API 流量資料，並在發生問題時傳送快訊，方便您快速排解問題。
以下列舉幾個可透過 API 監控執行的工作：
維持 API 可用性。
根據警示採取適當行動，避免消費者受到影響。
運用 Apigee 錯誤代碼，加快問題診斷速度。
快速找出問題區域，診斷錯誤、效能和延遲問題，以及問題來源。
Apigee 客戶也可以使用 Cloud Monitoring 工具支援 API Monitoring。如要與其他監控系統整合，建議您預設使用 Cloud Monitoring API 來提取指標。
Apigee 數據分析
Apigee Analytics 的目標是協助您瞭解 API 流量的長期趨勢，確保 API 符合業務需求，或視需要進行變更。如要研究這些趨勢，您可以建立自訂報表，判斷特定 API 指標隨時間的變化。
以下是您可以使用 Apigee Analytics 識別的幾項趨勢：
API 流量的長期趨勢如何？
您有哪些熱門應用程式？
您最常與哪些開發人員合作？
API 回應速度最快或最慢的時間為何？
您在哪些地理區域看到最多 API 流量？
API 監控資料和 Analytics 顯示的資料差異
API 監控和 Analytics 使用不同的管道存取 API 資料。因此，您可能會發現 Analytics 資訊主頁顯示的資料與 API 監控資料有所差異。一般而言，Analytics 顯示的資料較準確，但可能比 API 監控資料略有延遲 (不到一小時)。不過，這些微小差異不會影響 API 監控功能，您仍可透過這項功能掌握 API 的效能。
資料保留
Apigee Analytics 的資料保留時間比 API Monitoring 長，因此更適合分析長期趨勢。Analytics 和 API 監控的資料保留期限如下：
[[["容易理解","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\u003eThis content covers both API Monitoring and Apigee Analytics, explaining their distinct purposes and capabilities within the Apigee and Apigee hybrid platforms.\u003c/p\u003e\n"],["\u003cp\u003eAPI Monitoring focuses on providing real-time insights into API performance to quickly identify and resolve issues, ensuring API availability and enabling swift troubleshooting.\u003c/p\u003e\n"],["\u003cp\u003eApigee Analytics helps understand long-term API traffic trends, supporting business needs and enabling adjustments based on metrics like top apps, developers, and response times.\u003c/p\u003e\n"],["\u003cp\u003eWhile both tools collect API data, Apigee Analytics is designed for in-depth, long-term trend analysis with longer data retention periods, whereas API Monitoring prioritizes immediate operational insights.\u003c/p\u003e\n"],["\u003cp\u003eAPI Monitoring data may show minor discrepancies and be more timely compared to Apigee Analytics, but this does not hinder its effectiveness in maintaining awareness of API performance.\u003c/p\u003e\n"]]],[],null,["# Compare API Monitoring with Apigee Analytics\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\nThis section compares API Monitoring with\n[Apigee Analytics](/apigee/docs/api-platform/analytics/analytics-services-overview).\nWhile both API Monitoring and Analytics let\nyou collect and view API data, they have different objectives, as described\nin the following sections:\n\n- [API Monitoring](#api_monitoring)\n- [Apigee Analytics](#apigee_analytics)\n\nAPI Monitoring\n--------------\n\nThe goal of API Monitoring is to provide real-time insights into API\nperformance, and help you quickly diagnose and fix issues to you keep your APIs\nworking as intended. API Monitoring displays the latest API traffic data,\nand sends you alerts when issues arise so you can troubleshoot them quickly.\n\nHere are a few examples of the tasks API Monitoring enables you to perform:\n\n- Maintain the availability of your APIs.\n- Take appropriate actions based on alerts before consumers are affected.\n- Leverage Apigee fault codes to speed diagnosis of issues.\n- Isolate problem areas quickly to diagnose errors, performance, and latency issues, and their sources.\n\nApigee customers can also use\n[Cloud Monitoring](https://cloud.google.com/monitoring/docs)\ntools to support API Monitoring. If you wish to integrate with other monitoring systems, we recommend that you use the Cloud Monitoring API by default to pull metrics.\n\nApigee analytics\n----------------\n\nThe goal of Apigee Analytics is to help you understand the long-term\ntrends of your API traffic, so that you can make sure your APIs are supporting\nyour business requirements, or make changes if necessary. To study these trends,\nyou can create\n[custom reports](/apigee/docs/api-platform/analytics/create-custom-reports)\nto determine how specific\n[API metrics](/apigee/docs/api-platform/analytics/analytics-reference#metrics)\nare changing over time.\n\nHere are a few of the trends that you can identify using Apigee Analytics:\n\n- How is your API traffic is trending over time?\n- What are your top apps?\n- Who are your top developers?\n- When is API response time fastest or slowest?\n- In what geographical regions do you see the most API traffic?\n\nDifferences between data displayed by API Monitoring data and Analytics\n-----------------------------------------------------------------------\n\nAPI Monitoring and Analytics use different pipelines to access API data. As a result,\nyou may see some discrepancies between data displayed by Analytics dashboards\nas opposed to API Monitoring. In general, data displayed by\nAnalytics is more accurate, but may be slightly more delayed (by less than an\nhour),\nthan data displayed by API Monitoring data. However, these minor differences\ndon't affect API Monitoring's ability to keep you informed about your API's performance.\n\n### Data retention\n\nApigee Analytics has longer data retention than API Monitoring, making it more\nsuitable for analysis of long-term trends.\nThe data retention periods for Analytics and API Monitoring are as follows:\n\n- Analytics\n\n - Standard: 60 days\n - Enterprise: 90 days\n - Enterprise +: 14 months\n- API Monitoring: 6 weeks"]]
