Introduction
During development, testing, and support, we ask the following questions to understand what happened during an API call:
How many calls succeeded or failed?
What HTTP method was used (GET, POST, PUT, etc.)?
What is the resource path for the failed or successful calls?
However, it is often difficult to extract detailed information such as the HTTP method used and the response codes for each failed API call. When you open a proxy, you can see calls listed, but they are often not helpful, especially in error cases.
Standard monitoring tiles do not have any filters to see these information and you can only see upto 25 proxies and rest is flagged as others. Analytics Dashboard
Proxy Creation Types
We need to understand what are the ways to create proxies before jumpint into monitoring. There are variety of ways to create API proxies. Though it is easier to monitor proxies which fall under option 2, still custom dashboad can help to clearly see what was called.
Without any resource (Masking)One resource but one methodMultiple resource and multiple methodsMultiple target endpoints
For demonstration purpose I will make use of Northwind API https://services.odata.org/northwind/northwind.svc/
I will show you only masking and multiple resources with multiple methods type proxies for the sake of domonstration.
Masking
Proxy with multiple resources and methods
Custom Dashboard
Let us build custom Dashboard. First create custom view
You can see your charts now.
Testing
Let us use postman to trigger some API calls for monitoring.
Monitoring
Let us navigate to Analyze —>Custom Dashboard
You can select your proxy here if you see it, else make use of filter option to select the needed proxy
Filter option—> We can add one or more filters
Let us select Masking Proxy and find out the calls details
You can select Get and see the response codes
References
Read More Technology Blog Posts by Members articles
#abap