Apigee Edge collects information as data passes through it. The data includes API call information (URL, IP, and user ID) latency, errors, and so on. This data is gathered into trend charts and tables throughout the management UI. You can use this data to both monitor the overall health of your API program and the health of individual APIs.
See Analytics Services overview for more information.
This tutorial assumes that you have competed the first tutorial, where you create an API proxy to access the Yahoo weather API. If you have not yet completed that tutorial, see Part 1: Create your API.
While it is not required, Apigee recommends that you also complete the policies tutorial. See Part 2: Add policies to your API.
Use the data charts to see metrics about your APIs:
- In the management UI, click APIs. If the API Platform page is not open, click here.
- If not already selected, select test in the Environment drop-down list at the top of the page.
- Scroll down to the Performance section to the chart displaying metrics for all of your APIs. There may be a few minutes' lag time between when you send requests and when the metrics are available in the charts.
If you were to make requests over several hours, your chart might look something like this:
You can show or hide metrics for APIs by clicking their names in the right pane of the chart. You can select different time periods, different types of metrics, and you can move your mouse pointer over the chart to see details about specific data points.
You probably won't have much data yet. But select a Time Period of one hour to see information about the weather API.
- Now look at metrics for only your weather API. Click weather in the API Proxies list, click Overview, then scroll down to the Performance section, where you can view metrics for only the weather API and its resources.
- For a comprehensive, multi-dimensional view of your entire API program, click Dashboard in the management UI menu. The dashboard provides views of traffic, partner and developer engagement, and top performing APIs, products, apps, and developers. You can view different date ranges and drill down into API traffic details.
Analytics charts can also be exported to various file formats.
Now that you have created your first API, and learned more about policies and APigee tools, it is time to secure your API. It's important to protect your API from unauthorized access. One way to do that is to validate API keys (also called "public keys", "consumer keys" or "app keys").Continue on to Part 1: Create a secure API to learn about using API keys.
Help or comments?
- Something's not working: See Apigee Support.
- Something's wrong with the docs: Click Send Feedback in the lower right.
(Incorrect? Unclear? Broken link? Typo?)