I’ve noticed that we can see analytics per api proxy, but I don’t see a way to filter down these results to just certain endpoints. This is really critical for us, as we have proxies with up to 10+ endpoints, and need analytics for each one.
10 different flows. As in, ten different paths (/inventory/quantity, /orders/status, /salesorders, etc.) with their own flow that converge to a single target endpoint.
In Custom Report, there is a dimension for Proxy Path Suffix you can select that will give you the stats for each calls that were made to those resources
You can create a Custom report with Proxy as the first dimension and Proxy Path Suffix as the second dimension. Save the report
On clicking the proxy (in my case, I clicked the uberapi proxy), you should be able to drill down to another graph that shows the report per path suffix within that proxy
You can create a report with just Proxy Path Suffix as One dimension, but with the way I mentioned, its more easier to get the values for each proxies. Otherwise you would see across all which could make the report confusing
Your suggestion are working. But I was trying to do open period like get an aggregate results for 3 months. The report does not allow me more than 15 days period. is the a way to have free date/time range?
For that you might need to use the Management Stats API. I just ran this curl command to get the JSON response. You can use this and convert to a report
curl -X GET --header "Authorization:Basic *****" "https://api.enterprise.apigee.com/v1/o/{org}/e/{env}/stats/proxy_pathsuffix?select=sum(message_count)&timeRange=10%2F01%2F2016%2000%3A00~10%2F30%2F2016%2023%3A59&timeUnit=week"<br>
You can provide your own time range you want. I have provided 10/01/2016 to 10/30/2016
That works but not when we have proxy suffixes with dynamically determined parameter. If I have a /path/{dynamically_determined_parameter} as the path suffix, it will treat each endpoint as a unique path. Is there any suggested ways to do this?
Hi @Haline , welcome to the Apigee community—Thank you for engaging with this thread.
To ensure your question gets the attention it deserves, we recommend creating a new thread with the details of your issue. Feel free to reference this discussion in your new post for context.
Now that you’re here, we also encourage you to explore other community resources, including articles and upcoming events. We’re excited to have you as part of the community.