Dashboard tour
The customer dashboard lives at https://{your-customer-fa}.azurewebsites.net/api/dashboard?code=<admin-key>. It refreshes every 30 seconds and shows the live state of your stack.
Top row tiles
-
Plan & Seats — your current plan (badge) +
seatsUsed / seatQuota. Yellow border = you’re in the grace period. Red border = grace expired and (N+1)th agent claims are blocked. The “Upgrade in Marketplace” link is shown when you have an upgrade path. -
Active sessions — count of sessions whose
lastActivityAtwas within the last 24 hours. Includes both visitor-only and agent-handled sessions. -
Last 1h cost — estimated USD spent on Azure OpenAI tokens in the last hour. Computed from the token-usage records using your stack’s
pricePerInput/OutputUsdPerMsettings. -
Last 24h cost — same as above but rolled up over 24h.
-
Tokens (24h) — total input + output tokens to OpenAI in the last 24h.
Cost projection (linear vs median)
Two ways to extrapolate the next month’s bill:
- Linear — total 24h cost × 30. Simple; biased upward when you have a burst hour.
- Median — median per-hour cost across the 24 buckets × 24 × 30. Less swayed by bursts.
Use median for steady-state planning. Use linear for “what’s the worst case if today’s burst keeps happening”.
Charts
- Cost per hour — last 24 hours — bar chart, one bar per hour. Hover for exact USD + token count.
- Unique sessions per hour — bar chart of distinct session ids per hour. Useful to spot traffic spikes vs cost-per-session shifts.
Top sessions (24h)
Five most expensive sessions in the last 24h, sorted by total token cost. Click a session to drill into its transcript (visitor messages, bot replies, agent messages, with timestamps).
Settings panel
- Rotate admin key — generates a new 48-char hex value, writes to KV, shows once, invalidates existing sessions. See Key rotation.
- Sign out — clears your session cookie. Next dashboard access requires the admin key (or a fresh session).
- Teams setup — link to the per-deployment Teams app wizard. See Teams app.
Footer
- Deployment — your ARM deployment id (matches the ISV control plane records).
- Version — customer-runtime version (matches the marketplace package version baked into the plan zip you deployed from).
- Started — when the Function App last cold-started.