Every call, fully traced — without exposing what's inside it.
An Overview with KPIs and a usage-over-time chart, a Requests log with per-request metadata and guardrail findings, and an Errors & Blocked view — metadata-only by default, and the underlying model provider is never shown to your team.
What you see
Three views, one request pipeline
Overview
KPI strip — request volume, spend, guardrail block rate, error rate — plus a usage-over-time chart so you can see traffic shape and cost trend at a glance.
Requests
A per-request log: model tier, token counts, cost, latency, routing mode, cache hit, and guardrail findings for that call. Prompt and completion content is never stored in this log — metadata-only by default.
Errors & Blocked
Coarse error categories and guardrail block reasons for the calls that didn't complete cleanly — surfaced without any prompt or response content attached.
Privacy posture
Metadata-only, provider-hidden by design
Observability is built to answer "what happened" without ever needing to show "what was said." Prompt and response content stays out of the log by default — full content capture is opt-in and masked when you turn it on. Your data is isolated per tenant, the underlying model provider is never named to your team, and everything is built residency-first for Indonesia under UU PDP.
Provider-hidden
Anoman routes the call — the specific model provider behind a response is never surfaced in the dashboard or the API. You see the model tier and outcome, not the vendor.
Per-tenant isolation
Every request, trace, and log line is scoped to your account. Nothing is pooled or visible across tenants — not even in aggregate.
Residency-first (UU PDP)
Metadata-only logging by default, opt-in masked content capture when you need deeper debugging, and Indonesia-residency-first infrastructure aligned with UU PDP.