




















This article assumes you already have an Azure Foundry project and resource deployed in Microsoft Foundry. The options referenced here are documented in detail in the linked articles; this post serves as a consolidated step by step guide bringing them all together and explaining where each option is most useful.
|
Need |
Best Option |
|
Quick day-over-day visual, minimal setup |
Grafana Dashboard (Option 3) |
|
Custom growth % calculations |
App Insights + KQL in Log Analytics (Option 4) |
|
Shareable, interactive report |
Azure Workbooks (Option 5) |
|
Per-user/per-agent granularity |
APIM + App Insights (Option 6) |
|
Quick one-off chart, export to Excel |
Microsoft Foundry Monitor tab or App Insights Metrics Explorer (Option 1 and 2) |
If you have models deployed in Microsoft Foundry and would like to monitor its usage, go to the New Foundry Portal → Build → Models → Monitor tab.
View metrics such as:
This is the simplest way to monitor both model and agent usage.
Microsoft Foundry has a built in Monitor tab to view your model/agent usage.
For PAYG plans:
You can also view your total allocated quota (and figure out which Tier you are on) using the Quota Management Screen (New Foundry Portal → Operate → Quota tab).
This screen shows how much your total allocated quota is, per model in a given subscription + region + Deployment Type (Global, Data Zones or Regional). For eg., in the image below, for gpt-4o, I am allocated 7M total TPM in my subscription. I am only using 150K TPM of the allocated 7M TPM amount.
Which means, my requests will get throttled if I exceed the 150K TPM limit. To avoid throttling, I would need to increase my shared allocation limit.
NOTE: you are charged for usage, so if you allow more capacity, you use more, so you pay more.
This is already built into the Azure Portal and gives you time-series charts out of the box.
Tip: You can pin these charts to an Azure Dashboard for a persistent view, or click Share → Download to Excel to get the raw data for your own analysis.
This is the best option for a polished, real-time, day-over-day dashboard with no custom code. There's a pre-built AI Foundry dashboard ready to import. [grafana.com], [Create a M...ed Grafana]
How to set it up:
Token trends over time (inference, prompt, completion — day over day)
Request trends over time (AzureOpenAIRequests as a time series)
Latency trends (bonus)
NOTE: Default time range is 7 days — adjust to 30/60/90 days for growth trends
If you want fully custom day-over-day growth calculations (e.g., % change day-to-day), this is the way. [azurefeeds.com]
Setup:
Same view but showing a chart:
Export options:
Another way to get the above graphs are via Log Analytics. Simply enable Diagnostic Settings on your Azure OpenAI resource → send to a Log Analytics workspace. Open Log Analytics → Logs and try our your sample queries.
Sample KQL for day-over-day token usage (adjust to your needs):
AzureMetrics
| where MetricName in ("TokenTransaction", "ProcessedPromptTokens", "GeneratedTokens")
| where TimeGenerated > ago(30d)
| summarize DailyTokens = sum(Total) by bin(TimeGenerated, 1d), MetricName
| order by TimeGenerated asc
| render timechart
Result:
Sample KQL for day-over-day growth % (adjust to your needs):
AzureMetrics
| where MetricName == "TokenTransaction"
| where TimeGenerated > ago(30d)
| summarize DailyTokens = sum(Total) by Day = bin(TimeGenerated, 1d)
| sort by Day asc
| extend PrevDay = prev(DailyTokens)
| extend GrowthPct = round((DailyTokens - PrevDay) / PrevDay * 100, 2)
| project Day, DailyTokens, GrowthPct
Workbooks let you build interactive, parameterized dashboards that combine metrics and KQL logs.
What's more, you can select resources from multiple subscriptions and visualize them all in one place using Workbooks!
You can select different resources (or subscriptions) and view them all in one pane.
4. Save and share with your team.
1. If your app routes requests through Azure API Management, you can use the azure-openai-emit-token-metric policy to send per-request token metrics to Application Insights with custom dimensions (User ID, Subscription ID, Agent, etc.). [Azure API...osoft Docs]
This is ideal for scenarios like:
NOTE: Microsoft Foundry resources do not track usage by users. So, fronting your Foundry resource with an APIM could be a way to track users provided you pass the username/id in the request context. How you implement this is upto your app design.
Bonus: Check out all other APIM + AI related policies here:
AI-Gateway/labs/semantic-caching at main · Azure-Samples/AI-Gateway
AI-Gateway/labs/token-rate-limiting at main · Azure-Samples/AI-Gateway
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。