Alternative to Business Transactions API

[anonymous]

Before using the Business Transactions dashboard to analyze traffic metrics for specific URI patterns, it is necessary to first configure those URI patterns within the respective API proxies.

Over the next few weeks, as we incrementally update the underlying analytics platform, the business transactions dashboard and proxy performance reports for those API proxies configured with URI patterns may return an error. This issue will resolve itself once the upgrade is fully rolled out, and these queries will begin functioning as expected. Note - this will not impact you none of your API proxies are configured with URI patterns.

In the interim, here is an alternate analytics API call that can be modified to get results for an API proxy with configured URI patterns.

Let’s say you would like to get the sum of traffic for a particular URI pattern (eg., “/products”) for a particular time period. The following analytics API can be modified to include the URI pattern as part of the filter argument along with other metrics and dimensions. Other metrics and dimensions can also be added to the call as needed.

API call template:

[https://api.enterprise.apigee.com/v1/organizations/<org>/environments/<env>/stats/apiproxy?_optimized=js&accuracy=100&limit=14400&select=sum(message_count),sum(is_error)&sort=DESC&sortby=sum(message_count)&timeRange=MM%2FDD%2FYYYY+HH:mm:ss~MM%2FDD%2FYYYY+HH:mm:ss&timeUnit=day&tsAscending=true&filter=(request_uri+like+‘%products%’)](https://api.enterprise.apigee.com/v1/organizations/<org>/environments/<env>/stats/apiproxy?_optimized=js&accuracy=100&limit=14400&select=sum(message_count),sum(is_error)&sort=DESC&sortby=sum(message_count)&timeRange=MM%2FDD%2FYYYY+HH:mm:ss~MM%2FDD%2FYYYY+HH:mm:ss&timeUnit=day&tsAscending=true&filter=(request_uri+like+‘%products%’))

[anonymous]

Create a custom report using URI patterns

This post is an addendum describing how the request_uri can be used as a filter condition in custom reports to identify metrics on the usage of these patterns in various apis.

Let’s assume that we are interested in metrics on proxy usage for an uripattern ‘%/products%’.

The following screenshot shows the Custom Report definition of how a simple report showing various metrics can be defined for this pattern.

In this report, three metrics have been defined. There are no explicit dimensions defined, so the default dimension of apiproxy is picked.

The filter condition is specified as belows using the Advanced tab

Note: The user must create different reports for different uripatterns. The filter condition will allow additional terms but the will serve to narrow or broaden the results and not to group the results by a pattern.

A sample result screen is shown below

These are the metrics for the specific uripattern ‘%/products%’

[ssvaidyanathan]

@Arvind Jain / @spadmanabhan - do we have an update on this ?

We are still seeing a note to this community post when try to view the Proxy performance.

[anonymous]

@Sai Saran Vaidyanathan the article continues to be the recommended method.