Is it recommended to proxy APIGEE analytics API calls and expose?

[Ronson_Xaviour]

One of our customers would like to set up a dashboard on their side which will display API health based on analytics data. Apart from the dashboard, they'd like to set up a probe to watch the traffic and send alerts in case if the error rate goes above a limit.

We understand that we can leverage the analytics API in this case. However, we don't want to add one more user to Edge only for accessing analytics API and various security reasons. We'd like to proxy the analytics API by which we can restrict the caller from accessing unwanted data.

Is it recommended to proxy analytics API calls and expose to the caller in this case? Any issues in calling management APIs from Edge MP?

Any suggestions are appreciated.

[sidd-harth]

Hi @Ronson, by what I have seen on this forum, it is not recommended to proxy Management API calls.

What kind of data from Analytics API do you want to restrict the caller from accessing?

If you are an Apigee Edge Cloud Enterprise customer, the make use of Apigee API Monitoring for alerts.

[Ronson_Xaviour]

Hello @Siddharth Barahalikar,

If we create a user on Edge for the caller to consume analytics API, this user will have read access to all the modules on Edge and we don't want that. Also, we'd like to restrict the user from seeing the statistics of other API Proxies.

Wondering why is it not recommended to proxy Managment API calls.

[petamorris06]

Your monitor should be with proper proxy setup which can be connected with router easily. otherwise you do need proxy ananysis before you connect wireless router. try with linksys e1200 setup without cd this may help you to increase the speed of data you are getting from router and also gives the secure server to maintain privacy .