Monitoring & usage

Charts stay empty until something has been called: ML, Forecast, Loop, Resolve, Read, or Vision.

Where to look

Surface	How to open	What it shows
Usage	Sidebar → Usage (`/usage`)	Account intelligence + Lake/Lab tabs
Per-asset detail	Sidebar → ML / Forecast / Loop → click asset	Request log, drift (ML), endpoint breakdown
Dashboard	Sidebar → Dashboard	KPIs, shortcuts to Lake and Usage
Lake catalog	Sidebar → Lake	Bronze/silver/gold inventory, ingest jobs
Platform status	Navigate to `/health` or sidebar footer health indicator	Backend service availability

Open Usage from the sidebar. Two tabs:

Account-wide monitoring for every inference product:

Daily volume: stacked bars by product (ML, Forecast, Loop, Resolve, Read, Vision) or total line
Channel mix: Heimdall UI (in-app tests) vs API (your integration)
Response times: average latency per day
Summary cards: total inferences, API requests, avg response time, peak day (7 / 30 / 90 days)
Products panel: all-time totals with links to ML, Forecast, Loop, Resolve, or Settings (Read/Vision)
Top assets: models, forecasts, loops, and resolves ranked by call volume
Endpoint breakdown: which REST routes received traffic

Legacy URL aliases: ?tab=intelligence, ?tab=monitoring, ?tab=overview open this tab.

Lake and Lab activity:

Links jump to Lake or Lab.

Open the asset at /ml/{id}, /forecast/{id}, /loop/{id}, or /resolve/{id}.

Product	Where	What one call counts
ML	Usage on the model page	1 for `/predict/`, or one per successful batch row
Forecast	Usage on the forecast page	`time_windows` steps
Loop	Usage on the loop page	Predictions returned, and train calls
Resolve	API tab	1 answer

ML also stores a drift percentage when that model has drift stats from training. Forecast does not.

Read and Vision have no per-asset page. Their volume is on Usage → Data Intelligence only.

Platform status polls backend health and shows operational vs unavailable for auth, predict, ingestion, loop, read, vision, and related services.

Open directly: /health
Quick check: green indicator in the sidebar footer (expands to full panel on the health page)

Use during incidents or before launch windows. This is customer-facing availability: not a replacement for your app logs.

Mistake	Reality
Expecting Read/Vision per-request detail	Only account-level charts
Zero usage after deploy	In-app tests count: look for Heimdall UI channel
Charts empty on day one	Normal until first API or UI inference