Trends
What changed since you last looked. Trends is the Observe tab’s opening page: the trailing week against the week before it, by domain, plus what appeared for the first time and the freshest issues. Every number on it is a pointer into a deeper page.
The domain table
One row per domain, plus a No domain row for calls that address an entity directly. Each cell shows this week’s number with the movement against last week beside it — ▲ 12%, colored by whether that direction is good news for that column:
| Column | This week’s… | Up means |
|---|---|---|
| Usage | Loads | More traffic — green |
| Quality | Data completeness % (load-weighted) | More grounded payloads — green |
| Avg Assembly | Average assembly time | Slower — red |
| Errors | Error rate (errors ÷ loads) | More failed loads — red |
| Issues | Issue occurrences | More degradation — red |
Click a domain to open Usage already filtered to it.
Two honesty rules shape the cells. A domain with fewer than five loads in either week shows its number without a movement — a percentage over a handful of loads is noise dressed as signal. And Errors and Issues are different measurements: errors are loads that failed outright; issues are degradation inside loads that mostly succeeded — see Issues.
New This Week
Domains that served their first load this week, and users who made their first call — first ever, measured over all recorded history, not merely active-this-week. A new user arriving through a domain names the domain they came through. This is where a rollout shows up: a team you just enabled appears here before anyone thinks to check.
Recent Issues
The ten freshest issue rows — category, artifact, domain, occurrence count, and the sample message — with a jump to the full Issues page.
Who sees it
Admins see every domain. Domain managers see the same page over the whole org’s traffic — Observe is org-wide by design, since degradation anywhere can affect answers everywhere.