Analytics - Geography
In this article, we will cover the geographical analytics for the Azure API Management.
- Country: countries that were initiating traffic to your APIM. This is a good indicator for you to know which countries are accessing your APIM. For example, If you have no clients in Turkey, and you’re not expecting any traffic to be coming from Turkey, but you can see it in the APIM analytics. It’s going to be good to bring this up for investigation by the security team and understand who is initiating this traffic and whether it’s genuine or not.
- Unauthorized Requests: this shows the number of unauthorized requests posted to your APIM. Analyze this metric in combination with the Country metric to understand, from which country unauthorized requests to your APIM originate.
- Total Requests: This shows you the total number of requests being sent from different geographics. This could help you determine what’s the best way to scale your APIM. For instance, If you’re getting many requests from the USA region, it might make more sense (and has a more positive effect on the APIM performance by having the APIM instance closer to the consumer) to launch an additional APIM instance in US region, rather than to scale up the tier of your APIM that might be hosted in the other side of the world (AU East for example in this case).
Was this article helpful?
Thank you for your feedback! Our team will get back to you
How can we improve this article?
Character limit : 500