Share via

In the API Management blade in the Azure Portal, why has the filter not been copied from the "Analytics (classic)" blade to "Analytics"?

Matt Padfield 60 Reputation points
2026-06-03T16:32:46.3666667+00:00

In the API Management blade in the Azure Portal, the "Analytics (classic)" blade has a useful option for filtering by API, Product, Region, Subscription, User. This is missing in the replacement "Analytics" blade which can only filter by date/time. Could someone explain please:

Will this filter be added to the "Analytics" blade?

What options exist for getting the charts and tables shown in the Analytics blade, but filtered as in the classic blade?

User's image

Azure API Management
Azure API Management

An Azure service that provides a hybrid, multi-cloud management platform for APIs.


Answer accepted by question author

Pravallika KV 16,700 Reputation points Microsoft External Staff Moderator
2026-06-03T21:32:24.13+00:00

Hi @Matt Padfield ,

Why you can’t filter by API/Product/Region/etc. in “Analytics” today

The new Analytics blade is actually just an Azure Monitor powered workbook under the covers. It only ships with built-in time-range pickers and category-based drill-downs (like click “APIs” to see a per-API breakdown, or “Products” to see per-product usage), but it doesn’t yet mirror the classic blade’s dropdown filters for API, Product, Region, Subscription, User. There’s no public roadmap item stating that those exact controls will appear in the portal UI, since Microsoft’s pushing everyone toward custom Log Analytics queries & workbooks anyway and the classic blade will be retired in March 2027.

How to get the same filtered views today

  1. Metrics explorer (Monitoring → Metrics)
    • In Metrics you can choose the “Calls” metric (or any other metric API Management emits) and then add dimension filters: API name, Product, Subscription ID, Region, etc.
  2. Log Analytics workspace + Kusto queries
  • Under Monitoring → Diagnostic settings, send your ApiManagementGatewayLogs to a Log Analytics workspace (resource-specific table). Then in Logs you can write a query like
    
       ApiManagementGatewayLogs
       
       | where TimeGenerated between (startTime .. endTime)
       
       | where ApiId == "<your-api-id>"
       
       | where ProductId == "<your-product-id>"
       
       | summarize count() by bin(TimeGenerated, 1h), Region, CallerIpAddress
       
    
    • You can parameterize that in a Workbook and even add drop-down selectors for API, Product, Subscription, User, Region, etc.
  1. Azure Monitor workbooks
    • Go to Monitoring → Workbooks → + New, pick the “API Management Analytics” template, and then you can add dropdown parameters bound to your Log Analytics fields.
  2. REST/SDK-based analytics APIs
    • If you prefer code, you can call the API Management REST analytics endpoints or use Azure CLI/PowerShell to pull usage data filtered by API or product.

Hope this helps!


If the resolution was helpful, kindly take a moment to click on User's imageand click on Yes for was this answer helpful. And, if you have any further query do let us know.

Was this answer helpful?

2 people found this answer helpful.

Answer accepted by question author

Amira Bedhiafi 42,286 Reputation points MVP Volunteer Moderator
2026-06-03T18:51:56.0733333+00:00

Hello Matt !

Thank you for posting on MS Learn Q&A.

The filter was not copied because Analytics and Analytics (classic) are not the same implementation. Analytics is the newer Azure Monitor / Log Analytics–based dashboard, while Analytics (classic) is the legacy built-in APIM analytics experience. If you check the doc the classic analytics can be filtered by other report categories but the new Analytics dashboard steps only mention selecting a time range and report category not those classic filters. Classic analytics is also scheduled for retirement in March 2027.

https://learn.microsoft.com/en-us/azure/api-management/monitor-api-management

There is no public commitment in the docs that the same API/Product/Region/Subscription/User filter UI will be added to the new blade. The recommended workaround is to use Log Analytics / KQL over ApiManagementGatewayLogs then save the result as an Azure Monitor Workbook ,dashboard, Grafana dashboard, or Power BI report. The new dashboard uses a Log Analytics workspace as its source, and the gateway log table contains the fields needed for these filters, including ApiId, ProductId, Region, ApimSubscriptionId, UserId, and OperationName.

Example KQL:

ApiManagementGatewayLogs
| where TimeGenerated > ago(24h)
| where ApiId == "my-api-id"
| where ProductId == "my-product-id"
| where Region == "West Europe"
| where ApimSubscriptionId == "subscription-id"
| where UserId == "user-id"
| summarize
    Requests = count(),
    FailedRequests = countif(IsRequestSuccess == false),
    AverageDurationMs = avg(TotalTime),
    P95DurationMs = percentile(TotalTime, 95)
    by bin(TimeGenerated, 15m)
| render timechart

For a table similar to the Analytics blade:

ApiManagementGatewayLogs
| where TimeGenerated > ago(24h)
| where ApiId == "my-api-id"
| summarize
    Requests = count(),
    FailedRequests = countif(ResponseCode >= 400),
    AvgDurationMs = avg(TotalTime),
    P95DurationMs = percentile(TotalTime, 95)
    by ApiId, OperationName, ProductId, ApimSubscriptionId, UserId
| order by Requests desc

To summarizen use Analytics (classic) while it is still available but build the filtered version in Log Analytics / Workbooks for the long-term replacement.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.