This pageapplies toApigee andApigee hybrid.

View Apigee Edge documentation.

Apigee API Monitoring, Apigee API Analytics, and Apigee access logs arethree powerful tools you can use to collect, observe, and understand your API usage data. Each of these tools provides different insights and is recommended for different use cases. This document provides a brief overview of the purpose of each tool and its recommended usage, as described in the following sections:

• API Monitoring
• Apigee API Analytics
• Apigee access logs

API Monitoring

The goal of API Monitoring is to provide real-time insights into APIperformance, so that you can quickly diagnose and fix issues to keep your APIs working as intended.

API Monitoring provides you with aggregated data from your API proxies on a minute-by-minute basis, enabling you to closely monitor the health and performance of your APIs. You can use API Monitoring to configure near to real-time alerting on specified parameters and take advantage of the aggregated data when troubleshooting.

API Monitoring lets you:

• Maintain the availability of your APIs.
• Act on alerts before consumers are affected.
• Use Apigee fault codes to speed diagnosis of issues.
• Isolate problem areas quickly to diagnose the source of performanceand latency issues.

Apigee customers can also useCloud Monitoring tools to support API Monitoring. If you want to integrate with other monitoring systems, we recommend that you use the Monitoring API to pull metrics.

Latency data when using API monitoring

As API monitoring is intentionally designed to scale, it doesnot record every individual latency measurement in each transaction. Instead,distribution buckets are used to measure latencies. Latency buckets use predefined ranges to group observed latency values.

To learn more about using API Monitoring for your APIs, seeAPI Monitoring overview.

To learn more about using Monitoring along with Apigee to configure alerts, seeSetting up alerts and notification.

Apigee API Analytics

Apigee API Analytics provides historical trend analysis and detailed reporting for API call metadata. The goal of Apigee Analytics is to help you understand the long-term trends of your API traffic, so that you can make sure your APIs are supporting your business requirements, or make changes if necessary.

With Apigee API Analytics, you can choose from approximately 50 availabledimensions that specify the data you want to capture for each API call handled by a proxy. You can then createcustom reports to determine how specificAPI metrics change over time.

The analytics data captured is stored in BigQuery. You can use Apigee API Analytics tocreate custom reports in Looker Studio, set upasynchronous custom report jobs, orexport analytics data to your own Google Cloud storage repository, like BigQuery.If you start with Pay-as-you-go pricing, API Analytics is an optional add-on.

Here are a few of the trends that you can identify using Apigee Analytics:

• How is your API traffic trending over time?
• What are your top apps?
• Who are your top developers?
• When is API response time fastest or slowest?
• Which geographical regions have the most API traffic?

Note: Apigee API Analytics is not recommended as a tool for configuring alerts.

Latency data when using Apigee API Analytics

Observed latency in Apigee API Analytics uses anapproximate quantile aggregation function on individual records stored in BigQuery. This makes the resulting data surrounding latency more precise as compared to the bucketing logic used in API Monitoring. The latency in both API Monitoring and Apigee API Analytics is measured from the Apigee runtime and does not include latency calculations from prior networking hops, including Istio.

To learn more about Apigee API Analytics, seeApigee API Analytics overview.

Apigee access logs

Apigee access logs can be used to troubleshoot API calls to Apigee and identify which APIs are returning particular HTTP response codes.

Apigee access logs capture logs per transaction at the ingress gateway to Apigee. This lets you filter logs based on specific HTTP codes and readily troubleshoot corner cases, such as a response status code of0 on Istio.

To learn more about using Apigee access logs to troubleshoot your APIs, seeApigee access logs.

Differences between data displayed by API Monitoring data and Analytics

API Monitoring and Apigee API Analytics use different pipelines to access API data. As a result, you may see some discrepancies between the data displayed by Apigee API Analytics dashboards and the data available in API Monitoring.

Timeliness and accuracy

In general, the data displayed by Apigee API Analytics is more accurate, but may be slightly delayed (by less than an hour) compared to the data displayed by API Monitoring.

Data retention

Apigee API Analytics retains data for a longer time period than API Monitoring, making it more suitable for analysis of long-term trends.

The data retention periods for Analytics and API Monitoring are as follows:

• Analytics

  • Standard: 60 days
  • Enterprise: 90 days
  • Enterprise +: 14 months

• API Monitoring: 1 month

Note: The default retention period of one month for API Monitoring can be extended by changing the retention period in Cloud Monitoring. For more information, seeData retention.