DocsObservability
Summary and reports
One page for the people who answer for AI: estimated provider spend against budget, four status lights, a weekly email, a monthly report and saved views.
INFRO is in private early access. Running these examples requires an early-access account, an active trial or subscription entitlement, and your own provider connection. Self-serve purchasing is not generally open. See Early access.
The Summary is the console's page for the people who answer for AI in your organization. It shows this budget cycle's estimated provider spend against the budget and where it is heading, whether requests are working, how access is governed, and what needs a decision. Every amount is an estimate of what your own providers will bill you, from list or negotiated rates; INFRO's subscription is never part of it, and a request with no known rate is counted as unpriced, never as $0.
Open it from Summary at the top of the rail. Finance and analyst members open the console on it by default; anyone can choose their start page under Settings → Account.
Four status lights
Each light has a colour and the sentence that explains it. There is no combined score: a score would hide which of the four needs attention.
| Light | Green | Amber | Red |
|---|---|---|---|
| Spend | Projected below 90% of the budget. | Projected at 90% of the budget or more. | Projected above the budget, or the budget is reached. |
| Reliability | At least 99% of requests succeeded and no provider key is out of rotation. | Below 99%, or some keys are out of rotation while others serve. | Below 95%, or every key of a provider is failing. |
| Governance | Members sign in with two-factor authentication or SSO, and no gateway key has gone unused for 30 days. | A member signs in without two-factor, or an unused key still works. | None. |
| Coverage | At least 80% of spend is assigned to a project and at least 99% of requests are priced. | Less than either. | None. |
The budget is the organization's hard cap when one is set, otherwise its monthly target. With neither, Spend says so and shows the amount and projection alone. The projection is spend so far plus the average of the last seven days for each day left in the budget cycle, so a quiet start and a busy last week both show up.
Below the lights: what needs a decision (failing connections, open findings, budgets close to their limit), where the spend went by project and model with the change against the same days of the last cycle, reliability, and governance. Each line links to the screen where it is acted on.
The weekly summary and the monthly report
- Weekly summary, by email on Mondays from 08:00 UTC: the last seven days' estimated provider spend and its change on the week before, the cycle so far and its projection, the four lights with their reasons, and the largest projects and models.
- Monthly report, by email on the 2nd of each month from 08:00 UTC, for the calendar month before: estimated provider spend and its change on the month before, the largest projects and models, reliability and governance. The same report is a page in the console (Summary → Monthly report), for any past month, ready to print or save as a PDF.
Reports go to members of the organization only, and each member chooses for themselves under Settings → Account → Email reports. Owners and finance members start with both on; everyone else starts with both off. Every email has a link that turns that report off without signing in. A member whose access is limited to some projects never receives them, because they describe the whole organization.
Saved views and links
The Views menu beside the period control saves the screen in front of you, with its period, project, environment and grouping, under a name such as "Board: this quarter". Keep a view for yourself, or share it with the organization so it appears in every member's menu. Copy link to this view copies the address as it is.
A view holds a screen and its filters, never a figure. Opening one reads the data again, through the reader's own role and project access, so sharing a view never shows anybody more than they could already see. Anyone can delete their own views; owners and admins can also delete shared ones. An organization keeps up to 100 saved views.