- There is a change in the number of users (fewer users = lower traffic)
- There is a change in the number of apps calling an API (fewer call s= lower traffic)
- There is a change in the ability of the API to handle traffic. The network may be down, or the API has a new Quota policy that is restricting traffic
- There is a change in the amount of legitimate traffic (i.e. real user calls vs. attacks). Attacks could be taking up your bandwidth
- Use contextual analytics to look for traffic spikes or drops
- Generate a traffic report to see which App have a change in the amount of traffic they are sending to an API
- Look at traffic for specific resources a period of time to see if individual resources are experiencing drops/spikes
Use contextual analytics
Go to main dashboard page (click the apigee logo).
Look for large changes in traffic in the All API traffic chart. This will give you sense of when the change occurred. Here you can see a spike occurred on in mid August. When investigate further you'll want to look at this time period in particular.
Also check the Top API movers chart. You can see that which APIs had the highest drop or increase in traffic.
Generate a custom traffic report
A custom traffic report will let you examine specific apps and URIs to see exactly where the problem is occurring. The report will tell which apps have had a change in traffic. For each app you can see the traffic trend for all the APIs the app calls. You create an App traffic report by using apps the main measure with drill down on the requested URI by app.
Set up the primary measure
- On the Analytics tab, click the + Custom Report button.
- Enter App Traffic Report as the Report Name.
- Enter a brief description of the report in the Report Description field.
- Select prod from the Environment menu.
- Select message_count as the Primary Measure. This will let you see traffic data.
Set up data display
- Select Count as the Function.
- Select Column as the Chart type.
- Select Hourly as the Chart Refresh Interval.
Set up chart drill down
These selection will determine how you can refine the view of your content.
- Choose developer_app as Drilldown 1. Use this measure to see all the apps in your org. This lets you see the traffic by app.
- Choose request_uri as Drilldown 2. This dimension will break up the traffic by API.
- Click Save to generate the report.
Analyze the report
- Look for an App that's showing a large change in traffic. You can change the time period to see traffic trends over time.
- Click on the app you want review to drill down into more details. Again, using the time period menu, can view requests made by the App over various time periods to understand the nature of the traffic spike or drop. Look to see if individual resources are seeing a drop in the traffic or if it's the whole API. If only one resource is seeing a drop, it points to a possible network issue or reduced usage of a specific resource.
Decide on an action
If you're see a drop in an individual resource you may want to investigate your network infrastructure. If you're seeing unusual traffic patterns to your apps you may be under an attack that is eating up your bandwidth. If you're seeing a traffic increase to the whole API you may want to examine how the API is configured. You may have a policy that is limiting your traffic. In this case you can use Trace to inspect the message flow of your API.